Loading...
Loading...
Found 1,026 Skills
Backseat gaming mode for coding — you can see exactly what's wrong and tell the user precisely what to do, but you never touch the code yourself. The user implements everything. Persistent, no exit. Activate with /backseat. Use when the user says /backseat, "coach me but don't code for me", "guide me while I implement", or wants to do the coding themselves with guidance.
Comprehensive Contentful REST API guide. Covers Content Management API (CMA) for creating/updating content, Content Delivery API (CDA) for fetching published content, Preview API, Images API, and GraphQL API. All examples use curl/HTTP — language-agnostic.
Given event_candidates YAML (output from discover-event-surfaces), generates a concrete instrumentation plan for priority-3 (critical) events. Acts as a Software Architect: discovers existing analytics patterns in the codebase, reads the hinted files to determine what variables are in scope, designs minimal chart-useful properties, and identifies the exact insertion point for each tracking call. Outputs a structured JSON trackingPlan. Use this as step 3 of the analytics instrumentation workflow, after discover-event-surfaces. Trigger whenever a user has event_candidates and wants to generate tracking code, asks "instrument these events", "generate tracking plan", "add analytics for these events", "where should I put the tracking calls", or any request to turn event candidates into concrete implementation guidance.
Use when you need to print Jetson BSP info (L4T version, board configs, rootfs state) from a Linux_for_Tegra root on the host PC. This is an example skill.
Make dense or complex information easier to understand, navigate, remember, and act on through clear layers, concrete examples, and visible progress. Use when the user explicitly invokes Focus Friendly; requests focus-oriented simplification, chunking, pacing, mapping, or reorientation; reports overwhelm, trouble reading or focusing, task-initiation difficulty, or losing their place in the current task; asks whether those difficulties prove ADHD; or asks for help navigating long, structurally complex material that genuinely needs a map. Do not invoke merely because a request mentions ADHD or asks for summarization, teaching, planning, research, or routine coding; those tasks need an explicit focus or navigation signal.
Audit and govern Skills, plugins, and MCP servers across Codex, Claude Code, and compatible Agent hosts. This tool applies when users request to inventory, deduplicate, classify, scope, archive, or reduce the context cost of Agent capabilities; ask why there are so many Skills; need to make global/project/trigger-related decisions; or use phrases like "Skill Slimming", "Inventory Skills", "Organize Skills", "Skill Governance", "Too Many Skills", "Which Skills Take Effect Globally", "Analyze Plugins and MCP", "Context Occupancy", "Generate Skill Review Page", "I'm Done Selecting", or "Read My Skill Settings". Default to a read-only evidence audit and a locally persisted review draft. Never install, enable, copy, archive, disable, delete, or execute a plan without separate explicit authorization for the exact phase and target set.
Generates API documentation using OpenAPI/Swagger specifications with interactive documentation, code examples, and SDK generation. Use when users request "API documentation", "OpenAPI spec", "Swagger docs", "document API endpoints", or "generate API reference".
Translate online articles into Chinese and save them in Markdown format. Use this skill when users need to translate web articles or blog posts, for example: "Translate this article https://example.com/article", "Translate the article from this URL into Chinese and save it".
A tiny skill used by the skillloadmode example.
Data structures and algorithms reference based on CLRS. Use this skill when implementing, discussing, or choosing data structures or algorithms. Auto-activates for algorithm selection, complexity analysis, and performance optimization. Comprehensive coverage of fundamental and advanced data structures with pseudocode examples.
Generates clear, example-driven documentation with runnable code samples and progressive complexity. Use when writing API docs, guides, READMEs, or any technical documentation.
Creates reusable prompt templates with strict output contracts, style rules, few-shot examples, and do/don't guidelines. Provides system/user prompt files, variable placeholders, output formatting instructions, and quality criteria. Use when building "prompt templates", "LLM prompts", "AI system prompts", or "prompt engineering".