637 skills · sorted by relevance
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.
Clean up hard-wrapped Markdown and .qmd files by joining mid-sentence line breaks and placing each sentence on its own line. Preserve headings, code blocks, lists, quotes, and YAML metadata while adjusting paragraph whitespace.
Write or revise technical documents in plain English for readers outside the field. The skill uses short sentences, active voice, consistent terms, and brief definitions while preserving facts, code, commands, and product names.
Check documentation and operator scripts against current code and command conventions. Correct confirmed mismatches in small, focused changes, publish them through a pull request, and report what was inspected when no update is needed.
Upload model weights to Hugging Face Hub with an OpenMDW 1.1 license and a required research warning. Check the published README and license file after uploading or updating to confirm that the required information is present.
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.
Prepare a private project for public release by creating a separate copy, removing sensitive information, checking for remaining risks, and generating documentation, setup scripts, and license files for review before publishing.
Set up a realtime evaluation folder with a suitable shared harness, the framework that runs evaluations. Prepare prompts, tool definitions, realistic starter data, and a README, then validate the setup with evaluation and test runs.
Set consistent Python conventions for naming, formatting, type checking, and documentation. Configure ruff and mypy or pyright, write clear function descriptions, and organize README and changelog content so a team can maintain shared standards.
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.
Keep project documentation aligned with recent code changes. Review commits since the last checkpoint, update affected guides and README files, and open a pull request for human review only when documentation needs correcting.
Match videos from 王二讲Agent to their scripts, then add Bilibili links and Douyin video IDs to the designated documentation files. Identify missing entries while preserving existing links and IDs.
Prepares a project for open-source release by checking sensitive history, licensing, documentation, tests, and automated publishing. Helps identify gaps so people outside the project can build, use, and contribute to it.
Find documentation and agent instructions made outdated by a branch’s code changes. Update affected paths, commands, settings, and behavior descriptions in place, then commit the documentation fixes alongside the code in the same pull request.
Translate English skill documentation into Simplified Chinese while preserving commands, code, paths, and identifiers. Follow a shared glossary, refresh changed content, and review document structure and public indexes to keep the localized edition consistent.
Maintain sponsor listings in all-api-hub across public catalogs, README files, documentation, affiliate content, and images. It helps coordinate updates, verify operational details, and review compatibility with catalog formats that are still served.
Audit a research replication package with ten checks covering R syntax, file references, output freshness, dependencies, data sources, and documentation. Receive a pass/fail report with specific issues and suggested fixes for preparing the package for submission.
Handle small, self-contained changes with a known solution, such as typo fixes, configuration edits, or single-file cleanup. Implement the change, create a focused Git commit, and save a task summary and state record.
Search Wayback Machine archives for deleted GitHub files, issues, pull requests, and wiki pages. Recover available text and repository details from saved web pages to investigate a project's past state.
Use when auditing repository documentation for drift, stale statements, broken references, or README mismatches, especially across published docs under `doc/` and key entry surfaces such as `README.md` (English default), `README.zh-CN.md`, `mcp/README.md`, and `mcp/README.zh-CN.md` during periodic maintenance or before preparing corrective PRs.
The English summary is being prepared. Showing the original description.