BdM-15/capture-insights / skills/oci-sweeper
oci-sweeper
VerifiedFederal Organizational Conflict of Interest (OCI) sweeper backed by FAR Subpart 9.5 (9.501-9.508) and the active Theseus workspace knowledge graph. USE WHEN the user asks about OCI risk on a bid, organizational conflicts, incumbent conflicts, biased ground rules, unequal access to information, impaired objectivity, or any pre-bid OCI due diligence. Pulls `company`, `incumbent`, `subcontractor`, `customer`, `program_office`, and prior-contract relationships from the workspace KG, classifies each potential conflict into one of the three FAR 9.505 classes (biased ground rules, unequal access, impaired objectivity), and emits a structured findings envelope with mitigation recommendations (firewall, NDA, recusal, novation). DO NOT USE FOR FAR clause coverage audit (use `compliance-auditor`), proposal prose (use `proposal-generator`), competitor research (use `competitive-intel`), or pricing (use `price-to-win`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.4 KB |
| UPSTREAM.md | markdown | 2.5 KB |
| evals/evals.json | config | 4.3 KB |
| references/far_9_5_oci_taxonomy.md | markdown | 8.9 KB |
| references/oci_remediation_playbook.md | markdown | 5.5 KB |
| references/relationship_query_patterns.md | markdown | 4.8 KB |
UPSTREAM.md
View on GitHub# Upstream
`oci-sweeper` is a **greenfield Theseus skill** with no external upstream. It was authored under the `skill-creator` MANDATE workflow during Phase 4j (Skill Taxonomy + frontmatter pass).
## Authoring discipline
- **Evals-before-prose.** `evals/evals.json` was authored first (3 prompts covering all three FAR 9.505 conflict classes: incumbent → impaired objectivity, customer-side personnel → biased ground rules, prior-contract data → unequal access). The SKILL.md body and references were drafted to close the gaps those evals exposed.
- **Progressive disclosure.** SKILL.md body stays under 200 lines. The FAR taxonomy, mitigation playbook, and Cypher query patterns live in `references/` and load only when the runtime invokes `read_file` against them per the numbered workflow checklist.
- **Closed-by-default.** No MCPs declared. The skill operates against the workspace KG (via `kg_entities`, `kg_query`, `kg_chunks`) and a vendored FAR Subpart 9.5 reference. Live FAR fetch was intentionally skipped — Subpart 9.5 (sections 9.501–9.508) is short and stable enough that a vendored reference is more reliable than a network call.
- **Anthropic best-practices applied** (per `platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices`): six-field frontmatter only; description includes both WHAT (FAR Subpart 9.5 sweep) and WHEN (pre-bid OCI due diligence) plus a third-person "pushy" tone; references one level deep; no `templates/` (uses `assets/` if/when needed); workflow expressed as a numbered Markdown checklist invoking the runtime tools, not as a custom YAML field.
## Future upstream considerations
If the federal acquisition community publishes a canonical OCI taxonomy (DAU / DAFI guidance evolution, GAO bid-protest precedent updates), the `references/far_9_5_oci_taxonomy.md` file is the right place to cite and incorporate it. Keep the three-class structure (biased ground rules / unequal access / impaired objectivity) — that's the FAR statutory anchor and won't change without a Federal Acquisition Regulatory Council rulemaking.
If the skill grows into a multi-skill OCI sub-suite (e.g., separate `oci-sweeper`, `oci-mitigation-plan-drafter`, `oci-waiver-package-builder`), keep `oci-sweeper` as the _detection_ skill and split _drafting_ / _waiver-packaging_ into their own folders rather than inflating this one.
## Re-vendoring
Not applicable — no external source to re-vendor. Treat this UPSTREAM.md as the authoring provenance record only.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |