Loading...
Loading...
Found 13,836 Skills
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
DingTalk Workspace CLI (dws) - officially open-sourced cross-platform CLI tool from DingTalk. Provides 86 commands across 12 products: Contact, Chat, Bot, Calendar, Todo, Approval, Attendance, Ding, Report, AITable, Workbench, DevDoc. Built in Go with zero-trust security architecture. Use when user wants to operate DingTalk resources.
Baidu Web Search skill for real-time Chinese web information retrieval. Breaks through static knowledge base limitations to get the latest news and information. Use when user needs to search the Chinese web for current information.
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Extract self-contained static HTML from a built web application or React components by inlining CSS and images. Use this skill whenever you need to capture a specific UI state, share a static version of a page, or prepare assets for Stitch upload, even if the user just asks to 'save the HTML' or 'mock the view'.
Create New Skill - scaffolds a skill definition following Claude Code conventions and this repository's patterns. Use when adding a new skill.
The always-on protocol for the loam skill namespace. Use at session start and whenever a loam task appears. Routes goals and other loam work, explains the memory model (memory = umbrella; wiki, guidance, and checkpoints are substrates), and lists cross-cutting rules. This is a routing/meta skill — delegate to a specific loam skill rather than performing work itself.
All-in-one skill for CLAUDE.md files. Two modes: `audit` finds drift (claimed facts no longer matching code), leaked secrets, duplicates, instruction-budget bloat, and prescriptive-vs-descriptive imbalance across all CLAUDE.md files in your projects. `improve` measures one CLAUDE.md against Anthropic's official best practices (200-line budget, removability test, emphasis tuning, 3-tier hierarchy) plus community-validated guidance, then proposes concrete rewrite diffs applied only after user approval. Default behavior auto-detects: in a project with a CLAUDE.md → improve mode; otherwise → audit all. Use when: 'audit claude.md', 'check claude md drift', 'lint CLAUDE.md', 'claude md audit', 'refresh instructions', 'improve CLAUDE.md', 'restructure CLAUDE.md', 'tune CLAUDE.md', 'apply CLAUDE.md best practices', 'is my CLAUDE.md good', 'CLAUDE.md is too long', 'rebalance CLAUDE.md', or quarterly as a hygiene check.
Expert, skeptical business analyst for a business / startup / product idea. Grills the user about the idea (one round of pointed questions at a time), then runs deep market research in the home country (default Brazil) and internationally — TAM/SAM/SOM, competitors, demand evidence, pricing, regulation, costs — builds a financial model with pessimistic / realistic / optimistic scenarios (cost to run, users needed to break even, cash needed), issues a critical verdict (GO / VALIDATE-FIRST / PIVOT / KILL) and saves a complete dossier to ideas/<slug>/. Use it whenever the user describes a business idea, startup, SaaS, app, marketplace, side project, "estou pensando em fazer X", and wants to know if it is viable, how big the market is, who the competitors are, what it would cost, how many customers they need, or asks to validate / stress-test / grill / roast / "analisa essa ideia" / "vale a pena?" — even when they don't say "validate". Not for code or architecture reviews (use grill-me / grilling) and not for writing pitch decks.
Save durable knowledge into the Trove memory graph — new facts, decisions, gotchas, AND corrections to known facts. Replaces the old trove-capture and trove-update skills; the remember tool handles create-vs-revise itself. Trigger after a session produced insight worth keeping, when the user states a fact or preference to remember, or when a known fact changed (PR merged, port moved, X replaced Y).
Use when a question should be answered from the Trove memory graph rather than re-derived - prior projects, decisions, system knowledge, preferences, "what was I working on". Routes grep → read → recall by query shape (exact string, known slug, open question), synthesizes with citations, and remembers non-trivial answers back so exploration compounds.
Star the ax repo, file an issue / bug report, or fork-and-open-a-PR against github.com/Necmttn/ax on the user's behalf, by shelling out to the `gh` CLI. Triggers when the user says "star ax", "star the repo", "I want to support ax", "report this as an ax bug", "file an ax issue", "open an issue on ax", "this looks like an ax bug", "I want to contribute to ax", "fix this in ax", "open a PR against ax", or after an unhandled ax error when the user wants to report it. Acts only on an explicit user request - proactive star prompting is handled deterministically by the CLI (`ax star`), not this skill. Confirms before any account-mutating action (never stars without an explicit yes); falls back to a plain GitHub URL when `gh` is missing or unauthenticated. Do NOT auto-trigger on unrelated GitHub work or other repos.