Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
GitHub Copilot
Gemini CLI+20 moreClaude CodeCursorCodex CLIGitHub CopilotGemini CLI
OpenClaw
Manus
Grok+17 agentsPage Budget Editor
Reduces proposal sections to specific page budgets while protecting mandatory requirements and tracking every cut.
$5
Page Budget Editor
Example session with this skill installed
Cut section 4.2 in proposal_draft.md to 2 pages. 450 words/page. Graphics count. Mandatory IDs: SOW-101, SOW-102. Move overflow to Appendix A. Output to section_4.2_cut.md.
- Read your context and instructions
- Compiled the page budget editor
- Generated the document
Processed section 4.2. Reduced from 2.8 pages (1,260 words) to 1.95 pages (878 words). All mandatory SOW IDs (SOW-101, SOW-102) are preserved in the body narrative.
Section 4.2: Technical Implementation
Budget: 2.0 pages | Initial: 2.8 pages | Final: 1.95 pages | Words: 878
4.2.1 System Architecture [SOW-101]
The proposed architecture utilizes a distributed node network to ensure high availability. Each node operates independently, processing data streams in real-time. This configuration supports the mandatory 99.9% uptime requirement.
4.2.2 Security Protocols [SOW-102]
Our security framework implements AES-256 encryption at rest and TLS 1.3 in transit. Access controls are managed via a centralized identity provider, ensuring that all session logs are immutable and auditable.
Detailed Encryption Walkthrough: Appendix A (SOW-102).
Local Compliance Table
| Requirement ID | Location | Status |
|---|---|---|
| SOW-101 | 4.2.1 | Compliant |
| SOW-102 | 4.2.2 | Compliant |
Appendix A: Supplemental Narrative
Moved from 4.2.2: The encryption walkthrough involving the Monday clerk cycle was relocated here to meet page constraints. This narrative provides secondary evidence for the TLS 1.3 implementation (SOW-102).
Dropped-vs-Kept Log
| Block | Kind | Action | Pages | Destination | Reason |
|---|---|---|---|---|---|
| Intro 4.2 | restated intro | cut | 0.15 | — | Repeated heading content |
| Fig 4-1 | graphic | kept | 0.40 | Body | Required for SOW-101 |
| Walkthrough | example | moved | 0.30 | Appendix A | Second example for SOW-102 |
Next steps
- Review the pointers in Section 4.2.2 to ensure the flow to Appendix A is logical.
- Verify that the figure placeholder in Section 4.2.1 aligns with the final graphic dimensions.
- Finalize the Appendix A heading to match the master proposal template.
page-budget-editor.pdf
PDF · document
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
About this skill
The problem
Proposals and SOWs often exceed strict page limits, forcing developers and proposal leads to manually prune text. The risk of accidentally deleting a mandatory requirement ("shall") or failing to account for graphic real estate leads to non-compliant submissions.
What it does
- Calculates precise page counts using word density, table row counts, and graphic placeholders.
- Inventories every document block to map narrative evidence to specific SOW/PWS identifiers.
- Ranks potential cuts by priority, targeting redundant intros and culture padding first.
- Relocates overflow narrative to appendices with cross-reference pointers to maintain compliance.
- Generates a dropped-vs-kept log to audit every change against the original draft.
Why this beats prompting it yourself
Generic LLM prompts often "hallucinate" page counts or drop technical requirements to hit a length target. This skill enforces a rigid inventory-first procedure that treats mandatory requirements as immutable, ensuring the cut draft remains 100% compliant with the solicitation.
Use cases
- Reducing a three-page technical section to a two-page limit without losing mandatory claims.
- Moving non-essential worked examples to an appendix to make room for required figures.
- Auditing a draft to identify "padding" like slogans or restated win themes that consume budget.
- Ensuring all SOW identifiers are mapped to narrative blocks before and after document compression.
Known limitations
This skill requires an already coherent draft. It will not fix disjointed structure, write new content, or adjust document margins and font sizes to bypass limits.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 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