Loading...
Loading...
Found 645 Skills
Publish files or Obsidian notes as GitHub Gists. Use when user wants to share code/notes publicly, create quick shareable snippets, or publish markdown to GitHub. Triggers include "publish as gist", "create gist", "share on github", "make a gist from this".
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. All plans MUST be validated using the included validation script. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.
Remove signs of AI-generated writing from text to make it sound more natural and human-written. Use when editing or reviewing any form of document including: markdown, technical docs, emails, blog posts, PRDs, or any dedicated writing content. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Design comprehensive test cases using PICT (Pairwise Independent Combinatorial Testing) for any piece of requirements or code. Analyzes inputs, generates PICT models with parameters, values, and constraints for valid scenarios using pairwise testing. Outputs the PICT model, markdown table of test cases, and expected results.
Extract structured review themes from any input source: supports files (PDF/Word/Markdown/Tex), folders, images, natural language descriptions, web URLs, etc.; automatically identifies input types and extracts content; generates structured output of "Theme + Keywords + Core Questions" which can be directly used for systematic-literature-review and other literature review skills.
Explain how CE.SDK Web features work — concepts, architecture, and workflows. Covers React, Vue.js, Svelte, Angular, Electron, Vanilla JavaScript, Node.js, Nuxt.js, Next.js, SvelteKit. Use when the user says "explain", "how does X work", "walk me through", "what is", "describe", or wants to understand a CE.SDK concept at a conceptual level for Web development. Generates custom markdown explanations with diagrams and code examples. Not for looking up existing docs (use docs-{framework}), not for writing implementation code (use build). <example> Context: User wants to understand how text layers work user: "Explain how text layers work in CE.SDK" assistant: "I'll use /cesdk:explain to generate a detailed explanation." </example> <example> Context: User needs a concept explained in their context user: "How does the block hierarchy work for video editing?" assistant: "Let me use /cesdk:explain to create a custom explanation for video block hierarchy." </example> <example> Context: User needs to understand a workflow user: "Walk me through the asset loading pipeline" assistant: "I'll use /cesdk:explain to explain the asset pipeline." </example>
Validates the interoperability between skills. Ensures that output formats (JSON/Markdown) from one skill are correctly consumed by the next in a chain.
Perform code reviews following best practices from Code Smells and The Pragmatic Programmer. Use when asked to "review this code", "check for code smells", "review my PR", "audit the codebase", or need quality feedback on code changes. Supports both full codebase audits and focused PR/diff reviews. Outputs structured markdown reports grouped by severity.
Convert content between formats, summarize at different levels, and repurpose for various platforms. Use when asked to convert to markdown, create summaries of varying lengths, make tweets, create flashcards, or process video content. Triggers include "convert to markdown", "summarize in one sentence", "make this a tweet", "create flashcards", "TL;DR", "summarize this video", "export as CSV".
Primary tool for all code navigation and reading in supported languages (Rust, Python, TypeScript, JavaScript, Go). Use instead of Read, Grep, and Glob for finding symbols, reading function implementations, tracing callers, discovering tests, and understanding execution paths. Provides tree-sitter-backed indexing that returns exact source code — full function bodies, call sites with line numbers, test locations — without loading entire files into context. Use for: finding functions by name or pattern, reading specific implementations, answering 'what calls X', 'where does this error come from', 'how does X work', tracing from entrypoint to outcome, and any codebase exploration. Use Read only for config files, markdown, and unsupported languages.
Web scraping and search CLI returning clean Markdown from any URL (handles JS-rendered pages, SPAs). Use when user requests: (1) "search the web for X", (2) "scrape/fetch URL content", (3) "get content from website", (4) "find recent articles about X", (5) research tasks needing current web data, (6) extract structured data from pages. Outputs LLM-friendly Markdown, handles authentication via firecrawl login, supports parallel scraping for bulk operations. Automatically writes to .firecrawl/ directory. Triggers: web scraping, search web, fetch URL, extract content, Firecrawl, scrape website, get page content, web research, site map, crawl site.
REQUIRED skill for planning and designing coding tasks before implementation. Use this skill when: (1) User asks to "plan", "design", "create a plan", or "think before coding" (2) Complex tasks requiring multiple files or steps (3) Tasks involving both backend and frontend changes (4) Breaking down ambiguous requirements into concrete tasks This skill ensures plans are properly documented, saved as markdown, reviewed by subagent, and registered as todos before any code is written. Do NOT skip this skill for non-trivial tasks.