Loading...
Loading...
Found 849 Skills
Strategic GTM tracking planning with product manager expertise. Use when users need to plan tracking strategy, define what metrics to measure, understand business impact of tracking, create tracking specifications, or need guidance on "what should I track?" questions. Asks discovery questions about business goals, maps objectives to events, defines event taxonomy, and creates structured tracking plans. Trigger on - "plan GTM tracking", "what should I track", "create tracking plan", "define measurement strategy", "GTM strategy".
Skill for using Fabro, the open source AI coding workflow orchestrator that lets you define agent pipelines as Graphviz DOT graphs with human gates, multi-model routing, and cloud sandboxes.
P10 CTO mode — define strategic direction, design org topology, manage P9 teams. Use when user says 'CTO模式', 'P10', '战略规划', '架构委员会', or when facing cross-team architectural decisions. Produces: strategic input templates + org design.
Visualize whether skills, rules, and agent definitions are actually followed — auto-generates scenarios at 3 prompt strictness levels, runs agents, classifies behavioral sequences, and reports compliance rates with full tool call timelines
Guide a user through Stanford Biodesign's needs-finding process to define, scope, and refine a rigorous health-app need statement without jumping prematurely to solutions.
Behavioral compliance testing for any CLAUDE.md or agent definition file. Auto-generates test scenarios from your rules, runs them via LLM-as-judge scoring, and reports compliance. Optionally improves failing rules via automated mutation loop.
A library of creative mechanics — the structural patterns that define how an ad constructs meaning between its hook, visuals, and narrative. Use this whenever designing ad concepts, briefing creative, or trying to explain why a specific ad works beyond just its hook or format. Trigger when a user describes an ad they saw and wants to understand or replicate what made it work, when building a creative concept from a messaging angle, or when execution needs more than a hook and a format — it needs a structural idea. Creative mechanics sit between hooks and visual formats in the Creative Strategy Engine: hooks say what, formats show how, mechanics define the cognitive or emotional mechanism that makes the concept land. Always pair with Hook Writing for opening line execution and Hook Tactics for tactic classification.
Strategic framework for mapping pain/persona intersections and messaging angles. Defines the structure for organizing creative strategy, not the tactics for execution. Use this when planning an organizational or systematic approach to creative strategy, or when a user provides a product and wants to define messaging angles, write strategic hooks, or execute ads in visual formats defined by awareness and decision stages.
Model cloud-native applications with Radius using Bicep. Use when asked to create an application definition, scaffold app.bicep, configure environments, or create custom resource types.
Reference library of 35+ hook and headline tactic types. Use this when a user asks for hooks organized by tactic, wants to know which tactic to use for a given situation, or requests hooks "by tactic type." This defines what each tactic is and when to deploy it. Always pair with hook-writing for execution — tactics define the frame, psychological triggers are the mechanism inside the frame.
Build, refactor, or review macOS menubar apps that use Tuist and SwiftUI. Use when creating or maintaining LSUIElement menubar utilities, defining Tuist targets/manifests, implementing model-client-store-view architecture, adding script-based launch flows, or validating reliable local build/run behavior without Xcode-first workflows.
Design, weight, and tune a lead scoring model for your sales funnel. Use when building a lead scoring system, defining MQL/SQL criteria, assigning point values to lead attributes, setting up scoring in your CRM or MAP, tuning conversion thresholds, or deciding which signals should trigger sales follow-up. Do NOT use for reading existing buying signals (use /sales-intent), building prospect lists (use /sales-prospect-list), or marketing-to-sales handoff process design (use /revops).