Loading...
Loading...
Found 1,517 Skills
Primarily the agent's internal-thinking skill — invoke it silently to model a problem, identify trade-offs, and decide what to do, BEFORE asking the user anything or dispatching another skill. Workflow skills call `/culture` as their step-1 reasoning pass; the agent does not surface the dialogue. Only treat this as a user-facing skill when the user has explicitly opted out of writes — phrases like "no writes", "just rubber-duck this", "let's only talk", "/culture". In the user-facing path the output is conversation; the only sanctioned artifact is an opt-in `.cheese/notes/<slug>.md` handoff slug at session end if the user asks for notes. Culture never writes to production code, never commits, never opens PRs. If the dialogue reveals real work, recommend `/mold` (fuzzy → spec) or `/cook` (clear ask → code) and stop. Before `/mold` or `/cook`.
This skill should be used when the user asks about Mermaid diagram syntax, how to write flowchart, sequence, class, state, ER, Gantt, C4, mindmap, timeline, or other diagram types, node shapes, styling, theming, or rendering errors.
Rank outreach campaigns by real revenue impact — which campaigns actually generated deals, pipeline, or meetings — by cross-referencing the user's La Growth Machine campaign data with their CRM deal data (HubSpot today). Use whenever the user wants to know which campaigns drove pipeline, compare campaign ROI, see which campaigns to continue / stop / adapt, audit campaign impact, review attribution, asks 'which of my campaigns is actually working', or wants a campaign performance ranking by deals or revenue. Triggers on: 'which campaigns drove pipeline', 'rank my campaigns by deals', 'campaign ROI', 'campaign impact', 'which campaigns to stop', 'which to scale', 'attribution review', 'pipeline by campaign'. Pulls live data from the La Growth Machine MCP and the HubSpot MCP when connected; works from pasted exports otherwise. For RevOps, Heads of Sales/Marketing, founders and growth leads doing campaign performance reviews. Maintained by La Growth Machine.
A shared, file-based town square where multiple coding agents talk, coordinate, and debate — no server required. Use whenever more than one agent works the same repo (parallel Claude Code or Codex sessions, separate git worktrees, a fleet splitting a task) and they must stay out of each other's way or think together. TRIGGER on phrasings like "coordinate with the other agent/session", "post to / check the agora", "ask the other agents", "leave a message for whoever's working on X", "announce what files you're touching", "is anyone else editing this?", or any time you're about to edit shared code while other agents are live. Also trigger when an agent is stuck and wants a peer's second opinion, or when several agents each drafted a design (an API, a schema, an architecture) and the group needs to compare the proposals and converge on the best one. Works for any agent that can run a Python script, not just Claude Code.
Pressure-tests a product idea before the founder invests in planning, building, or launching. Surfaces fatal flaws, tests whether the problem is real, maps real competition (including current behavior), plans first 10 customers, defines a 2-week MVP test, returns a strong/weak/pivot verdict, then sharpens `docs/product-idea.md` based on the founder's direction calls. Use when the founder says "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "stress test my idea", or otherwise wants to evaluate an idea before committing.
Provision and migrate Fusion databases using the fusion-infra-cli (finf). USE FOR: provision a database for a service, run SQL migrations, provision PR-specific ephemeral databases, check database state. DO NOT USE FOR: application code changes, service deployments, role management, or infrastructure other than databases.
Split Markdown documents into paragraph blocks with stable IDs and hashes, only replace blocks approved by the user, and output the retention ratio, modification reasons, and issue tracking report. Use when the user asks for "only modify these paragraphs", "partial modification according to review comments", "keep other content unchanged", "generate reviewable modification patch", or requests the rw-revision-patch workflow.
Use when interacting with Unity CLI from the terminal — install, upgrade or uninstall editors, create, list or open projects, manage modules, manage licenses, check auth status, read logs, browse Unity releases, build/test projects, configure the Unity MCP server for AI agents, or run any other Unity CLI operation. For a guided idea-to-running-project flow for a brand-new game, use the new-unity-project skill instead.
Guides agents to discover requirements and design a governed, secure borderless open data lakehouse with agentic AI integration. Use when designing a multi-product architecture that connects data silos to AI agents, joining data across clouds, or running federated queries across Google Cloud and external data sources, including on-premises or other cloud providers. Don't use for simple single-cloud data warehouses or non-AI workloads.
Use when the user wants to query Lore git trailers from commit history — surface constraints, rejected alternatives, directives, test gaps, and other decision context. Triggers on "최근 제약조건 확인", "리젝된 대안 보여줘", "check recent constraints", "show directives", or explicit skill invocation (/lore-query in Claude Code, $lore-query in Codex CLI, /skill:lore-query in Kimi Code, lore-query in Qwen Code).
Connect to SageMaker Managed MLflow (mlflow-app or mlflow-tracking-server ARN) as an MLflow backend, then hand off to the other MLflow skills. Triggers on a SageMaker MLflow ARN (arn:aws:sagemaker:...:mlflow-app/... or arn:aws:sagemaker:...:mlflow-tracking-server/...) or "SageMaker Managed MLflow".
Use the public `orca` CLI to operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, worktree comments, and the browser embedded inside the Orca app. Use when the user says "$orca-cli", "use orca cli", "Orca worktree", "child worktree", "cardStatus", "spawn codex/claude in a worktree", "read/wait/send Orca terminal", "terminal send", "full handoff", "handover", "give this to another agent", "another worktree", "Orca browser", "orca artifacts", "share HTML/Markdown", "public artifact link", or "control the browser inside Orca". Prefer this over raw `git worktree`, ad hoc PTYs, Playwright, or Computer Use when the task touches Orca-managed state. Use Computer Use for browser windows, webviews, or desktop UI outside Orca's embedded browser.