Loading...
Loading...
Found 506 Skills
Write, rewrite, or normalize structured `*.spec.md` specification files for agent-driven development. Use this whenever the user asks for a spec, requirements, acceptance criteria, implementation-ready documentation, feature definition before coding, or wants an existing idea/codebase turned into an actionable spec, even if they do not explicitly say "spec".
Audit and evolve the brain vault - prune outdated content, discover cross-cutting principles, review skills for structural encoding opportunities. Triggers: "meditate", "audit the brain".
Curated list of Claude Skills, resources, and tools for customizing Claude AI workflows and agentic coding
Wren Engine CLI workflow guide for AI agents. Answer data questions end-to-end using the wren CLI: gather schema context, recall past queries, write SQL through the MDL semantic layer, execute, and learn from confirmed results. Use when: user asks a data question, requests a report or analysis, asks about metrics, revenue, customers, orders, trends, or any business data; user says 'how many', 'show me', 'what is the', 'top N', 'compare', 'trend', 'growth', 'breakdown'; user wants to explore, analyze, filter, aggregate, or summarize data from a database; agent needs to query data, connect a data source, handle errors, or manage MDL changes via the wren CLI.
Create and manage agent graphs — directed graphs of configs connected by edges with handoff logic. Use when building multi-agent workflows where configs route to each other.
This skill should be used when the user asks to "fix my skill" or "audit this skill". Make sure to use this skill whenever the user mentions skill quality, structural issues, broken skills, or skill diagnostics — even if they don't explicitly say "repair-skill". Not for adding features or improving effectiveness — use improve-skill. Not for agents — use repair-agent.
Validate and auto-repair YAML frontmatter on brain pages. Catches malformed pages before they enter the brain (missing closing
A-share Market Daily Review System. Actively invoked when users mention needs such as market review, market analysis, or tomorrow's market prediction. Covers: Market Environment, Sentiment Cycle, Main Line Identification, Capital Monitoring, Post-Market Variables, Tomorrow's Combat Map. For research reference only, does not constitute securities investment consulting business or investment advice.
Use at the start of any conversation—establishes how to find and use skills, requiring the Skill tool to be called before any response (including clarifying questions)
Share markdown reports to the user's configured Slack agent_cli_report channel via Fastfold API, and persist the markdown as a library item.
THE workflow for picking up and carrying ONE ticket/card forward, for an autonomous worker agent or for a human doing it locally. Resolves the repo's tracker from the AFK registry (~/.claude/afk.json; GitHub Projects or Linear), picks one ticket by priority, routes by status x label (interview / human walkthrough / execute), loads LEARNINGS.md as binding constraints, implements test-first, verifies end-to-end and simplifies the diff (the /go finish), then branches to a PR for the reviewer. Use when the user says "pick up <id>", "work on issue <id>", invokes /engineer, invokes /pickup, says "pickup", or at the very start of working any card.
原始人スタイル subagent への委譲判断ガイド。`genshijin-investigator` (コード位置特定)、 `genshijin-builder` (1-2ファイル編集)、`genshijin-reviewer` (diff レビュー) を inline作業 or vanilla `Explore` の代わりにスポーンするタイミングを示す。subagent 出力は原始人圧縮 → 主コンテキストに戻る tool-result が約60%縮小 → 長セッション持続。 Trigger: 「subagent 委譲」「genshijin-crew 使用」「investigator/builder/reviewer 起動」「コンテキスト節約」「圧縮 agent 出力」。