Loading...
Loading...
Found 307 Skills
Do the work. Pre-flight, build, detect drift, salvage if needed. Use when you have a clear aim and are ready to implement.
Interact with Notion using the unofficial private API - pages, databases, blocks, search, users, comments
Store a lesson learned from the current conversation. Triggered by /lesson command. Use when Master signals that the recent conversation contains a pitfall, fix, or key insight that should be persisted to long-term memory.
Read Figma designs via Figma MCP server. Auto-detects MCP availability and prompts user only if setup is needed. Use when Figma links or UI design images are found in task context.
Coordinates multi-session, delegated, or long-running work with persistent state, recovery checks, and explicit status transitions. Use when a task spans multiple turns, multiple agents, background jobs, or scheduled loops, or when interrupted work must be resumed reliably.
Real-time analytics with Redis counters, periodic PostgreSQL flush, and time-series aggregation. High-performance event tracking without database bottlenecks.
Harness Engineering Phase 3: Establish cross-session state management to solve the problem of agents forgetting previous conversations. Create three files: tasks.json (task list), progress.md (progress record), and init.sh (environment initialization script). Use this skill immediately when the user says phrases like "establish task management", "make agent remember progress", "create tasks.json", "maintain state across sessions", "agent doesn't remember what was done last time", "create progress file", or "initialize state management". Prerequisites: harness-step1 and harness-step2 have been completed (the project has AGENTS.md and docs/ knowledge base).
Explicitly save an insight, decision, or learning to agentmemory's long-term storage. Use when the user says "remember this", "save this", or wants to preserve knowledge for future sessions.
Use when you need to turn a vague idea into a confirmed design spec before implementation (new feature/component/behavior change). First check project context, then ask one question at a time, provide 2-3 options with trade-offs, finally output design in segments (~200-300 words each) with confirmation after each. Triggers: brainstorm, clarify idea, design spec, refine concept, requirement clarification.
Extract learning before restarting. Code is a draft; learning is the asset. Use when work is drifting, approach has reversed 3+ times, or scope is expanding while "done" keeps fuzzing.
Agent harness performance system for Claude Code and other AI coding agents — skills, instincts, memory, hooks, commands, and security scanning
Pre-publish verification gauntlet for Roblox games