Loading...
Loading...
Found 269 Skills
Add a new gameplay feature to your game — just describe what you want
Manage cmux debug windows and related debug menu wiring for Sidebar Debug, Background Debug, and Menu Bar Extra Debug. Use this when the user asks to open/tune these debug controls, add or adjust Debug menu entries, or capture/copy a combined debug config snapshot.
Adapt a single master creator brief into platform-specific versions for TikTok, Instagram Reels, and YouTube Shorts with correct specs, safe zones, and platform-native guidance. This skill should be used when converting a brief for multiple platforms, adapting a campaign brief from TikTok to Reels, creating platform-specific content briefs from a master brief, adjusting video specs for different short-form platforms, building TikTok and Reels and Shorts versions of one brief, formatting creator deliverables by platform, splitting a campaign brief into platform versions, or generating platform-adapted briefs for a multi-platform creator campaign. For writing the master brief itself, see content-brief-builder. For generating content concepts before briefing, see creator-content-concept-generator. For checking submitted content against a brief, see content-to-brief-compliance-checker.
This skill should be used when the user needs to perform year-end closing adjustments, review financial statements, compute depreciation, or review their trial balance. Trigger phrases include: "year-end settlement", "year-end closing adjustments", "prepare financial statements", "depreciation", "trial balance", "trial balance sheet", "income statement", "balance sheet", "BS", "PL", "period-end processing", "inventory taking", "accrual of unpaid expenses", "prepayment processing"
Based on the content of NSFC proposal text and combined with the application code recommendation library, provide you with 5 sets of recommended primary/secondary application codes (Code 1/Code 2) with justifications; output to NSFC-CODE-vYYYYMMDDHHmm.md (read-only, no modification to the proposal)
Compact, compress, or minify markdown files to use fewer tokens while preserving all information and meaning. Use this skill whenever the user wants to reduce the size of a markdown file, shrink a README, compress a SKILL.md or CLAUDE.md, minify documentation, or make any markdown more token-efficient. Trigger even if they just say "make this shorter" or "compress this" on a markdown file.
Use when making decisions under uncertainty with quantifiable outcomes, comparing risky options (investments, product bets, strategic choices), prioritizing projects by expected return, assessing whether to take a gamble, or when user mentions expected value, EV calculation, risk-adjusted return, probability-weighted outcomes, decision tree, or needs to choose between uncertain alternatives.
Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, create an engineering deep-dive, or produce any written content destined for the Sentry blog or developer audience. Also trigger when the user mentions "blog post," "blog draft," "write-up," "announcement post," "engineering post," "deep dive," "postmortem," or asks for help with technical writing for Sentry. Even if the user just says "help me write about [feature/topic]" — if it sounds like it could become a Sentry blog post, use this skill.
Configure TTS voices, speed, timeouts, queue depth, and bot settings. TRIGGERS - configure tts, change voice, tts speed, queue depth, tts timeout, bot config, tune settings, adjust parameters.
Manage a structured task list using a Markdown file in the workspace. Track progress on complex multi-step tasks. File-based — just Read and Write the todo file.
Guide for using the `paper` CLI tool — a local academic paper management system with AI-powered vector search. Use this skill whenever the user wants to manage academic papers, create knowledge bases, add PDFs to a knowledge base, search papers semantically, configure embedding models, or manage literature metadata and notes. Also trigger when the user mentions "paper" CLI, knowledge bases for research, literature management, or wants to query their paper collection. Even if the user just says something like "add this PDF" or "search my papers" in a project that uses paper-manager, this skill should activate.
NEVER escalate without investigation first. This is the Iron Law. Use when evaluating whether to escalate models, facing genuine complexity requiring deeper reasoning, novel patterns with no existing solutions, high-stakes decisions requiring capability investment. Do not use when thrashing without investigation - investigate root cause first. DO NOT use when: time pressure alone - urgency doesn't change task complexity. DO NOT use when: "just to be safe" - assess actual complexity instead.