Loading...
Loading...
Found 9,706 Skills
Run agentlint CLI after code changes to catch patterns for AI evaluation. Activate when finishing code modifications, before committing, or when the developer asks to lint, scan, or review code with agentlint. Covers agentlint check, agentlint list, agentlint review, agentlint init, inline suppression, and output interpretation.
Create new skills for the lovstudio/skills repo. Fork of the official skill-creator with lovstudio conventions: lovstudio: name prefix, skills/lovstudio-<name>/ directory structure, mandatory README.md per skill, SKILL.md with AskUserQuestion interactive flow, standalone Python CLI scripts, CJK text handling, and auto-update of root README + CLAUDE.md. Use when the user wants to create a new skill, add a skill to this repo, scaffold a skill, or mentions "新建skill", "创建skill", "new skill", "add skill", "生成skill".
NetEase Cloud Music skill for searching songs, managing playlists, getting personalized recommendations, and controlling playback via ncm-cli. Use when user wants to search music, play songs, manage playlists, or get music recommendations.
Core Catalyst project setup — directory structure, environments, CLI commands, and all Catalyst IDs (Project ID, ZAID, Table ID, Segment ID, Org ID). Trigger on 'start a Catalyst project', 'what is .catalystrc', 'where do I find my Table ID', 'difference between Development and Production', or any Catalyst ID or CLI question.
Use and read this skill immediately if the user request is in any way related to SEO or a site's organic search or AI search presence. That includes site audits, rankings, keyword research, competitors, backlinks, click or traffic changes, indexing problems, crawling, redirects, sitemaps, metadata, structured data, Core Web Vitals, internal links, content opportunities, programmatic SEO, local search, Search Console, Google Analytics or Clicky questions, Google update impact, llms.txt, AI search visibility in ChatGPT, Claude, Perplexity, or Google AI Overviews, and client SEO reporting. Routes to evidence-backed local reports through the SEO CLI and MCP server.
File new notes into the right folder and audit/reorganize folder structure in the user's Obsidian vault, using the `obsidian` CLI and a single source-of-truth map note (`00_Index/Folder_Map.md`) that lives inside the vault. Use this whenever a note needs to be placed, filed, sorted, or moved into the vault; whenever the user asks where a note "belongs" or "should go"; and whenever they want to clean up, reorganize, deduplicate, audit, or restructure vault folders (e.g. orphaned notes, dead-end notes, near-duplicate titles, overlapping folders). Trigger even when the user just says "add this to my vault", "put this somewhere sensible", or "tidy up the cellchat notes" without naming a folder. Requires the Obsidian desktop app to be running.
Use when the user asks anything about blockchain wallets, transactions, signing, token transfers, supported chains, wallet balances, perpetual futures trading, prediction markets, token swaps, cross-chain bridges, market data, token discovery, decoding EVM calldata, DeFi earn/yield vaults, or authentication via the MetaMask Agentic CLI; also when an HTTP request returns 402 Payment Required / x402 or the agent needs to pay for a paywalled API, endpoint, file, or resource over HTTP. Single entry point for all mm CLI operations.
Run Git and GitHub CLI commands through the host context when sandboxing blocks Keychain authentication, network access, or .git writes. Use for gh auth, repository or PR operations, and git index.lock or permission failures. Handles execution context only, not GitHub workflow design.
Renders a Structurizr workspace as a Claude artifact or a static site, using the Renderizr CLI. Use when the user wants to see, share, publish or hand over a C4 architecture model — "show me the architecture", "turn this workspace into an artifact", "publish these diagrams" — or mentions Renderizr, workspace.json or artifact.html.
Use the mcpc CLI to work with MCP (Model Context Protocol) servers from the shell - connect to a server as a persistent session, then list and call tools, read resources, get prompts, and run async tasks. Use --json for scripting and code mode. Reach for this whenever interacting with MCP servers, calling MCP tools, or accessing MCP resources programmatically.
Moda meta and routing help — not a design tool. Use for meta asks only: installing or updating Moda, authentication and org switching, "what can Moda do?", "which Moda skill or tool should handle X?", CLI troubleshooting (doctor, last-error, typed errors), automation and integration asks ("set up Moda to auto-post/sync/schedule X", connect Moda to another tool, recurring jobs — the automation part only: any artifact to author still routes to its format skill) — or when a Moda request doesn't CLEARLY fit any other moda skill (a matching format skill always wins; this is the none-fit catcher, never a shortcut). Creating or editing designs, decks, documents, sites, graphics, videos, or diagrams is never this skill — load the format skill (moda-deck, moda-one-pager, moda-social, moda-diagram, moda-website, moda-video, moda-brand, moda-edit).
Make video and motion on Moda: short generated clips (text-to-video, image-to-video from a logo, photo, or canvas frame, reference-guided), brand stingers, animated posts and ads, logo animations, video upscaling, and vector-native motion (animated shader fills, animation-canvas exports). Use for "make a video", a GIF or mp4, an animated ad/post/banner, a motion graphic, animating a logo/image/design, or upscaling a video. moda-video owns anything that renders to mp4/gif — an animated social post is this skill for the motion (moda-social owns still sizes and formats). Still posts/carousels/banners → moda-social; slide decks → moda-deck; live sites → moda-website; edits to an existing canvas that stay still → moda-edit. Video generation is a metered lane; canvas motion authoring and mp4/gif export are not.