73 个 · 按相关度排序
Write how-to guides and tutorials that naturally integrate affiliate product recommendations. Triggers on: "write a how-to guide", "tutorial for [task]", "step by step guide to [goal]", "how to [verb] with [product]", "write a tutorial blog post", "guide on how to [task]", "beginner guide to [topic]", "walkthrough for [product]", "write an educational article", "how do I [task] blog post", "write a tutorial that promotes [product]".
中文简介正在准备中。当前显示原文说明。
How-To guide patterns for documentation - task-oriented guides for users with specific goals. Use when writing a how-to/howto guide, task guide, procedural guide, step-by-step guide, or how-to documentation. Builds on the docs-style core writing principles.
中文简介正在准备中。当前显示原文说明。
Review blog posts, landing pages, and guides for readability. Estimate reading difficulty, identify long sentences and jargon, and simplify wording and paragraph structure so broad audiences can follow the content more easily.
中文简介正在准备中。当前显示英语简介。
Turn articles, notes, or a topic into an explainer video without filming a presenter. The workflow plans the story, creates text and diagram visuals, adds narration when needed, and prepares an MP4 in HyperFrames.
中文简介正在准备中。当前显示英语简介。
Turn conversations and notes into structured Notion pages, including wiki entries, how-to guides, FAQs, and decision logs. Capture context and sources, connect related pages, and maintain owners and status as information changes.
中文简介正在准备中。当前显示英语简介。
Draft SEO-focused blog posts, landing pages, and website copy from a keyword or topic, or improve an existing page. Follow Google's guidance on helpful content and experience, expertise, authority, and trust.
中文简介正在准备中。当前显示英语简介。
Golang skills orchestrator — always active on any Golang coding, review, debug, or setup task. Reads the task context and loads the most relevant skills from samber/cc-skills-golang, often multiple at once: writing a gRPC service loads golang-grpc + golang-testing + golang-error-handling; debugging a panic loads golang-troubleshooting + golang-safety; auditing security loads golang-security + golang-lint + golang-safety. Also: disambiguates competing clusters when two skills seem to overlap (performance vs benchmark vs troubleshooting, samber/lo vs mo vs ro, DI cluster, safety vs security), and configures the project's agent-config file (CLAUDE.md, AGENTS.md, GEMINI.md, Cursor rules, or Copilot instructions) to force-trigger skills in a project (/golang-how-to configure).
中文简介正在准备中。当前显示原文说明。
Deprecated compatibility entry for How-to Section construction. This component is now maintained in Bricks; install and use component-builder to build a new How-to Section.
中文简介正在准备中。当前显示原文说明。
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.
中文简介正在准备中。当前显示原文说明。
Audit, classify, validate, and scaffold documentation using the Diataxis framework (Tutorials, How-to guides, Reference, Explanation). Use when user mentions "diataxis", "documentation framework", "quadrant", "doc audit", "doc coverage", "collapsed document", "tutorial vs how-to", "quadrant purity", "documentation types", or wants to classify docs by type.
中文简介正在准备中。当前显示原文说明。
Write, restructure, or review documentation — tutorials, how-to guides, reference pages, concept/explanation docs, API references, READMEs, changelogs, release notes, and troubleshooting guides. Distills documentation craft from Mintlify's guides (compiled from technical writers at Stripe, GitHub, Amplitude, and Anaconda), the Diátaxis framework (including the compass and per-type voice), the Google and Microsoft style guides, Every Page Is Page One, Write the Docs, and Docs for Developers: audience analysis, content-type selection, style and word-level rules, procedure writing, structure for humans and AI agents, code-example standards, page templates (templates.md), mechanical enforcement and llms.txt (mechanics.md), maintenance, and success metrics. Use this skill when the user asks to "write docs", "document this feature", "improve this page", "review these docs", "write a tutorial / how-to / reference page", "structure the docs", "write API documentation", "write a README / changelog", or when authoring any file under a `docs/` tree. For Skmtc docs specifically, this skill governs the *craft* (what makes the page good); the content split between skills, `llms.md`, and the docs tree is governed by `docs/skills/README.md`. Distinct from `skmtc-retro` (captures observations about work) and the `skmtc-*` operational skills (guide doing the work) — this skill guides writing *about* the work for readers.
中文简介正在准备中。当前显示原文说明。
在AI的建议、计划、估算或分析后附上两三个简短问题，帮助用户在行动前检查数字、逻辑与缺失信息。问题紧扣回答中的具体内容，可直接向代理追问。
Create editable documents for sharing and comments, including reports, proposals, resumes, and guides. Use the docs connector to prepare documents that can be exported to Word, PDF, Markdown, or Google Docs.
中文简介正在准备中。当前显示英语简介。
Turn conversations and notes into organized Notion pages for decisions, guides, FAQs, and team knowledge. Create or update pages with summaries, source links, tags, and owners, then connect them to related documentation.
中文简介正在准备中。当前显示英语简介。
Work on Handsontable core bugs, features, and TypeScript types using its architecture and implementation conventions. The skill directs tasks to specialist guides and outlines registration, compatibility, documentation, and testing checks for changes.
中文简介正在准备中。当前显示英语简介。
Present travel plans, product choices, and numerical data directly in Kortix chat using photo-based steps, cards, maps, tables, and charts. The skill selects a visual format suited to each part of the answer.
中文简介正在准备中。当前显示英语简介。
Turn conversations and notes into organized Notion pages for decisions, guides, FAQs, and team knowledge. Create or update pages with summaries, source links, tags, and owners, then connect them to related documentation.
中文简介正在准备中。当前显示英语简介。
Create or revise software documentation for learning, completing tasks, checking technical details, or understanding concepts. Organize README sections, API docs, and operational guides around reader needs, with commands and claims checked against available project evidence.
中文简介正在准备中。当前显示英语简介。
Turns a technical topic into a structured tutorial tailored to the reader's experience and environment. It includes prerequisites, setup, verifiable steps, troubleshooting, further learning, and a concise cheatsheet of commands and common fixes.
中文简介正在准备中。当前显示英语简介。
Draft a pull request description that explains the problem, implementation, trade-offs, and testing. It combines source-backed reasoning, validated Mermaid diagrams, and actual validation output into one Markdown file reviewers can assess on its own.
中文简介正在准备中。当前显示英语简介。
Generate JSON-LD structured data, code that describes page content to search engines, for FAQ, HowTo, Article, Product, LocalBusiness, or combined schemas. Check Google requirements and get guidance on adding the markup to a page.
中文简介正在准备中。当前显示英语简介。
Not for writing library code (name that library skill). Use this skill whenever another DOCA skill says "prefer the structured tool per doca-structured-tools-contract", or when the user wants a one-shot answer that consolidates info multiple manual commands would produce — DOCA env / version / devices / capabilities / validate / host vs DPU state. Trigger even when the user does not explicitly mention "structured tool" or "doca-env --json" — typical implicit phrasings include "is there one command that tells me everything about my DOCA install", "what version is X capability available since", "every PF/VF/SF visible on this BlueField with PCIe address", "will this pipe pass validate before commit", "diff host vs DPU state", or "why does the agent give a one-line answer on host A and five commands on host B". Refuse and route elsewhere for general DOCA orientation, specific library API how-to, or install-from-scratch guidance — those belong to the per-library skill, doca-public-knowledge-map, or doca-setup.
中文简介正在准备中。当前显示原文说明。
Update website docs to match recent code changes, cross-validating every flag against source. Use this skill whenever the user asks to: update documentation, sync docs with code, document a new flag or command, fix stale docs, or update the README. This skill covers all website/docs/ categories (commands, reference, understand, how-to, troubleshooting, getting-started) plus the built-in skill description and README. If you just implemented a feature and need to update docs, this is the skill to use. Never manually edit website docs without cross-validating flags against Go source first.
中文简介正在准备中。当前显示原文说明。
Audit, write, and improve developer documentation using Google's Developer Documentation Style Guide and Technical Writing courses. Use this skill for any documentation work, even when the user names no style guide: "audit our docs", "review this README", "write a README", "getting started guide", "how-to or tutorial", "API reference", "docstrings", "CLI help text", "changelog or release notes", "migration guide", or "our docs are confusing". Also use it when writing docs from code, rewriting a doc for clarity, fixing headings, procedures, or code samples, or enforcing consistent voice and terminology across a docs set — prefer it over editing documentation unaided. Covers reader and doc-type fit, second person and active voice, procedures, headings, lists and tables, code samples and placeholders, link text, notices, the word list, timeless docs, and accessibility. For code comments and naming, see clean-code. For marketing or landing-page copy, see storybrand-messaging.
中文简介正在准备中。当前显示原文说明。