Loading...
Loading...
Found 6,047 Skills
Extract knowledge from closed tasks and archive context
DingTalk Address Book and Contact Query. Use this skill when the user mentions terms like "DingTalk address book", "find employee", "search user", "check user info", "get user details", "user phone number", "employee name", "employee ID", "check department", "search department", "department members", "department list", "department details", "sub-department", "parent department", "department path", "total number of employees", "address book search", "userId to unionId", "unionId to userId", "dingtalk contact", "dingtalk directory", "find user", "get user info", "department members". Supported operations: search users/departments by keyword, get complete user information (name/phone/employee ID/department/position/unionId), get department member list, get department tree structure, query user's department path, count total number of employees, and all other address book operations.
This skill implements a specific task from a project's ROADMAP.md file. It should be used when the user wants to work on a roadmap action item by its ID (e.g., '1.1', '2.3'). Triggered by requests like '/do-task 1.1', '/do-task 2.3', or 'do task 3.1'. Works alongside the project-init skill (which creates the roadmap) and the checkpoint skill (which commits afterward).
Run, monitor, resume, merge, and debug Ralph loops. Use this skill whenever the user asks to operate `ralph run` or `ralph loops`, inspect loop state, recover suspended loops, analyze diagnostics, or unblock merge queue issues.
Verify AI claims against source documents using the DeepCitation API
Add new or remove obsolete model IDs for existing AI SDK providers. Use when adding a model to a provider, removing an obsolete model, or processing a list of model changes from an issue. Triggers on "add model", "remove model", "new model ID", "obsolete model", "update model IDs".
Automatically create a PR to register insights, conventions, and best practices obtained from the current project as rules in the TBSten/skills repository. It runs the entire end-to-end process: collecting insights from the project's CLAUDE.md, .claude/rules/ directory and codebase, packaging them as reusable Claude Code rules, and creating the PR. Rules are files stored in .claude/rules/, and unlike skills, they do not require frontmatter. RULE.md serves as the main rule body, while detailed documentation (<rule-name>.md / <rule-name>.ja.md) is placed directly under the rules/ directory. Use when the user requests: "Register insights as rules", "contribute rule", "Share this rule", "Register as a rule", "Compile rules into a PR", "Turn this convention into a rule", "Turn best practices into rules". gh CLI and git must be installed.
Qwilr integration. Manage Accounts. Use when the user wants to interact with Qwilr data.
Kite Suite integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Kite Suite data.
Paymo integration. Manage Organizations, Pipelines, Leads, Users, Goals, Filters. Use when the user wants to interact with Paymo data.
Implement tasks from a working change. Use when the user wants to start implementing, continue implementation, or work through planned tasks.
Enter this sub-process when conducting code optimization — handle tasks where 'behavior remains unchanged, structure changes' (structure / performance / readability). Shift single-module internal optimization from 'AI random refactoring' to 'first scan to generate a checklist, confirm each item with the user, execute step-by-step according to the method library, and require manual approval for each step'. Trigger scenarios: Users mention phrases like 'optimize it / refactor / rewrite / split it / poor performance / code is too long' without any accompanying behavior changes. Do not handle new requirements (route to feature), bugs (route to issue), or cross-module architecture restructuring (route to architecture + decisions).