aiskillstore/marketplace / skills/1102tools-dev/sow-pws-builder
sow-pws-builder
VerifiedTrigger for: writing, revising, converting, or descoping a federal Statement of Work, Performance Work Statement, SOW, PWS, or SOO; develop executable requirements; define contract scope; create measurable performance standards; or prepare requirements before an IGCE. Produce a contract-file-ready .docx plus separate chat-only staffing and Section B handoffs. Never place FTEs, SOC codes, staffing estimates, IGCE content, CLINs, or pricing schedules inside the SOW/PWS body. Do NOT use for the IGCE, market research report, acquisition plan, QASP, or clause-selection matrix.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.0 KB |
| agents/openai.yaml | config | 295 B |
| references/document-specification.md | markdown | 5.3 KB |
| references/handoff-specification.md | markdown | 2.9 KB |
| references/question-blocks.md | markdown | 3.5 KB |
| references/regulatory-and-content-rules.md | markdown | 3.5 KB |
| references/runtime-adaptation.md | markdown | 1.7 KB |
| references/validation-gates.md | markdown | 2.5 KB |
| scripts/validate_docx.py | script | 6.9 KB |
| skill-report.json | config | 39.9 KB |
| test.md | markdown | 3.3 KB |
| testing.md | markdown | 24.3 KB |
skill-report.json
View on GitHub{
"schema_version": "2.0",
"meta": {
"generated_at": "2026-08-24T13:08:37.491Z",
"slug": "1102tools-dev-sow-pws-builder",
"source_url": "https://github.com/1102tools-dev/federal-contracting-skills/tree/6c8edf1c45e63acd1bdbb276392924435dde28b3/skills/sow-pws-builder",
"source_ref": "6c8edf1c45e63acd1bdbb276392924435dde28b3",
"model": "codex",
"analysis_version": "3.0.0",
"source_type": "community",
"content_hash": "9a959975cd5474f645959f66bc7b4f7351ec75793cda3fa1120fc9e80c127e0d",
"tree_hash": "c4beea5e2ef1c6a884383e49a951f0ed959101d12437178618f3134f73b7bb64",
"provenance": {
"model_effective": "codex",
"fallback_chain": [
{
"agent": "codex",
"outcome": "success"
}
],
"analysis_version": "3.0.0"
},
"upstream_version_raw": null,
"upstream_version_normalized": null,
"upstream_version_source": "none",
"upstream_version_status": "missing",
"upstream_commit_sha": "6c8edf1c45e63acd1bdbb276392924435dde28b3"
},
"skill": {
"name": "sow-pws-builder",
"description": "Build, revise, convert, or reduce federal Statements of Work and Performance Work Statements. Produce a contract-ready DOCX with measurable requirements and separate staffing and Section B handoffs.",
"summary": "Create structured federal SOW and PWS documents while keeping staffing and pricing details separate.",
"icon": "📦",
"author": "1102tools-dev",
"license": "MIT",
"category": "documentation",
"tags": [
"federal-contracting",
"sow",
"pws",
"requirements",
"docx"
],
"supported_tools": [
"claude",
"codex",
"claude-code"
],
"risk_factors": [
"filesystem",
"external_commands"
]
},
"security_audit": {
"risk_level": "safe",
"is_blocked": false,
"safe_to_publish": true,
"analysis_status": "ok",
"summary": "All 39 static findings are false positives. The DOCX validator reads local archive content without extraction, while the reported command patterns are Markdown formatting or a bounded call to the bundled validator. No prompt injection, data exfiltration, or malicious business intent was found.",
"remediation": [],
"risk_factor_evidence": [
{
"factor": "filesystem",
"evidence": [
{
"file": "scripts/validate_docx.py",
"line_start": 10,
"line_end": 10
},
{
"file": "scripts/validate_docx.py",
"line_start": 69,
"line_end": 69
},
{
"file": "scripts/validate_docx.py",
"line_start": 80,
"line_end": 80
},
{
"file": "scripts/validate_docx.py",
"line_start": 82,
"line_end": 82
},
{
"file": "scripts/validate_docx.py",
"line_start": 88,
"line_end": 88
},
{
"file": "scripts/validate_docx.py",
"line_start": 140,
"line_end": 140
}
]
},
{
"factor": "external_commands",
"evidence": [
{
"file": "SKILL.md",
"line_start": 18,
"line_end": 18
},
{
"file": "SKILL.md",
"line_start": 20,
"line_end": 20
},
{
"file": "SKILL.md",
"line_start": 31,
"line_end": 31
},
{
"file": "SKILL.md",
"line_start": 39,
"line_end": 39
},
{
"file": "SKILL.md",
"line_start": 45,
"line_end": 45
},
{
"file": "SKILL.md",
"line_start": 70,
"line_end": 70
},
{
"file": "SKILL.md",
"line_start": 72,
"line_end": 72
},
{
"file": "SKILL.md",
"line_start": 73,
"line_end": 73
},
{
"file": "SKILL.md",
"line_start": 88,
"line_end": 88
},
{
"file": "SKILL.md",
"line_start": 137,
"line_end": 137
},
{
"file": "SKILL.md",
"line_start": 145,
"line_end": 145
},
{
"file": "SKILL.md",
"line_start": 161,
"line_end": 161
},
{
"file": "SKILL.md",
"line_start": 164,
"line_end": 164
},
{
"file": "SKILL.md",
"line_start": 166,
"line_end": 166
}
]
}
],
"static_findings": [
{
"id": "blocker:references/document-specification.md:78:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "references/document-specification.md",
"line_start": 78,
"line_end": 78,
"snippet": "State report content, cadence, meetings, data sources, Government roles, escalation, and record rete"
},
{
"id": "blocker:references/document-specification.md:115:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "references/document-specification.md",
"line_start": 115,
"line_end": 115,
"snippet": "- Avoid standalone `support`, undefined `as needed`, unnamed `best practices`, and coordination with"
},
{
"id": "blocker:references/handoff-specification.md:26:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "references/handoff-specification.md",
"line_start": 26,
"line_end": 26,
"snippet": "- Identify hybrid CLIN or contract-type routing in Notes."
},
{
"id": "blocker:references/handoff-specification.md:57:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "references/handoff-specification.md",
"line_start": 57,
"line_end": 57,
"snippet": "For CPFF, carry the confirmed Completion or Term form in Notes. For hybrid requirements, make each l"
},
{
"id": "blocker:references/question-blocks.md:8:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "references/question-blocks.md",
"line_start": 8,
"line_end": 8,
"snippet": "2. User-confirmed contract framework: FFP, T&M, LH, CPFF, CPAF, CPIF, hybrid by CLIN, or pending CO "
},
{
"id": "blocker:references/validation-gates.md:15:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "references/validation-gates.md",
"line_start": 15,
"line_end": 15,
"snippet": "- The file is a valid DOCX ZIP."
},
{
"id": "filesystem:scripts/validate_docx.py:10:python-archive-libraries",
"category": "filesystem",
"severity": "medium",
"pattern": "Python archive libraries",
"file": "scripts/validate_docx.py",
"line_start": 10,
"line_end": 10,
"snippet": "import zipfile"
},
{
"id": "filesystem:scripts/validate_docx.py:69:python-archive-libraries",
"category": "filesystem",
"severity": "medium",
"pattern": "Python archive libraries",
"file": "scripts/validate_docx.py",
"line_start": 69,
"line_end": 69,
"snippet": "with zipfile.ZipFile(path) as archive:"
},
{
"id": "filesystem:scripts/validate_docx.py:80:python-archive-libraries",
"category": "filesystem",
"severity": "medium",
"pattern": "Python archive libraries",
"file": "scripts/validate_docx.py",
"line_start": 80,
"line_end": 80,
"snippet": "if not zipfile.is_zipfile(path):"
},
{
"id": "filesystem:scripts/validate_docx.py:82:python-archive-libraries",
"category": "filesystem",
"severity": "medium",
"pattern": "Python archive libraries",
"file": "scripts/validate_docx.py",
"line_start": 82,
"line_end": 82,
"snippet": "with zipfile.ZipFile(path) as archive:"
},
{
"id": "filesystem:scripts/validate_docx.py:88:python-archive-libraries",
"category": "filesystem",
"severity": "medium",
"pattern": "Python archive libraries",
"file": "scripts/validate_docx.py",
"line_start": 88,
"line_end": 88,
"snippet": "except (OSError, ValueError, zipfile.BadZipFile) as exc:"
},
{
"id": "filesystem:scripts/validate_docx.py:140:python-archive-libraries",
"category": "filesystem",
"severity": "medium",
"pattern": "Python archive libraries",
"file": "scripts/validate_docx.py",
"line_start": 140,
"line_end": 140,
"snippet": "except (KeyError, OSError, zipfile.BadZipFile) as exc:"
},
{
"id": "blocker:scripts/validate_docx.py:81:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "scripts/validate_docx.py",
"line_start": 81,
"line_end": 81,
"snippet": "return {\"status\": \"fail\", \"failures\": [\"file is not a valid DOCX ZIP\"]}"
},
{
"id": "external_commands:SKILL.md:18:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 18,
"line_end": 18,
"snippet": "Turn program-office scope decisions into a contract-file-ready `.docx` SOW or PWS. Produce three sep"
},
{
"id": "external_commands:SKILL.md:20:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 20,
"line_end": 20,
"snippet": "1. The SOW/PWS `.docx`, containing requirements and measurable acceptance or surveillance content."
},
{
"id": "external_commands:SKILL.md:31:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 31,
"line_end": 31,
"snippet": "- [document-specification.md](references/document-specification.md) before authoring the `.docx`."
},
{
"id": "external_commands:SKILL.md:39:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 39,
"line_end": 39,
"snippet": "1. **Separation:** The `.docx` contains no staffing handoff, FTE estimate, SOC code, IGCE content, C"
},
{
"id": "external_commands:SKILL.md:45:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 45,
"line_end": 45,
"snippet": "7. **QASP and CPARS:** QASP payment or administrative consequences must not pre-commit CPARS ratings"
},
{
"id": "external_commands:SKILL.md:70:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 70,
"line_end": 70,
"snippet": "1. Confirm the host can read inputs and create `.docx` files."
},
{
"id": "external_commands:SKILL.md:72:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 72,
"line_end": 72,
"snippet": "3. Confirm Python and `python-docx` or an equivalent OOXML authoring capability for `scripts/validat"
},
{
"id": "external_commands:SKILL.md:73:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 73,
"line_end": 73,
"snippet": "4. Match capabilities semantically. Do not depend on `/mnt` paths, a named client tool, or a generat"
},
{
"id": "external_commands:SKILL.md:88:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 88,
"line_end": 88,
"snippet": "If T&M or LH is selected, flag the D&F and overall ceiling-price requirement for Contracting Officer"
},
{
"id": "external_commands:SKILL.md:137:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 137,
"line_end": 137,
"snippet": "The final sentence must ask the user to proceed or correct the summary. Stop immediately after the q"
},
{
"id": "external_commands:SKILL.md:145:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 145,
"line_end": 145,
"snippet": "3. Use real `Heading 1`, `Heading 2`, and `Heading 3` styles, real numbered or bulleted lists, expli"
},
{
"id": "external_commands:SKILL.md:161:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 161,
"line_end": 161,
"snippet": "6. Run `scripts/validate_docx.py <document> --document-type <sow|pws>`."
},
{
"id": "external_commands:SKILL.md:164:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 164,
"line_end": 164,
"snippet": "Deliver the `.docx`, then present both chat-only handoffs using [handoff-specification.md](reference"
},
{
"id": "external_commands:SKILL.md:166:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 166,
"line_end": 166,
"snippet": "When a dynamic TOC has not been updated in Word, end with: `Open the document in Word, press Ctrl+A "
},
{
"id": "blocker:SKILL.md:44:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "SKILL.md",
"line_start": 44,
"line_end": 44,
"snippet": "6. **Result-oriented PWS:** Organize a PWS around outcomes, measurable standards, AQLs, and assessme"
},
{
"id": "blocker:SKILL.md:81:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "SKILL.md",
"line_start": 81,
"line_end": 81,
"snippet": "2. User-confirmed contract type: FFP, T&M, LH, CR subtype, or hybrid by CLIN."
},
{
"id": "blocker:test.md:18:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "test.md",
"line_start": 18,
"line_end": 18,
"snippet": "- The TOC remained a valid dynamic field with a placeholder in the LibreOffice render. The skill cor"
},
{
"id": "blocker:test.md:25:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "test.md",
"line_start": 25,
"line_end": 25,
"snippet": "1. A rich FFP help-desk prompt with one 24x7x365 Tier 1 seat and 1,880 productive hours produced 4.6"
},
{
"id": "blocker:testing.md:53:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "testing.md",
"line_start": 53,
"line_end": 53,
"snippet": "- **It has not been tested on** Special Access Program or Special Access Required variants; commerci"
},
{
"id": "blocker:testing.md:132:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "testing.md",
"line_start": 132,
"line_end": 132,
"snippet": "Root cause: the skill's FAR 37.102(d) enforcement block was focused on staffing tables and the Phase"
},
{
"id": "blocker:testing.md:143:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "testing.md",
"line_start": 143,
"line_end": 143,
"snippet": "- **Scenario 5:** Non-commercial CPFF R&D PWS, Workflow A, NASA Glenn Research Center cryogenic flui"
},
{
"id": "blocker:testing.md:179:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "testing.md",
"line_start": 179,
"line_end": 179,
"snippet": "3. **Sonnet self-approved Phase 1 Decision Summary on Scenario 6.** Said \"Proceeding to document ass"
},
{
"id": "blocker:testing.md:187:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "testing.md",
"line_start": 187,
"line_end": 187,
"snippet": "7. **Sonnet domain reasoning on CPFF was notably sharp.** Sonnet on Scenario 5 caught that CPFF fee "
},
{
"id": "blocker:testing.md:248:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "testing.md",
"line_start": 248,
"line_end": 248,
"snippet": "- **Hybrid contract structures** (FFP plus T&M or LH CLINs; FFP with cost-reimbursable travel CLINs "
},
{
"id": "blocker:testing.md:254:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "testing.md",
"line_start": 254,
"line_end": 254,
"snippet": "Users working in these contexts should expect to validate outputs more carefully and may encounter e"
},
{
"id": "blocker:testing.md:266:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "testing.md",
"line_start": 266,
"line_end": 266,
"snippet": "Every assertion was graded by a separate Claude instance reading only the worker's final output and "
}
],
"finding_verdicts": [
{
"id": "blocker:references/document-specification.md:78:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "This line defines reporting content for a contract document. It does not inspect the host system or collect runtime information."
},
{
"id": "blocker:references/document-specification.md:115:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "This is writing guidance that rejects vague requirement language. It contains no reconnaissance behavior or system command."
},
{
"id": "blocker:references/handoff-specification.md:26:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "This line requests contract-type routing notes for an acquisition handoff. It does not query or enumerate system resources."
},
{
"id": "blocker:references/handoff-specification.md:57:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "This line describes CPFF and hybrid contract documentation. It has no host discovery or security-sensitive behavior."
},
{
"id": "blocker:references/question-blocks.md:8:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "This is a user-facing question about the selected contract framework. It does not perform system reconnaissance."
},
{
"id": "blocker:references/validation-gates.md:15:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "Checking whether a supplied file is a valid DOCX ZIP is format validation, not host or network reconnaissance."
},
{
"id": "filesystem:scripts/validate_docx.py:10:python-archive-libraries",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The zipfile import supports read-only inspection of DOCX package structure. The script does not extract archives or write package contents."
},
{
"id": "filesystem:scripts/validate_docx.py:69:python-archive-libraries",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The validator opens the user-selected DOCX and reads two fixed OOXML members. No archive extraction, traversal, or modification occurs."
},
{
"id": "filesystem:scripts/validate_docx.py:80:python-archive-libraries",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "is_zipfile only verifies the format of the document path supplied to the local validator. It performs no unsafe filesystem operation."
},
{
"id": "filesystem:scripts/validate_docx.py:82:python-archive-libraries",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The archive is opened only to enumerate members and confirm fixed DOCX parts. Nothing is extracted or written."
},
{
"id": "filesystem:scripts/validate_docx.py:88:python-archive-libraries",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "This exception handler safely reports malformed or unreadable DOCX files. It adds no archive capability or security risk."
},
{
"id": "filesystem:scripts/validate_docx.py:140:python-archive-libraries",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "This exception handler contains failures from fixed-member DOCX inspection. It does not extract data or alter the filesystem."
},
{
"id": "blocker:scripts/validate_docx.py:81:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The line returns a validation error for an invalid local DOCX file. It does not reveal or probe host system details."
},
{
"id": "external_commands:SKILL.md:18:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The backticks are Markdown formatting around the DOCX extension. No shell or Ruby execution syntax is present."
},
{
"id": "external_commands:SKILL.md:20:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The backticks format a DOCX filename extension in prose. They do not execute a command."
},
{
"id": "external_commands:SKILL.md:31:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "This line links a bundled reference file and formats the DOCX extension. It contains no command execution."
},
{
"id": "external_commands:SKILL.md:39:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The line uses Markdown backticks to identify the DOCX artifact. It does not invoke a shell."
},
{
"id": "external_commands:SKILL.md:45:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "Backticks format CPARS rating labels in documentation. There is no executable expression or external command."
},
{
"id": "external_commands:SKILL.md:70:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The line asks the host to confirm normal document read and write capability. Its backticks only format the DOCX extension."
},
{
"id": "external_commands:SKILL.md:72:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.98,
"reason": "This dependency check names Python, python-docx, and the bundled validator using Markdown. It does not contain shell substitution or untrusted command construction."
},
{
"id": "external_commands:SKILL.md:73:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The backticks format a mount-path example that the skill explicitly says not to depend on. No command is executed."
},
{
"id": "external_commands:SKILL.md:88:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The backticks format a pending-decision placeholder in contract prose. They are not execution syntax."
},
{
"id": "external_commands:SKILL.md:137:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The backticks identify the DOCX artifact in a workflow gate. This is plain Markdown documentation."
},
{
"id": "external_commands:SKILL.md:145:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The backticks format Microsoft Word style names. They do not invoke Ruby or a shell."
},
{
"id": "external_commands:SKILL.md:161:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "This is a direct invocation of the bundled read-only validator with a document path and an enumerated document type. It uses no shell substitution or dynamically constructed command."
},
{
"id": "external_commands:SKILL.md:164:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The line formats the DOCX extension and links a bundled handoff reference. It contains no executable command."
},
{
"id": "external_commands:SKILL.md:166:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The backticks quote a user instruction for refreshing a Word table of contents. Keyboard actions in prose are not shell execution."
},
{
"id": "blocker:SKILL.md:44:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "This line defines outcome-based PWS writing requirements. It does not inspect system state or resources."
},
{
"id": "blocker:SKILL.md:81:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "This is an acquisition intake question about contract type. It has no system reconnaissance behavior."
},
{
"id": "blocker:test.md:18:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "This test record describes table-of-contents rendering behavior in LibreOffice. It does not direct host inspection or data collection."
},
{
"id": "blocker:test.md:25:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "This line records a staffing calculation from a behavior test. It does not probe system information."
},
{
"id": "blocker:testing.md:53:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The line documents untested acquisition scenarios. It contains no host discovery or reconnaissance instruction."
},
{
"id": "blocker:testing.md:132:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "This is a root-cause note about contract-document staffing language. It has no system-level behavior."
},
{
"id": "blocker:testing.md:143:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "This line identifies a fictional federal acquisition test scenario. It does not inspect or enumerate a system."
},
{
"id": "blocker:testing.md:179:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The line reports a failed user-approval gate during testing and criticizes self-approval. It is not an instruction to bypass approval or security review."
},
{
"id": "blocker:testing.md:187:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "This line evaluates contract-law reasoning from a test run. It has no reconnaissance content."
},
{
"id": "blocker:testing.md:248:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The line lists untested hybrid contract structures. It does not request system discovery."
},
{
"id": "blocker:testing.md:254:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "This is a caution to validate outputs for untested acquisition contexts. It contains no system inspection behavior."
},
{
"id": "blocker:testing.md:266:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.99,
"reason": "The line explains independent grading of test outputs. It does not access system information or direct reconnaissance."
}
],
"semantic_findings": [],
"critical_findings": [],
"high_findings": [],
"medium_findings": [],
"low_findings": [],
"dangerous_patterns": [],
"files_scanned": 11,
"total_lines": 1126,
"audit_model": "codex",
"audited_at": "2026-08-24T13:08:37.491Z",
"agent_auto_install_policy": "allowed",
"manual_install_policy": "allowed"
},
"content": {
"user_title": "Build Federal SOW and PWS Documents",
"value_statement": "Federal acquisition teams need measurable requirements without mixing pricing content into the contract document. This skill builds structured SOW or PWS files and separate internal handoffs.",
"seo_keywords": [
"Claude",
"Codex",
"Claude Code",
"Statement of Work",
"Performance Work Statement",
"federal contracting",
"SOW builder",
"PWS builder",
"DOCX requirements"
],
"actual_capabilities": [
"Guides intake for document form, contract framework, scope, period, quality, security, and transition.",
"Builds a new SOW or PWS, converts an SOO, or reduces scope in an existing requirements document.",
"Structures measurable requirements, deliverables, acceptance criteria, performance standards, and AQLs.",
"Produces separate chat-only staffing and Section B handoffs without placing pricing details in the contract document.",
"Validates DOCX structure, required sections, dynamic TOC settings, and prohibited content leakage."
],
"limitations": [
"Does not create an IGCE, acquisition plan, market research report, clause matrix, or standalone QASP.",
"Requires user or Contracting Officer confirmation for contract type, commerciality, and CPFF form decisions.",
"Requires local DOCX authoring and office rendering capabilities for the complete workflow.",
"Does not process classified information or replace legal, policy, or Contracting Officer review."
],
"use_cases": [
{
"title": "Draft a New PWS",
"description": "Turn program requirements into outcome-based objectives, standards, AQLs, deliverables, and acceptance criteria.",
"target_user": "Federal program manager"
},
{
"title": "Convert an SOO",
"description": "Extract settled objectives and identify missing decisions before producing an executable SOW or PWS.",
"target_user": "Acquisition specialist"
},
{
"title": "Reduce Contract Scope",
"description": "Compare current requirements with budget constraints and revise selected capabilities while preserving internal staffing assumptions.",
"target_user": "Contracting Officer"
}
],
"prompt_templates": [
{
"title": "Start a Basic PWS",
"prompt": "Build a PWS for [service]. The agency is [agency], users are [population], and performance occurs at [location]. Begin with the required intake questions.",
"scenario": "Use when starting from a short service description."
},
{
"title": "Draft from Detailed Requirements",
"prompt": "Create a [SOW or PWS] from these requirements: [requirements]. The confirmed contract framework is [type], and the period is [period]. Stop at each approval gate.",
"scenario": "Use when the main scope and acquisition decisions are available."
},
{
"title": "Convert a Source Document",
"prompt": "Convert the attached SOO into a [SOW or PWS]. Preserve settled facts, list unresolved decisions, and keep staffing and Section B details outside the DOCX.",
"scenario": "Use when objectives already exist in an SOO."
},
{
"title": "Perform a Controlled Scope Reduction",
"prompt": "Revise the attached [SOW or PWS] to meet a target of [budget or coverage]. Present capability tradeoffs first, wait for selection, then update the document and handoffs.",
"scenario": "Use for a budget-driven revision of an existing requirement."
}
],
"output_examples": [
{
"input": "Create a PWS for a 24-hour federal help desk with measurable service levels.",
"output": [
"A DOCX PWS organized around service outcomes, response standards, AQLs, deliverables, security, transition, and a QASP summary.",
"A separate staffing handoff showing the approved coverage basis.",
"A separate Section B handoff with suggested line-item structure."
]
},
{
"input": "Convert an agency SOO for application modernization into a contract-ready SOW.",
"output": "A structured SOW that preserves supplied objectives, resolves scope gaps through approval questions, and defines testable tasks and acceptance criteria."
},
{
"input": "Reduce an existing PWS while protecting essential incident response coverage.",
"output": "A revised PWS reflecting approved capability tradeoffs, plus updated internal staffing and Section B handoffs that remain outside the contract file."
}
],
"best_practices": [
"Provide known scope, workload, service levels, period, location, security context, and agency templates before drafting.",
"Confirm staffing assumptions and the Decision Summary before document generation.",
"Have the Contracting Officer review contract framework, clauses, Section B structure, and unresolved assumptions."
],
"anti_patterns": [
"Do not ask the skill to choose a contract type, commerciality determination, or CPFF form.",
"Do not place staffing counts, SOC codes, CLINs, rates, or pricing schedules inside the SOW or PWS.",
"Do not treat LibreOffice rendering or automated validation as proof of Microsoft Word behavior."
],
"faq": [
{
"question": "What documents can this skill create?",
"answer": "It creates federal SOW or PWS DOCX files and supports SOO conversion and controlled scope reduction."
},
{
"question": "Does it create an IGCE?",
"answer": "No. It creates a chat-only staffing handoff that a separate pricing or IGCE workflow can use."
},
{
"question": "Can it select the contract type?",
"answer": "No. It explains document consequences but requires the user or Contracting Officer to confirm the contract framework."
},
{
"question": "Where do CLIN and pricing details appear?",
"answer": "They appear only in a chat-only Section B handoff, never in the SOW or PWS body."
},
{
"question": "How does it validate the DOCX?",
"answer": "It checks package structure, section order, headings, TOC settings, measurable content, and prohibited information leakage."
},
{
"question": "Does it replace acquisition or legal review?",
"answer": "No. A qualified reviewer must verify regulatory citations, agency requirements, assumptions, security language, and final acquisition decisions."
}
]
},
"file_structure": [
{
"name": "agents",
"type": "dir",
"path": "agents",
"children": [
{
"name": "openai.yaml",
"type": "file",
"path": "agents/openai.yaml",
"lines": 8
}
]
},
{
"name": "references",
"type": "dir",
"path": "references",
"children": [
{
"name": "document-specification.md",
"type": "file",
"path": "references/document-specification.md",
"lines": 128
},
{
"name": "handoff-specification.md",
"type": "file",
"path": "references/handoff-specification.md",
"lines": 72
},
{
"name": "question-blocks.md",
"type": "file",
"path": "references/question-blocks.md",
"lines": 80
},
{
"name": "regulatory-and-content-rules.md",
"type": "file",
"path": "references/regulatory-and-content-rules.md",
"lines": 56
},
{
"name": "runtime-adaptation.md",
"type": "file",
"path": "references/runtime-adaptation.md",
"lines": 28
},
{
"name": "validation-gates.md",
"type": "file",
"path": "references/validation-gates.md",
"lines": 62
}
]
},
{
"name": "scripts",
"type": "dir",
"path": "scripts",
"children": [
{
"name": "validate_docx.py",
"type": "file",
"path": "scripts/validate_docx.py",
"lines": 180
}
]
},
{
"name": "SKILL.md",
"type": "file",
"path": "SKILL.md",
"lines": 179
},
{
"name": "test.md",
"type": "file",
"path": "test.md",
"lines": 48
},
{
"name": "testing.md",
"type": "file",
"path": "testing.md",
"lines": 285
}
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |