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

Counterpart Style Profiler

by @quochungto

Profile a negotiation counterpart's communication style and generate a tailored adaptation strategy. Use when asking "how should I approach this person?", "w...

Versionv1.0.0

#legal #gaming #automation

⚡ When to Use

Trigger	Action
This skill works in two scenarios:
1. Pre-negotiation preparation: You have some information about the counterpart and want a communication blueprint before first contact or before a critical conversation.
2. Mid-negotiation diagnosis: A conversation has stalled, or your usual approach isn't working, and you need to identify why and adjust.
Do not use this skill if: You have no information about the counterpart whatsoever. The profile requires at least a few observable signals to be reliable. Proceed with the Analyst archetype defaults (data-driven, slow pace, minimal warmth) as a low-risk starting posture when blind.
---

💡 Examples

Example 1: Pricing Negotiation with a Procurement Manager

Scenario: A sales rep preparing for a final pricing negotiation with a procurement manager. The manager has sent three highly detailed emails with numbered questions, requested a full pricing breakdown with line items, took five days to respond to the last message, and opened the first meeting with "Let's get right to the numbers."

Trigger: "How should I approach this negotiation? He's very analytical but also seems impatient."

Process:

Step 1: Signals — detailed numbered questions (directness, information style), full pricing breakdown requested (data preference), 5-day response time (deliberate pace), "get right to the numbers" (time-efficient, task-focused)

Step 2: Analyst=4 (data-driven, detailed, deliberate pace), Assertive=3 (direct opener, time-efficiency signal), Accommodator=1 (no warmth signals)

Step 3: Primary type: Analyst with Assertive secondary — classify as Analyst-Assertive blend

Step 4: User self-identifies as Accommodator → projection risk: user will want to build warmth before numbers; counterpart wants numbers immediately

Step 5: Tempo — be prompt but don't rush decision. Information — lead with a complete pricing breakdown before the meeting, not in response to pushback. Relationship — skip extended small talk; open with "I've prepared the full breakdown you asked for." Risk — don't interpret slow response time as doubt; don't pad with warmth that reads as evasion

Output: counterpart-profile.md classifying as Analyst-Assertive blend, adaptation strategy leading with data delivery, projection risk warning for Accommodator user, language examples ("Here's the complete breakdown — happy to walk through any line item you want to dig into" vs. avoid "I just want to make sure we have a good relationship here before we get into numbers").

Example 2: Salary Negotiation with a Hiring Manager

Scenario: A candidate preparing for salary negotiation with a hiring manager who has been very friendly throughout the interview process, asked personal questions about the candidate's family and career journey, said "I'm sure we can make this work" multiple times, but has not yet made a concrete offer after three conversations.

Trigger: "She keeps saying yes but nothing is moving. How should I approach asking for a number?"

Process:

Step 1: Signals — personal questions (high warmth), "sure we can make this work" (verbal agreement without commitment), three conversations without concrete offer (avoidance of conflict), friendly throughout (relationship emphasis)

Step 2: Accommodator=5 (all signals match), Analyst=1 (no data or deliberation signals), Assertive=1 (no directness or pace signals)

Step 3: Primary type: Accommodator (high confidence)

Step 4: User self-identifies as Analyst → projection risk: user may over-explain rationale and data for the salary ask; the manager needs to feel the relationship is good before committing

Step 5: Tempo — allow relationship talk before business; don't rush. Information delivery — frame the ask in terms of the relationship and mutual success, not market data. Relationship — acknowledge the warmth explicitly before making the ask. Risk — verbal "yes" from an Accommodator is not a commitment; close with a specific follow-up: "So can we agree to [specific number] and have an offer letter by [date]?" Silence means something is wrong — check in.

Output: counterpart-profile.md classifying as Accommodator, adaptation strategy prioritizing relationship acknowledgment before the ask, specific language for closing ("I really appreciate how collaborative this process has been — I'd love to confirm the number and timeline so I can get excited about next steps"), and explicit warning that "I'm sure we can make this work" is not a commitment.

Example 3: Partnership Negotiation with a Co-founder

Scenario: A founder trying to negotiate equity terms with a potential co-founder. The potential co-founder responds to messages within minutes, jumps to conclusions quickly, stated his equity expectations in the first meeting ("I need at least 30%"), interrupted twice when the founder was explaining the rationale, and pushed back hard when the founder said "let me think about it."

Trigger: "Every time I try to explain my reasoning, he cuts me off. What am I doing wrong?"

Process:

Step 1: Signals — minute-level response time (fast pace), stated position immediately (direct, no preamble), interrupted twice (impatient with build-up), pushed back on "let me think about it" (time-is-money, wants momentum)

Step 2: Assertive=5 (all signals match strongly), Analyst=1, Accommodator=1

Step 3: Primary type: Assertive (high confidence)

Step 4: User self-identifies as Analyst → projection risk: user's instinct to explain full rationale before stating position is exactly what causes the interruptions

Step 5: Tempo — respond quickly, match his pace. Information delivery — lead with the number, offer rationale only if asked. Relationship — respect is earned by being direct and holding a position, not by explaining it. Risk — do not launch into rationale before acknowledging his 30% position; use a label first: "It sounds like you see your contribution as worth 30% of the outcome — I want to make sure I understand what's driving that before responding." Then state your position directly.

Output: counterpart-profile.md classifying as Assertive, adaptation strategy emphasizing label-first approach before counter-positions, explicit example language ("It sounds like timeline is the main concern — here's what I can do on that"), and projection risk warning for the Analyst user to front-load conclusion, not rationale.

View on ClawHub

TERMINAL

clawhub install bookforge-counterpart-style-profiler