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

Call Outcome Classifier

by @quochungto

Classify whether a sales call outcome was an Order, an Advance, a Continuation, or a No-sale — and flag when the seller has misread a Continuation as success...

Versionv1.0.0

#crypto #can-make-purchases #clawhub

⚡ When to Use

Trigger	Action
This skill is most valuable when your honest answer to "how did the call go?" is "pretty well, they seemed interested" — that phrasing is a red flag. Rackham's research on 35,000+ sales calls found that salespeople routinely classify calls as successful when the customer expressed enthusiasm but agreed to nothing concrete. The skill forces you to find the customer action; if there isn't one, it classifies the call as a Continuation regardless of how positive the tone was.
Input this skill needs: Call notes or a transcript. Deal context (account name, stage, what happened on prior calls) improves the assessment but is not required.
Do not use this skill to plan the next call. If the outcome is a Continuation, use `commitment-and-advance-planner` to define a better Advance objective before the next call.
---

💡 Examples

Example 1: Genuine Advance — Specific Action Named

Scenario: Enterprise AE reviewing notes from a second discovery call with a logistics software prospect.

Trigger: "I think we moved forward but want to make sure before I update the CRM."

Call notes excerpt: *"End of call: Marcus said he wants to loop in his VP of Operations before they go further. He offered to set up a three-way call for next Thursday and asked me to send him a one-pager to share internally ahead of time. I said I'd have it to him by Wednesday."*

Process:

Step 1: Customer action statements: "He offered to set up a three-way call for next Thursday" — customer is taking action (setting up the call). "Asked me to send a one-pager" — seller action.

Step 2: Advance. The customer agreed to arrange access to a higher-level decision-maker (VP of Operations) and set a specific date (next Thursday).

Step 3: No misread risk. The customer action (three-way call with VP) is specific, dated, and customer-initiated.

Output: call-outcome-2024-03-12.md — ADVANCE. Customer action: "Marcus agreed to arrange three-way call with VP of Operations for Thursday 2024-03-14; confirmed before call." CRM update: advance to next stage, log VP of Operations introduction as next-step objective.

Example 2: Continuation Disguised as Success

Scenario: Mid-market AE reviewing notes from a demo call that felt like a breakthrough.

Trigger: "The demo went great. They were really engaged and the VP said it was exactly what they needed. Should I move this to 'proposal stage' in the CRM?"

Call notes excerpt: *"Fantastic demo — they loved the reporting module. VP said 'this is exactly the kind of solution we've been looking for.' Everyone was nodding. At the end, Sarah (champion) said 'we're definitely interested, let's circle back after we've had some time to digest this.' I said I'd follow up next week."*

Process:

Step 1: Customer action statements: "Let's circle back after we've had some time to digest this" — no specific action, conditional and buyer-initiated in form only. "I'd follow up next week" — seller action only.

Step 2: Continuation. No customer action committed. "Circling back" is buyer-conditional with no date, no agenda, no confirmed attendees.

Step 3: Continuation-as-success misread present. The VP's phrase "this is exactly the kind of solution we've been looking for" is an expression of sentiment, not a commitment. "Let's circle back" matches the classic Continuation pattern. Flag raised.

Output: call-outcome-2024-03-15.md — CONTINUATION. No specific customer action committed. Flag: "The VP's enthusiasm and Sarah's 'we're definitely interested' are positive sentiment signals, not Advance commitments. 'Let's circle back after we've had some time to digest' is a Continuation — no date, no agreed agenda, no access to additional stakeholders. Do not advance CRM stage. Use commitment-and-advance-planner to define a specific Advance objective before the next contact."