DOCSEARCHbyAlgolia
Submit Docs

Wondel.ai Agent Skills

repository·main·Indexed 23 days ago

https://github.com/wondelai/skills

A collection of 62 expert frameworks from bestselling books across Business, Marketing, UX, and Coding designed for AI agents like Claude, Cursor, and Codex. It features individual skills based on industry standards and 'metaskills'—stateful, guided journeys that orchestrate these frameworks to help users build, improve, or grow products and codebases.

Tokens
355.3K
Snippets
404
Records
1.3K
Agent score
82%

What's inside wondelai-skills

  1. Complete the Referral Systems implementation checklist

    main

    Use this checklist to ensure your referral system is fully operational:

    • Referral program is designed with trigger, mechanism, and two-sided incentive
    • Referral ask scripts are written and the team is trained on them
    • Referrals are asked for at the moment of peak satisfaction (not randomly)
    • Referral mechanism is simple (one click, one card, one introduction)
    • At least one strategic partnership is active and generating referrals
    • Partner evaluation matrix has been used to identify and prioritize new partnerships
    • Affiliate program is in place (if appropriate for the business model)
    • All referral sources are tracked using at least two methods
    • Referral dashboard is reviewed monthly
    • Top referrers are recognized and rewarded beyond standard incentives
    • "How did you hear about us?" is captured for every new lead and customer

  2. Use the hundred-million-offers skill for offer creation

    main

    The hundred-million-offers skill provides a framework for creating irresistible offers using the Value Equation, bonus stacking, risk-reversing guarantees, and ethical scarcity.

    Triggering the skill: This skill is designed to be used when a user mentions:

    • "grand slam offer"
    • "make my offer more compelling"
    • "what bonuses should I add"
    • "guarantee strategy"
    • "offer naming"
    • "people say its too expensive"

    It is also applicable when:

    • Packaging a product for higher perceived value.
    • Justifying premium pricing instead of discounting.
    • Designing a money-back guarantee.
    • Structuring tiers to maximize conversions.

    Related Frameworks:

    • For product positioning, use obviously-awesome.
    • For outbound sales, use predictable-revenue.

  3. Use the high-perf-browser skill for web performance optimization

    main

    The high-perf-browser skill provides a systematic approach to optimizing web performance by focusing on network protocols, resource loading, and browser rendering internals.

    Triggering scenarios: Use this skill when addressing issues related to:

    • Slow site performance or slow page loads.
    • Core Web Vitals optimization.
    • Network protocols (HTTP/2, HTTP/3, TCP/TLS optimization, network latency).
    • Resource loading (resource hints, render-blocking, critical rendering path, bundle sizes).
    • Caching (Cache-Control, caching strategies, service workers).
    • Real-time communication (choosing between WebSocket and SSE).
    • Time to First Byte (TTFB) optimization.

    Related skills:

    • For UI visual performance, use refactoring-ui.
    • For font loading, use web-typography.

  4. Use the Scorecard Marketing Skill

    main

    The scorecard-marketing skill is used to build quiz and assessment funnels that generate qualified leads. Trigger this skill when a user mentions terms like "quiz funnel", "scorecard", "lead magnet", "score-based segmentation", or "lead qualification". It is also applicable when designing self-assessment tools, marketing calculators, graders, or personalized result pages.

    This skill covers:

    • Concept hooks and question design
    • Dynamic results based on scoring tiers
    • Automated follow-up sequences
    • Landing page conversion strategies

    For specific landing page conversion techniques, refer to cro-methodology. For comprehensive marketing plans, refer to one-page-marketing.

  5. Use the Good Strategy Bad Strategy skill

    main

    The good-strategy-bad-strategy skill is a framework for formulating and auditing strategy based on Richard Rumelt's work. It focuses on replacing goal lists and vision statements with a 'kernel' consisting of an honest diagnosis, a guiding policy, and coherent actions.

    Trigger Keywords

    You can trigger this skill by mentioning:

    • good strategy bad strategy
    • strategy kernel
    • diagnosis guiding policy coherent action
    • our strategy is just goals
    • strategic planning
    • mission vs strategy
    • annual plan
    • is this actually a strategy

    Use Cases

    • Auditing: Review strategy documents or pitch decks for fluff and bad strategy hallmarks.
    • Formulation: Turn a list of goals into a real strategy for a product or company.
    • Optimization: Find leverage points and proximate objectives.

    Note: For product positioning, use obviously-awesome. For uncontested markets, use blue-ocean-strategy.

  6. Use the High Output Management skill

    main

    The high-output-management skill implements Andy Grove's management framework. It is designed to help users manage for output by focusing on high-leverage activities.

    Triggering Keywords: Use this skill when discussing:

    • "high output management"
    • "managerial leverage"
    • "one-on-ones" or "1:1 agenda"
    • "OKRs"
    • "performance review"
    • "task-relevant maturity"
    • "delegation"
    • "meeting overload"
    • "new manager"
    • "how do I run a 1:1"
    • "just got promoted to manager"

    Use Cases:

    • Structuring a manager's calendar and meeting cadence.
    • Designing team metrics.
    • Running planning sessions.
    • Coaching delegation.
    • Preparing performance reviews.

    Note: For intrinsic motivation, use drive-motivation. For a company operating system, use traction-eos.

  7. Use the hooked-ux skill for habit-forming product design

    main

    The hooked-ux skill is a framework for designing product loops that move users from deliberate usage to automatic habits using the Hook Model.

    Use this skill when discussing:

    • User retention issues ("users aren't coming back")
    • Habit formation or engagement loops
    • Designing notification or re-engagement strategies
    • Building streaks or progress systems
    • Analyzing why users drop off after signup
    • Ethical evaluations of engagement mechanics

    Core Loop Structure: Trigger → Action → Variable Reward → Investment (where Investment loads the next Trigger).

    Note: For friction reduction specifically, see improve-retention. For viral sharing, see contagious.

    name: hooked-ux
