aiskillstore/marketplace / skills/1102tools-dev/govcon-growth-workflow
govcon-growth-workflow
VerifiedTrigger for: finding federal opportunities; capture and bid screening; competitor or incumbent intelligence; recompete pipelines; teaming partner research; agency, customer, or market intelligence; federal labor-rate or pricing context; or refreshing prior GovCon research. Always begin with the complete workflow menu and obtain the user's selection before research, preflight, file generation, web search, or MCP calls. Produce sourced chat findings or an optional validated GovCon Growth Brief without making a bid decision from public data alone.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.9 KB |
| agents/openai.yaml | config | 316 B |
| references/brief-specification.md | markdown | 1.1 KB |
| references/competitor-intelligence.md | markdown | 722 B |
| references/evidence-contract.md | markdown | 3.2 KB |
| references/evidence-limitations.md | markdown | 988 B |
| references/launch-menu-and-question-blocks.md | markdown | 1.8 KB |
| references/market-and-agency-intelligence.md | markdown | 743 B |
| references/opportunity-intelligence.md | markdown | 1.1 KB |
| references/pricing-context.md | markdown | 744 B |
| references/recompete-radar.md | markdown | 707 B |
| references/runtime-adaptation.md | markdown | 1.8 KB |
| references/teaming-due-diligence.md | markdown | 720 B |
| references/web-provider-policy.md | markdown | 7.4 KB |
| scripts/build_growth_brief.py | script | 11.5 KB |
| scripts/validate_growth_brief.py | script | 5.1 KB |
| scripts/validate_research_record.py | script | 18.4 KB |
| skill-report.json | config | 56.9 KB |
| test.md | markdown | 6.3 KB |
| testing.md | markdown | 4.4 KB |
references/evidence-contract.md
View on GitHub# Research evidence contract
Market Research uses schema version `1.2`; GovCon Growth retains schema `1.1`. Both use these shared top-level fields. The example below is the Market Research artifact form:
```json
{
"schema_version": "1.2",
"skill": "market-research-workflow",
"workflow_mode": "complete_report",
"question": "What market evidence informs this acquisition?",
"scope": {"as_of_date": "2026-08-21", "agency": null, "naics": [], "psc": [], "period": null},
"document_register": [],
"user_context": [],
"assumptions": [],
"web_research": {
"mode": "no_public_web",
"approved": true,
"approved_at": "2026-08-21T18:00:00Z",
"disclosure_acknowledged": true,
"planned_providers": [],
"providers_used": [],
"fallback_events": []
},
"queries": [],
"evidence": [],
"findings": [],
"inferences": [],
"user_decisions": [],
"conflicts": [],
"unresolved_questions": [],
"outputs": [],
"validation": {
"findings_approved": false,
"findings_approved_at": "",
"decisions_approved": false,
"decisions_approved_at": "",
"unresolved_items_disposition_approved": false,
"unresolved_items_disposition_approved_at": ""
}
}
```
Every evidence item has a stable ID such as `E001`, source class, title, locator or operation, retrieval time, as-of date when known, concise fact, and limitations. Source classes are `document`, `federal_mcp`, `official_web`, `other_web`, `user_statement`, and `calculation`.
Every source call in `queries` has a stable ID such as `Q001` and records provider, semantic operation, sanitized parameters, the timestamp recorded when that call completed, count or coverage, and limitations. For GovCon Growth, evidence from `federal_mcp`, `official_web`, or `other_web` sources includes `source_call_ids`; its `retrieved_at` must match one of the linked source-call timestamps. Report-build time is never substituted for retrieval time.
Every finding has a stable ID such as `F001`, text, and one or more supporting evidence IDs. Inferences have their own IDs, cite evidence IDs, and state the reasoning and uncertainty. Queries record provider, semantic operation, sanitized parameters, retrieval time, count or coverage, and limitations. The `web_research` object records explicit approval, planned and used providers, and any approved fallback. Never store credentials or sensitive source text.
Every decision string begins with a stable identifier such as `D001:`. Every unresolved-question string begins with a stable identifier such as `U001:`. For a complete Market Research report, `validation` records explicit findings approval, decision approval, and unresolved-item-disposition approval with UTC timestamps. A deferred unresolved item is valid only when its disposition explicitly carries it forward as a limitation.
Market Research schema `1.1` records remain readable for archive review and refresh intake. They must be migrated to `1.2` before a formal report can be generated.
Use `scripts/validate_research_record.py` before generating an artifact. The validator rejects duplicate IDs, unknown evidence references, missing required fields, unapproved enumerations, secrets, and unsafe query keys.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |