tender-research

Run parallel sub-agents to research government tenders and write Markdown and JSON reports.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/popodidi/harvis --skill tender-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tender-research
Source: https://github.com/popodidi/harvis/tree/main/projects/pcctw/skills/tender-research
Command: npx skills add https://github.com/popodidi/harvis --skill tender-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates government tender research by coordinating multiple sub-agents to analyze several tenders in parallel, dramatically reducing manual workload and time-to-insight.

Core Features & Use Cases

  • Parallel tender research: Spawns one sub-agent per tender ID and executes in parallel for faster results.
  • Methodology-driven analysis: Each sub-agent follows the tender research methodology and outputs both a human-readable Markdown report and a machine-readable JSON summary.
  • Output versatility: Writes two files per tender: research-{tender_id}.md and research-{tender_id}.json, stored in a user-specified directory.
  • Use Case: Procurement teams evaluating multiple tenders can generate consistent, auditable research packs for governance reviews.

Quick Start

Run the tender research on a set of tender IDs with an optional output directory. For example: /pcctw-tender-research 11501262, TTMH115B006, 115-00133 --output results/

Frequently Asked Questions about tender-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate government tender research for multiple procurement opportunities at once?

Automate government tender research by running parallel sub-agents for each tender ID, spawning simultaneous tasks that extract key metadata. This parallel execution methodology dramatically reduces manual workload and accelerates time-to-insight for procurement teams.

What file formats are generated when analyzing multiple tenders in parallel?

Parallel tender analysis generates two files per tender ID: a human-readable Markdown report (research-{tender_id}.md) and a machine-readable JSON summary (research-{tender_id}.json). Both structured outputs are written to a user-specified output directory.

Can I use this parallel procurement research approach for bid desk governance reviews?

Bid desks can use this parallel procurement research approach to generate consistent, auditable research packs for governance reviews. Each sub-agent follows a methodology-driven analysis workflow to ensure standardized reporting across multiple evaluated tenders.

How do I run parallel research tasks on a set of specific tender IDs?

Run parallel research tasks by passing a comma-separated list of tender IDs and an optional output directory. The system reads the tender methodology, spawns one autonomous sub-agent per ID, and writes the resulting research files to the specified location.

Does parallel tender analysis require any external dependencies or components?

Parallel tender analysis requires no external dependencies or components to function. The advanced internal design coordinates autonomous sub-agents natively, executing the methodology-driven workflow without needing additional libraries or frameworks.

What is the best way to extract key metadata from multiple government tenders simultaneously?

The best way to extract key metadata from multiple government tenders simultaneously is using parallel autonomous sub-agents. This approach enforces a structured methodology that reads each tender, extracts relevant data, and generates both Markdown and JSON reports.