6.6K skills · sorted by relevance
Manage SiYuan notebooks, documents, and blocks, the individual pieces of note content, from the terminal. Search your knowledge base, create or update notes, inspect document structure, and export documents as Markdown through its local API.
Maintain Cherry Studio documentation by checking it against source code, placing facts in appropriate files, and removing duplication. Review documentation affected by code changes and keep relevant English and Chinese counterparts aligned.
Write or revise system architecture documents, design decision records, and engineering references. Use concrete examples and clear explanations of design choices to make documents useful both to newcomers and to developers needing precise details.
Create technical documentation that people and AI can navigate by separating facts, context, known bugs, and uncertain claims. Convert existing Markdown to HADS, a structured documentation format, and check its required elements.
Write or update repository and product documentation, including README files, user guides, API documentation, architecture notes, and migration instructions. Identify the audience, improve existing documents where possible, and verify commands and paths while flagging unknown details.
Document a local codebase with file references, architecture diagrams, and verified project commands. For legacy modernization, assess what still runs and create a phased migration plan with validation methods suited to each component’s current condition.
Creates software documentation using Diátaxis, a framework that separates learning, task instructions, reference information, and explanation. Clarifies the audience, goal, and scope, then proposes an outline before writing Markdown content consistent with existing documentation.
Documents a codebase with linked AGENTS.md files that explain each directory, important files, dependencies, and working rules. It can also update existing documentation while preserving human-written notes and checking that the document hierarchy remains consistent.
Build document search and AI retrieval workflows with Chroma, a database for numerical representations of text. Cover document storage, meaning-based search, metadata filters, persistence, and connections to LangChain and LlamaIndex.
Append plain text to the end of an existing Google Docs document using its document ID. Use it to add notes, follow-up information, or extra paragraphs through the gws command-line tool.
Convert attached office documents, EPUB, CSV, and text-based PDFs into local Markdown using Firecrawl AnyDoc CLI. Files stay inside the agent container, producing readable text for review without uploading documents to an external parsing service.
Maintain Composio's documentation site and record documentation decisions. Work on content, Fumadocs configuration, changelogs, automation prompts, and review guidance, including ADR-style records that capture decisions and their rationale.
Find and retrieve official OpenAI documentation to answer API integration questions with source evidence. Check endpoint definitions, parameters, and documented limits, and receive setup guidance when the documentation connection is unavailable.
Compare documented permissions and data boundaries with actual code to find meaningful gaps. Produce findings that connect each documented rule to implementation evidence, identify who could exploit it and who is affected, and propose a concrete fix.
Find and synthesize official Google developer documentation for platforms including Google Cloud, Gemini, Android, and Firebase. Retrieve command syntax, API details, permissions, and product comparisons through Developer Knowledge, then turn the findings into practical technical answers.
Fill documentation gaps identified by a CARLA documentation audit, following the project's writing style. Work through one category at a time, assess which findings deserve entries, update source files, and report changes and skipped findings.
Checks a local CARLA checkout for missing API documentation, outdated references, broken links, and pages absent from navigation. Produces a grouped Markdown report without building the project or running the simulator.
Build document search and AI retrieval workflows with Chroma, a database for numerical representations of text. Cover document storage, meaning-based search, metadata filters, persistence, and connections to LangChain and LlamaIndex.
Create a technical design document before implementation by answering questions about the problem, scope, architecture, risks, and delivery plan. The skill adjusts sections to project size and covers security, testing, monitoring, and recovery where relevant.
Azure AI Document Translation SDK for batch translation of documents with format preservation. Use for translating Word, PDF, Excel, PowerPoint, and other document formats at scale. Triggers: "document translation", "batch translation", "translate documents", "DocumentTranslationClient".
The English summary is being prepared. Showing the original description.
Record a decision, document existing code, or file a supplied research material. Modes: document decision (ADR, RFC, or rule), document code (spec, doc, guide, or scenario for existing behavior), document research (only when a finished report or one external material is already in hand). Use for 'we decided', 'record this decision', 'document why we chose X', 'make it our standard', 'draft an RFC', 'should we switch to Y' proposals, 'resolve the RFC', 'we accepted the proposal', 'document the auth module', 'capture how the payment system works', reference material, how-to instructions, or a user flow with examples over an existing spec. Name the type inside the subject to skip the type question. Planning a feature or an intended user journey → /archcore:plan. Checking docs against code or docs health → /archcore:review.
The English summary is being prepared. Showing the original description.
Design and run a documentation system for a team or product. Use this skill when planning what to document, choosing a documentation tool, organizing existing docs, fixing stale documentation, designing a maintenance cadence, or scoping technical writing work. Triggers on documentation, docs, tech writing, knowledge base, wiki, runbook, README, internal docs, doc audit, doc maintenance, stale docs, where do we document. Also triggers when the team is repeatedly answering the same questions or when onboarding takes too long.
The English summary is being prepared. Showing the original description.
Update Han plugin documentation so every skill, agent, guidance doc, index, and cross-reference is current and accurate. On a non-default branch, scopes the pass to entities the branch actually touched. On the default branch, performs a full documentation sweep across the whole plugin. Use when updating, refreshing, syncing, auditing, or verifying Han's docs after changing skills, agents, references, or top-level guidance — including "update the docs", "doc sweep", "refresh documentation", "audit the docs", "make sure the docs are current". This is a repository-maintenance skill for the Han repo itself, not a general documentation skill — use /project-documentation to document features in arbitrary projects, /han-release to cut a release (and update CHANGELOG), and /update-pr-description for PR bodies.
The English summary is being prepared. Showing the original description.
Generate comprehensive documentation for undocumented or poorly documented codebases. Use when a user asks to document code, add JSDoc/docstrings, create README files, generate architecture docs, explain what a codebase does, produce onboarding guides, or document internal APIs. Works with any language.
The English summary is being prepared. Showing the original description.