Loading...
Loading...
Found 1,022 Skills
Produces API reference documentation for Next.js APIs: functions, components, file conventions, directives, and config options. **Auto-activation:** User asks to write, create, or draft an API reference page. Also triggers on paths like `docs/01-app/03-api-reference/`, or keywords like "API reference", "props", "parameters", "returns", "signature". **Input sources:** Next.js source code, existing API reference pages, or user-provided specifications. **Output type:** A markdown (.mdx) API reference page with YAML frontmatter, usage example, reference section, behavior notes, and examples.
Firecrawl produces cleaner markdown than WebFetch, handles JavaScript-heavy pages, and avoids content truncation. This skill should be used when fetching URLs, scraping web pages, converting URLs to markdown, extracting web content, searching the web, crawling sites, mapping URLs, LLM-powered extraction, autonomous data gathering with the Agent API, or fetching AI-generated documentation for GitHub repos via DeepWiki. Provides complete coverage of Firecrawl v2.8.0 API endpoints including parallel agents, spark-1-fast model, and sitemap-only crawling.
Write a textual content based on given document(s) and requirements, using ZhiPu GLM-V multimodal model. Read and comprehend one or multiple documents (PDF/DOCX), write a content in Markdown format according to the specified requirements. Use when the user wants to draft a paper/article/essay/report/review/post/brief/proposal/plan, etc.
All-in-one WeCom CLI Suite covering 6 core business domains: Contacts, Messages, Documents (including three types: Document, Smart Sheet, Smart Document (formerly Smart Homepage)), Schedules, Meetings, and Tasks. It supports searching contacts by name/alias, sending and receiving messages (text/image/file/voice/video), creating/reading/editing documents in Markdown format, managing Smart Sheet structures and records, creating Smart Documents and exporting their content as Markdown, creating/modifying/canceling schedules and checking availability, booking/managing meetings, and creating/tracking/assigning tasks. This skill should be triggered even if users do not explicitly mention 'WeCom' as long as scenarios involving messages, schedules, tasks, etc., are involved.
Async media + document derivations via `platform.media.transforms` and the declarative `transforms` block in `maravilla.config.ts`. Media: transcode video, thumbnail extraction, image resize/variants, OCR. Documents (.docx/.odt/.pptx/.xlsx/...): convert to PDF, render page thumbnails, generic format conversion, Markdown extraction (RAG-ready), single-file HTML with inlined images, image-replacement templating ({{TAG}} swap + named-object swap), QR-code injection. Use when ingesting user uploads that need normalised renditions, generating contracts/invoices from templates, or extracting structured content for LLMs. Critical: derived keys are content-addressed — `keyFor(srcKey, spec)` is known up front, before the worker starts, so clients can render placeholder UI without round-trips. Declarative config is the default; imperative `transforms.*` calls are for one-offs.
This skill should be used when the user wants to create a new agent skill, scaffold a SKILL.md, validate an existing skill against repo rules, or refactor a skill to match this monorepo's conventions. Common triggers include "build a skill for X", "create a new skill", "scaffold a skill", "add a skill that does Y", "make me a skill", "audit this skill against our rules", and "refactor this skill to match repo conventions". Enforces kebab-case naming, verbatim trigger phrases, selective XML for example boundaries, and a RED→GREEN→REFACTOR cycle. Skip when modifying source code, debugging an existing skill, or writing non-skill markdown.
Explains how to use skeeper to keep spec artifacts (SPEC.md, ADRs, RFCs, plan/PRD/TechSpec markdown, custom globs) next to the code they describe without polluting main-repo history. Covers strict hooks, the tracked skeeper.lock file, namespaces, sync/verify/fsck, safe drift workflows with diff/hydrate/reconcile/rescue/update, adopt/untrack/pattern, repair, SKEEPER_SKIP, and the GitHub Action. Use when setting up skeeper, configuring a sidecar, syncing/verifying a lockfile, recovering drift or failed syncs, auditing bypasses, or wiring CI. Do not use for general Git hook questions, repos with no .skeeper.yml and no intent to add one, or editing skeeper internals.
Detect software architecture bad smells, algorithmic complexity hotspots, and anti-patterns in a codebase. Produces a detailed markdown report identifying violations of architectural principles, design patterns, code quality, and performance complexity. Triggers on: smell, code smell, architecture smell, find anti-patterns, detect bad smells, complexity analysis, 代码坏味道, 架构坏味道, 反模式, 找出坏味道, 复杂度分析.
Verify citations and references in scientific documents to detect hallucinated or invalid sources. Extracts DOIs, URLs, arXiv IDs, PubMed IDs, and ISBNs from Markdown, LaTeX, org-mode, and plain text, then validates them using API lookups and web fetches. Use this skill when: - Reviewing AI-generated content for citation accuracy - Validating references in papers, reports, or documentation - Checking if DOIs/URLs resolve to actual papers - Auditing a document for broken or fake citations
An official AI mind map generator developed by ProcessOn, focusing on converting content such as natural language, Markdown, long text, documents, web pages, and image text into professional, clear-structured, well-layered, and editable mind maps with one click. Whether it's article summarization, data organization, document decomposition, knowledge point induction, learning path sorting, or reading notes, paper literature sorting, meeting minutes extraction, work report summary, outline generation, project task decomposition, brainstorming and idea generation, this skill can quickly generate professional mind maps to help users transform scattered content into clear structured knowledge. This skill supports 7 professional graphic layouts including mind maps, logic diagrams, organizational charts, fishbone diagrams, timelines, tree diagrams, and table diagrams, and is deeply integrated with the ProcessOn online collaboration platform. The generated mind maps can be edited online, collaboratively modified, and efficiently reused, suitable for scenarios such as office work, study review, scientific research reading, knowledge management, and scheme planning. Note: This skill is mainly used to generate mind maps and knowledge structure brain maps, and is not applicable to the generation of process or technical charts such as flowcharts, swimlane diagrams, sequence diagrams, system architecture diagrams, ER diagrams, and Mermaid diagrams.
Spawning Plan. Use when user wants to spawn agents, create a team, or coordinate multiple agents. Automatically gathers context, asks team topology questions, outputs clean TEAM PLAN markdown, and gets user approval. 3 steps: context gathering → questions → present plan. **CRITICAL**: MUST NOT SPAWN AGENTS SKIPPING THIS SKILL, USE ALWAYS.
Catalog GitHub starred repositories into a structured Obsidian vault with AI-synthesized summaries, normalized topic taxonomy, graph-optimized wikilinks, and Obsidian Bases (.base) index files for filtered views. Fetches repo metadata and READMEs via gh CLI, classifies repos into categories and normalized topics, generates individual repo notes with frontmatter, and creates hub notes for categories/topics/authors that serve as graph-view connection points. Use this skill when users want to: (1) Catalog or index their GitHub stars into Obsidian (2) Create a searchable knowledge base from starred repos (3) Organize and discover patterns in their GitHub stars (4) Export GitHub stars as structured markdown notes (5) Build a graph of starred repos by topic, language, or author For saving/distilling a specific URL to a note, use kcap instead. For browsing AI tweets, use ai-twitter-radar instead.