Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    Draft Repair

    1

    A systematic procedure for reconciling, outlining, and repairing disjointed proposal drafts against SOW requirements.

    $5

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned
    Draft Repair

    Draft Repair

    Example session with this skill installed

    Repair section_id 4.2 using sow.md and messy_draft.docx. Page budget is 3. Weave 'Zero Trust' and 'Scale' themes. Proof points: 99.9% uptime, 50k users. Output to repaired_4.2.md.

    • Read your context and instructions
    • Compiled the draft repair
    • Generated the document

    I have repaired the draft for Section 4.2. I performed a full inventory of the 12 blocks in the source draft, identified three stray duties that were removed, and mapped the remaining content to PWS 4.2.1 through 4.2.4.

    Section 4.2: Technical Infrastructure

    Budget: 3 pages | Estimated: 2.1 pages | Word Count: 945 (was 1,250)

    4.2.1 System Availability (PWS 4.2.1)

    The [Offeror] ensures 99.9% system uptime using a load-balanced architecture across three availability zones. This mechanism provides a self-healing infrastructure that scales automatically to support up to 50,000 concurrent users (PWS 4.2.1).

    4.2.2 Security Architecture (PWS 4.2.2)

    The [Offeror] implements a Zero Trust architecture for all internal service communication. Every request is authenticated and authorized via mTLS, ensuring that identity is verified regardless of network location (PWS 4.2.2).

    ... [Additional sections following SOW order]

    Compliance Table

    SOW IDModalSubsectionEvidence in this sectionGap
    4.2.1shall4.2.1 System AvailabilityUptime proof + scaling mechanismNone
    4.2.2shall4.2.2 Security ArchitectureZero Trust implementationNone
    4.2.3should4.2.3 Legacy SupportCompatibility statementNone

    Repair Log

    • Blocks Dropped: 3 (2 slogans regarding "market leadership", 1 stray duty regarding janitorial services).
    • Modality Restored: 4.2.3 was promoted to 'shall' in the draft; restored to 'should'.
    • Open Items: None.

    Next steps

    1. Review the scaled user count against the updated hardware list.
    2. Verify the mTLS implementation matches the current internal security policy.
    3. Export the markdown to the final proposal template.

    draft-repair.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Align messy drafts to the SOW order for evaluator clarity.Verify every mandatory 'shall' has a corresponding mechanism and tag.Remove stray duties and marketing fluff to meet page budgets.Weave win themes into existing prose without creating 'theme dumps'.

    About this skill

    The problem

    Proposal drafts often become disjointed through multiple contributors, repeating content while missing mandatory requirements. Manual reconciliation against a Statement of Work (SOW) is slow and prone to compliance gaps.

    What it does

    • Inventories existing draft blocks to flag slogans, repetitions, and invented metrics.
    • Reconciles draft content against specific SOW identifiers to find missing "shalls."
    • Generates a rigid outline based on SOW order before writing any prose.
    • Rewrites prose to prioritize evaluator readability with inline SOW tagging.
    • Calculates page-budget estimates to ensure the repair fits solicitation constraints.

    Why this beats prompting it yourself

    Standard prompts often try to "fix everything at once," leading to hallucinations or lost requirements. This skill enforces a mandatory six-step procedure—inventory, reconciliation, and outlining—before a single sentence of prose is written, ensuring 100% compliance coverage.

    Use cases

    • Repairing a "Pink Team" draft that drifted from the SOW structure.
    • Auditing a technical section to ensure every "shall" has a tagged mechanism.
    • Stripping marketing fluff and slogans from engineer-written content.
    • Weaving specific win themes into a compliant narrative without adding bulk.

    Known limitations

    Does not generate first drafts from a blank page. Requires a pre-existing draft and specific SOW items to function.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 1 day ago

    • Passed all security checks, Safe to install

    Listed1 day ago

    Frequently Asked Questions