create-skill-file SKILL.md skillA
create-skill-file from bg-szy/top-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add bg-szy/top-skills/create-skill-file@git:20260530.b083023Pins git:20260530.b083023 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- bg-szy/top-skills
- Path
skills/Claude-meta-skill/create-skill-file__create-skill-file/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260530.b083023, committed May 30, 2026
- Size
- 10,257 bytes
- Repository stars
- 6
- License
- a license file GitHub does not identify
Guides Claude in creating well-structured SKILL.md files following best practices. Provides clear guidelines for naming, structure, and content organization to make skills easy to discover and execute.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Claude Agent Skill 编写规范 > 如何创建高质量的 SKILL.md 文件 ## 目录 - [快速开始](#快速开始) - [核心原则](#核心原则) - [文件结构规范](#文件结构规范) - [命名和描述规范](#命名和描述规范) - [内容编写指南](#内容编写指南) - [质量检查清单](#质量检查清单) --- ## 快速开始 ### 3步创建 Skill **第1步: 创建目录** ```bash mkdir -p .claude/skill/your-skill-name cd .claude/skill/your-skill-name ``` **第2步: 创建 SKILL.md** ```markdown --- name: your-skill-name description: Brief description with trigger keywords and scenarios --- # Your Skill Title ## When to Use This Skill - User asks to [specific scenario] - User mentions "[keyword]" ## How It Works 1. Step 1: [Action] 2. Step 2: [Action] ## Examples **Input**: User request **Output**: Expected result ``` **第3步: 测试** - 在对话中使用 description 中的关键词触发 - 观察 Claude 是否正确执行 - 根据效果调整 --- ## 核心原则 ### 1. 保持简洁 只添加 Claude **不知道**的新知识: - ✅ 项目特定的工作流程 - ✅ 特殊的命名规范或格式要求 - ✅ 自定义工具和脚本的使用方法 - ❌ 通用编程知识 - ❌ 显而易见的步骤 **示例对比**: ```markdown # ❌ 过度详细 1. 创建 Python 文件 2. 导入必要的库 3. 定义函数 4. 编写主程序逻辑 # ✅ 简洁有效 使用 `scripts/api_client.py` 调用内部 API。 请求头必须包含 `X-Internal-Token`(从环境变量 `INTERNAL_API_KEY` 获取)。 ``` ### 2. 设定合适的自由度 | 自由度 | 适用场景 | 编写方式 | |--------|---------|---------| | **高** | 需要创造性、多种解决方案 | 提供指导原则,不限定具体步骤 | …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_gwmwz6n36waruo4y/732a27bc1c01fbf01a4d2b14a09991354e977545840b0c35efe82db0d01797cb.json
Then /plugin install create-skill-file@markdownregistry-gwmwz6n36waruo4y in Claude Code. It installs git:20260530.b083023, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add bg-szy/top-skills/create-skill-file@sha256:732a27bc1c01fbf0The line at the top of this page pins the label git:20260530.b083023, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_gwmwz6n36waruo4y)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in bg-szy/top-skills/create-skill-file since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of create-skill-file from somewhere else? Ask it: where did my create-skill-file come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on May 30, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/create-skill-file/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10257 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
bg-szy/top-skills · 6 stars · license a license file GitHub does not identify · pushed 2026-11-15 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_gwmwz6n36waruo4y GET https://markdownregistry.com/api/v1/resolve?ref=bg-szy/top-skills/create-skill-file GET https://markdownregistry.com/api/v1/blob/732a27bc1c01fbf01a4d2b14a09991354e977545840b0c35efe82db0d01797cb
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from bg-szy/top-skills
Every file in bg-szy/top-skills