Works with the AI Agents you already use
Service Menu Clarity Builder
The problem Vague service descriptions lead to endless "what's included" emails and scope creep that kills margins.
$9.99
Service Menu Clarity Builder
Example session with this skill installed
I'm a freelance technical writer. I offer API docs, README audits, and monthly blog posts. I struggle with scope creep on revisions. Help me package this for a website.
- Read your context and instructions
- Compiled the service menu clarity
I have organized your technical writing services into a tiered structure focused on preventing scope creep through clear revision limits and defined deliverables.
Technical Documentation Service Menu
Service Context Summary
You provide specialized technical writing for developer-focused products, helping teams translate complex code into readable documentation. The primary buyer need is reducing support overhead and improving developer experience (DX).
Recommended Service Menu Structure
A "Project vs. Retainer" structure works best here to separate one-off audits from ongoing content needs.
Service Packages
1. The README Health Check
- Best for: Open-source projects or startups needing a quick documentation win.
Included deliverables: Full audit of current README.md, revised installation instructions, 1x contribution guide (CONTRIBUTING.md), and a 30-minute walkthrough call.
- Timeline: 3-5 business days.
Boundaries: Includes 1 round of minor text revisions. Does not include API reference documentation or code refactoring.
2. API Reference Core
- Best for: Teams launching new endpoints or internal tools.
Included deliverables: Documentation for up to 10 endpoints, authentication guide, 3 code samples (Node.js, Python, cURL), and OpenAPI/Swagger schema validation.
- Timeline: 10-14 business days.
- Boundaries: Includes 2 rounds of revisions. Requires access to a staging environment or Postman collection.
3. Continuous Authority (Retainer)
- Best for: Growth-stage companies needing consistent developer marketing.
Included deliverables: 2x 1,500-word technical blog posts per month, monthly documentation maintenance, and priority Slack support.
- Timeline: Ongoing (Monthly).
- Boundaries: Unused hours do not roll over. Maximum 2 revisions per article.
Package Comparison Block
| Feature | README Health Check | API Reference Core | Continuous Authority |
|---|---|---|---|
| Primary Goal | Clarity & Setup | Technical Accuracy | Growth & Education |
| Deliverables | README + Audit | Endpoint Docs | Blog Posts + Maint. |
| Revisions | 1 Round | 2 Rounds | 2 per Post |
| Support | Email Only | Priority Slack |
Next steps
- Review the revision limits to ensure they align with your typical workflow.
- Select one package to pilot as a "Productized Service" on your landing page.
- Use the "Boundaries" section to update your standard freelance agreement.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Vague service descriptions lead to endless "what's included" emails and scope creep that kills margins. Many freelancers and agencies struggle to define where their work ends and where a new invoice should begin.
What it does
- Converts loose service ideas into structured packages with specific, tangible deliverables.
- Drafts professional boundaries and exclusions to prevent unpaid work and scope creep.
- Generates buyer-friendly comparison tables that help leads select the right tier without manual intervention.
- Writes service-specific FAQs that address common pre-sale objections and technical requirements.
- Builds realistic delivery timelines and process stages based on client responsibilities.
Why this beats prompting it yourself
Most generic prompts result in "fluff" that sounds like marketing jargon. This skill enforces a commercial clarity framework that prioritizes deliverables, boundaries, and exclusions, ensuring your offer is actually ready for a contract.
Use cases
- Turning a messy list of skills into a "Starter / Growth / Scale" pricing page.
- Auditing an existing service menu to identify hidden risks of scope creep.
- Creating onboarding documents that clearly define what the client must provide.
- Drafting a professional "Service Exclusions" list for a high-ticket proposal.
Known limitations
This skill provides drafting and positioning support only. It does not provide legal, tax, or financial advice and should not be used as a replacement for a formal legal contract.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.
Provides drafting and positioning support only. Does not replace legal, tax, or financial advice. Requires user to provide basic business context for accurate output.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 2 months ago
- Software
Python
Permissions
No special permissions declared or detected