BytesAgain is a curated directory of 60,000+ AI agent skills from ClawHub, GitHub, LobeHub, and Dify. Search skills by keyword in 7 languages, browse by role (developer, creator, trader, marketer) or by use case.

How do I find AI skills on BytesAgain?

Use the search bar on BytesAgain.com to search by keyword in 7 languages. You can also browse by role (developer, creator, trader, marketer) or by use case. Each skill shows install instructions for Claude, Cursor, OpenClaw, Continue, and more.

Yes, BytesAgain is completely free. No registration required for searching skills. The MCP API is also free with rate limits.

Does BytesAgain have an API for AI agents?

Yes! BytesAgain provides a free MCP SSE endpoint at /api/mcp/sse for AI agents, plus a REST API at /api/mcp?action=search&q= . No authentication needed.

Can I request a new AI skill on BytesAgain?

Yes! Visit the Requests page on BytesAgain.com to submit a skill request. Your request will be visible to the community and notified to the site admin.

🦀 ClawHub

Benefit Statement Drafter

by @quochungto

Draft Benefit statements that link product capabilities to specific customer-expressed Explicit Needs. Use this skill when preparing follow-up emails, propos...

Versionv1.0.0

#writing #legal #communication

⚡ When to Use

Trigger	Action
This skill drafts one Benefit statement per matched (Explicit Need, capability) pair. Each statement follows a simple structure: the customer stated they need X; our product delivers X in this way.
Use this skill when:
- Preparing a follow-up email after a discovery call where Explicit Needs were surfaced
- Writing the value section of a proposal or deck for a specific account
- Drafting a demo opening that references what the customer told you they needed
- Moving from "here's what our product does" to "here's why it matters for this customer"
Critical gate: This skill requires a `needs-log.md` with at least one confirmed Explicit Need. If you ask this skill to draft Benefits before Explicit Needs exist, it will decline and redirect you to `spin-discovery-question-planner` to develop needs first. This is intentional — Rackham's 5,000-call study found that statements meeting Explicit Needs (true Benefits) are strongly linked to call success, while statements showing how a product can help (Advantages) have no statistically significant relationship to success in large sales.
Do NOT use this skill to: audit existing sales content (use `fab-statement-classifier`), generate discovery questions (use `spin-discovery-question-planner`), or write full proposals or emails (this skill produces statement-level drafts you incorporate into longer content).

💡 Examples

Scenario: Follow-up email after a discovery call with confirmed Explicit Needs

Trigger: AE says — "I had a great call with a VP of Finance. My needs-log shows she said 'we need to cut our monthly close from 7 days to 2 days' and 'we need a single dashboard all three regional controllers can see.' Help me draft the Benefits for my follow-up email."

Process:

(Step 1) Read needs-log.md: Two Explicit Needs confirmed: "cut close from 7 to 2 days" and "single dashboard for three regions."

(Step 2) Match to product-capabilities.md: Automated close workflow matches Need 1. Unified multi-entity dashboard matches Need 2. No gaps.

(Step 4) Draft Benefit 1: "You mentioned you need to cut monthly close from 7 days to 2. Our automated close workflow runs the period-end reconciliation and approval chain in parallel rather than sequentially, which is how clients in your situation have reduced their close to 1-3 days." Draft Benefit 2: "You said you need a single dashboard your three regional controllers can all see. Our multi-entity view consolidates all three regions into one real-time view with role-based access — each controller sees the same live data, and you see the consolidated view above them."

(Step 6) Write benefit-statements-vp-finance-acme.md.

Output: Two grounded Benefit statements ready to be pasted into the follow-up email, anchored to the customer's own words. No aspirational claims.

Scenario: Refusal — only Implied Needs in the record

Trigger: AE says — "I have a call transcript. The customer mentioned they're frustrated with their current system and said approvals take forever. Help me write Benefits."

Process:

(Step 1) Read the transcript: "frustrated with current system" = Implied Need. "approvals take forever" = Implied Need. No Explicit Needs (no "we need," "we want," "we're looking for").

(Step 2) Refusal Protocol fires: No Explicit Needs present.

Output: > STOP. The customer has expressed problems and frustrations (Implied Needs) but has not yet stated what they want or need. This skill cannot draft Benefits without confirmed Explicit Needs — drafting now would produce Advantages, which have no statistically significant relationship to large-sale success. > > Run spin-discovery-question-planner before your next call. Input: the Implied Needs above. The planner will build Implication Questions to develop these into felt problems, and Need-payoff Questions to get the customer to articulate the want. Once they do, return here with the updated needs log.

Scenario: New product launch

Trigger: Solutions consultant says — "We just launched a new security monitoring tool. We don't have any customer conversations yet. How do I use Benefits with this product?"

Process:

(Step 3) New-Product-Launch Sub-flow activates.

(Step 3a) Ask: "What problems is this tool designed to solve?" User provides: insider threat detection, compliance audit trail, real-time alert on anomalous access.

(Step 3b) Map to likely customer types: security directors, compliance officers, CISOs in regulated industries.

(Step 3c) Draft discovery plan: "Before presenting any capabilities, plan Problem → Implication → Need-payoff question chains for each of these three problems. Use spin-discovery-question-planner with this problem list. Only after customers have expressed wants related to these problems should you draft Benefits."

(Step 3d) Draft three PROVISIONAL benefit templates, labeled clearly: "PROVISIONAL — do not use until customer has confirmed this need."

Output: benefit-statements-new-security-tool-provisional.md — problem list, discovery plan, three provisional templates with explicit instruction to develop needs first.

View on ClawHub

TERMINAL

clawhub install bookforge-benefit-statement-drafter