612 skills · sorted by relevance
Structure guides, READMEs, design documents, and pull request descriptions so readers can find answers quickly. Put outcomes first, introduce details gradually, and use examples, tables, and checklists to support understanding and review.
Package a finished local web project for GitHub with a tailored README and a preview from the running project. Audit files before pushing, publish compatible projects through GitHub Pages, and verify the repository and live demo.
Turn repository documentation and images into a complete landing page with features, setup instructions, and FAQs. Generate static HTML, CSS, and JavaScript files, plus a GitHub Actions workflow for publishing on GitHub Pages.
Check a software module’s folder structure, required README.md and DESIGN.md files, and whether documentation matches the code. Produce a report identifying missing content and issues to resolve before handoff.
Review a codebase and generate or update its README.md according to best practices. The skill performs static analysis of the project structure, dependencies, scripts, and existing documentation, then produces a comprehensive, accurate README. **Triggers — use this skill when:** - User asks to "review", "update", "improve", or "generate" a README - User says "create a README for this project" - User mentions "document this repo", "add documentation" - User asks to "fix my README" or "make my README better" - User provides a codebase and asks for documentation help **Covers:** Any project type — Node.js, Python, Rust, Go, Java, Ruby, PHP, monorepos, static sites, CLI tools, libraries, APIs, Docker-based projects, and more. Works with both new READMEs (from scratch) and existing ones (update/improve).
The English summary is being prepared. Showing the original description.
Generates professional PyPI-compliant README files in Markdown or reStructuredText. Use when creating a Python package README for PyPI publication, converting between README.md and README.rst formats, validating markup with twine check before publishing, configuring the readme field in pyproject.toml, integrating sphinx-readme to generate PyPI-compatible RST from Sphinx docs, troubleshooting rendering errors on PyPI, or previewing README rendering locally with grip or docutils.
The English summary is being prepared. Showing the original description.
Compare release changes with project documentation, then update files such as README and CHANGELOG to reflect what shipped. The skill also checks architecture diagrams, maps missing documentation, and records remaining documentation work in the pull request.
Create an animated diagram showing request flows, background jobs, or feature changes. The result is a single SVG image for README files, pull requests, issues, or blog posts, with support for light and dark themes.
Review prose for repetitive wording, inflated language, and overly regular structure. Get an issues-only audit, a rewritten version, or targeted file edits that preserve the author's voice, existing facts, and protected quoted material.
Create text diagrams with PlantUML for README files, emails, and terminal workflows. Convert diagram definitions into plain ASCII or Unicode box-drawing output to share interactions and relationships where image-based diagrams are unsuitable.
Compare documentation with actual code, configuration, and commands to find outdated instructions or missing information. Produce a read-only audit with evidence, severity levels, and specific guidance on which documents need updating.
Add corporate sponsors to ZCF’s English, Chinese, and Japanese README lists, with optional advertising cards and API connection presets. Check for existing entries and keep sponsor information consistent across languages.
Prepare conference LaTeX template archives for writing in Overleaf. The skill identifies the main file and dependencies, proposes cleanup for approval, and organizes sections, resources, and a README with submission and compilation guidance.
Update the root README.md with entries for new or changed agent companies. Use when a new company has been added to the repo, when company details have changed (agents added/removed, skills added/removed), or when the user asks to refresh/sync the README. Triggers on: "update the readme", "add this company to the readme", "sync readme", "refresh readme", or after creating a new company with company-creator.
The English summary is being prepared. Showing the original description.
Use this skill to write or revise a README.md for a Shipfox workspace package (libs/*, tools/*). It applies the shared package README standard and repository prose policy. Trigger on write a README, draft README, rewrite README, document this package, or improve the README.
The English summary is being prepared. Showing the original description.
Rewrite technical documentation and instructions using ASD-STE100, a set of rules for clear technical English. Shorten sentences, keep terminology consistent, and audit passages with rule numbers and suggested corrections while preserving code and commands.
Compare README, specification, and product documents with recent git history to find outdated claims or missing features. Make small factual corrections, preserve the existing style, and prepare a pull request for review.
Maintain a Chinese independent developer project list by reviewing comments, issues, and pull requests. Check duplicate URLs and submission eligibility, add projects to the appropriate README, merge contributions, and reply with the listing result.
Review and rewrite Chinese product announcements, articles, emails, and README text using eleven style checks. Identify repetitive phrasing, overloaded sentences, vague openings, and decorative language, then revise them into clearer statements suited to each type of writing.
Create or edit Markdown with each prose paragraph on one source line, letting the viewer wrap the text automatically. Preserve meaningful line breaks in lists, code, and poetry while reducing unnecessary changes in file comparisons.
Turn a written diagram request into a JSON specification and render a blueprint-style SVG. Create system architectures, request flows, state machines, or neural network diagrams as files for documentation, READMEs, posts, and slides.
Create and review technical documentation alongside repository instructions for agents and contributors. The skill checks clarity, working procedures, documentation coverage, and consistency across languages, then provides updated drafts or findings with validation notes.
Redesign GitHub README homepages or create project-native pure SVG, hybrid SVG-composed PNG/WebP, and opt-in animated GIF assets. Use when a user asks to beautify, redesign, rebrand, visually upgrade, simplify, or audit a GitHub README; create only a hero, section headers, diagrams, badges, motion graphics, showcase modules, or other README assets; or turn a repository homepage into a cohesive visual story. If whole-README work versus asset-only work is unclear, ask which scope the user wants. For hero-like assets where pure SVG and generated raster material are both viable, explain the tradeoffs and confirm the implementation before creating the asset.
The English summary is being prepared. Showing the original description.
リポジトリの構造・技術スタック・機能一覧・セットアップ手順を動的に解析し、 包括的なドキュメントを自動生成するスキル。言語・フレームワーク問わず汎用的に動作する。 Use this skill whenever the user asks to: - Explain a repository / リポジトリの説明 / リポジトリの概要 - Generate a README / README生成 / README作成 - Understand project structure / プロジェクト構成を教えて / 構造を説明して - Learn how to run a project / 使い方を教えて / 動かし方 / セットアップ方法 - Get a repo overview / repo overview / explain this repo / what does this repo do - List features / 機能一覧 / このプロジェクトは何ができる？ - Onboard to a new codebase / コードベースのキャッチアップ / 新しいリポジトリに入った - "このリポジトリ何？" "プロジェクトの全体像" "how to run this project" - "コードの全体を把握したい" "ドキュメントを整備して" "技術スタックを知りたい" This skill is especially useful when joining a new project, onboarding team members, or when a repository lacks proper documentation. It works with ANY repository regardless of programming language, framework, or project type.
The English summary is being prepared. Showing the original description.