Loading...
Loading...
Found 6,129 Skills
Build Temporal workflow applications in Go. Use when creating or modifying Temporal workflows, activities, workers, clients, signals, queries, updates, retry policies, saga patterns, or writing Temporal tests.
JazzHR integration. Manage data, records, and automate workflows. Use when the user wants to interact with JazzHR data.
Marketstack integration. Manage data, records, and automate workflows. Use when the user wants to interact with Marketstack data.
Vectara integration. Manage data, records, and automate workflows. Use when the user wants to interact with Vectara data.
Snowplow Analytics integration. Manage data, records, and automate workflows. Use when the user wants to interact with Snowplow Analytics data.
Forensic audit of the user's recent Claude Code sessions to surface step-change workflow improvements — not marginal ones. Use when the user asks to "audit my Claude Code sessions", "analyze how I use Claude Code", "find patterns in my usage", "improve my Claude Code workflow", "review my sessions", "find leverage in my setup", or wants to understand where their Claude Code setup is leaking time. Samples dozens of real transcripts, extracts quantitative signal via scripts, uses parallel subagents for deep reads, then synthesizes into a short prioritized report with drafted implementations (new skills, CLAUDE.md rules, hooks, settings diffs) that the user can install directly. Trigger even when the user doesn't say the word "audit" — if they're asking about improving or reviewing their Claude Code habits at scale, use this skill.
Timekit integration. Manage data, records, and automate workflows. Use when the user wants to interact with Timekit data.
Flespi integration. Manage data, records, and automate workflows. Use when the user wants to interact with Flespi data.
Slope integration. Manage data, records, and automate workflows. Use when the user wants to interact with Slope data.
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`.
Kandy integration. Manage data, records, and automate workflows. Use when the user wants to interact with Kandy data.
Router skill for LLMQuant portfolio workflows. Use when the user needs company profiles, thesis tracking, theme research, watchlist monitoring, or alert management.