
Invisible git layer for non-technical users. Handles commits, pushes, pulls, branching, and conflict resolution automatically — surfacing decisions only when human judgment is required, in plain business language with no git jargon. ALWAYS activate this skill when working with a non-technical user in a GitHub repo. Also activate when the user says "save my work," "send for review," "what changed," "am I up to date," or "publish my changes."
Reference guide for the Agentic Mesh framework (Falconer, O'Reilly 2025). Covers agent architecture, mesh platform design, trust frameworks, operating models, and implementation roadmaps. Use when: discussing agentic mesh concepts, designing agent ecosystems, planning mesh infrastructure, referencing agent patterns (communication, role, organizational), understanding trust/security/governance for agents, building agent factories, or implementing the Agonda methodology. Triggers: agentic mesh, agent architecture, agent ecosystem, mesh platform, trust framework, agent factory, agent fleet, agentic quantum, microagent, agent registry, agent lifecycle, agent patterns, mesh governance, agent operations
When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
Transform rough ideas into clear, engaging writing using Gary Provost's rhythm and structure principles. Use when the user needs help writing emails, tweets, scripts, sales copy, articles, or any content where readability, flow, and digestibility matter. Ideal for entrepreneurs and content creators who want to turn ideas into professional writing without sounding robotic or over-polished. Apply when the user asks for help writing, editing for clarity, improving pacing, or making content more engaging.
Reference skill for Claude Code plugin and hook authoring. Covers plugin.json schema, all 15 hook events, exit code semantics, matchers, environment variables, caching behavior, and proven Agonda patterns. Use when designing hooks, scaffolding plugins, validating hook configuration, or debugging hook behavior. Not a workflow — a knowledge base that other skills reference.
Guide for authoring skills in the Agonda system. Covers two skill templates (CLI/API and knowledge processing), YAML frontmatter spec, progressive disclosure patterns, config management, and shipping checklists. Use when creating a new skill, validating skill structure, or understanding skill conventions.
Detect B2B buying signals for prospect companies. Analyzes companies across web/news, landing pages, social media and scores them by buying intent (HOT/WARM/COOL/COLD). Use for: prospect scoring, lead qualification, outbound sales research, GTM signal detection. Triggers: buying signals, analyze company, score prospects, buying intent, lead scoring, signal detection, sales intelligence, prospect research, company analysis, outbound signals, GTM signals, warm leads, hot leads
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.
Generate beautiful, self-contained HTML pages that visually explain systems, code changes, plans, and data. Use when the user asks for a diagram, architecture overview, diff review, plan review, project recap, comparison table, or any visual explanation of technical concepts. Also use proactively when you are about to render a complex ASCII table (4+ rows or 3+ columns) — present it as a styled HTML page instead.