description: 'Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment). Use when the user mentions "users arent coming back", "habit formation", "engagement loops", "habit zone", or "the manipulation matrix". Also trigger when designing notification or re-engagement strategies, building streaks or progress systems, or analyzing why users stop after signup. Covers ethics evaluation and onboarding for habits. For friction reduction and B=MAP, see improve-retention. For viral sharing, see contagious.'

  8. Use the Clean Code Framework for code quality and refactoring

    main

    The clean-code skill is a disciplined approach to writing readable, maintainable code. It is designed to be triggered when you need to clean up code, address long functions, resolve code smells, improve naming conventions, or enhance unit test quality. It covers principles like Single Responsibility (SRP), comment discipline, formatting, and error-handling patterns.

    When to use this skill:

    • When mentioning "clean up this code", "this function is too long", "code smells", "naming conventions", "boy scout rule", "single responsibility", or "unit test quality".
    • When reviewing pull requests for readability.
    • When untangling messy functions or debating comment styles.
    • When improving error-handling patterns.

    Note: For specific refactoring techniques, refer to refactoring-patterns. For architecture and dependency rules, refer to clean-architecture.

  9. What is the ERRC Grid (Four Actions Framework)?

    main

    The Eliminate-Reduce-Raise-Create (ERRC) grid is a strategic tool used to translate Blue Ocean thinking into concrete actions. It aims to achieve differentiation and low cost simultaneously by challenging industry logic through four specific questions.

    By applying these four actions, a company can pursue Value Innovation: a state where costs are driven down (via Elimination and Reduction) while buyer value is driven up (via Raising and Creating).

  10. What is a seam and why use them for legacy code?

    main

    A seam is a place where you can alter program behavior without editing the code at that specific location. Every seam has an enabling point: the location where you decide which behavior runs.

    In legacy code testing, seams are used to substitute slow, global, or external dependencies with fakes while keeping the production source code untouched. This ensures that your characterization tests are honest—you are testing the exact code that runs in production, rather than a modified version you created just to make it testable.

  11. What is Ubiquitous Language in DDD?

    main

    Ubiquitous Language is a core Domain-Driven Design (DDD) practice where developers and domain experts use a shared, precise vocabulary across all forms of communication: conversations, documentation, code, tests, and diagrams.

    It is not a static glossary, but a living language that shapes the system's architecture. The goal is to eliminate the 'cost of translation'—the mental overhead and errors that occur when developers use technical terms (e.g., UserEntity, processData(), status = 3) that do not align with the business reality (e.g., Policyholder, adjudicateClaim(), status = 'Active').

  12. What is an Aggregate and how do they work?

    main

    An Aggregate is a cluster of domain objects (entities and value objects) treated as a single unit for data changes. Every aggregate has a single root entity, known as the Aggregate Root, which serves as the sole entry point for all external access.

    Core Concepts

    • Inside the boundary: Strong consistency. All business invariants (rules that must always be true) are enforced within a single transaction.
    • Outside the boundary: Eventual consistency. Changes to other parts of the system propagate via domain events or polling.

    The Aggregate Root Pattern

    The Aggregate Root is the single entity through which all external interaction occurs. To maintain integrity, follow these rules:

    1. External objects may only hold references to the root, never to internal entities.
    2. All changes to the aggregate must go through the root's methods.
    3. The root enforces all aggregate invariants.
    4. The root controls the lifecycle of all internal objects.
    5. Deleting the root deletes everything inside the aggregate.
    // External code interacts only with Order (the root)
order.addLineItem(product, quantity, price)
order.removeLineItem(lineItemId)
order.calculateTotal()

// LineItems are never accessed directly from outside
// WRONG: lineItem.changeQuantity(5)
// RIGHT: order.changeLineItemQuantity(lineItemId, 5)