做什么
为阿波罗GraphQL和GraphQL开发创造有效技能指南. 当:(1)用户想创建新技能,(2)用户想更新现有技能,(3)用户询问技能结构或最佳做法,(4)用户需要帮助写入SKILL.md文件时,使用此技能.
技能库 智客分类:写作与研究 skill-creator
为阿波罗GraphQL和GraphQL开发创造有效技能指南. 当:(1)用户想创建新技能,(2)用户想更新现有技能,(3)用户询问技能结构或最佳做法,(4)用户需要帮助写入SKILL.md文件时,使用此技能.
官方网址:skills.sh
先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。
为阿波罗GraphQL和GraphQL开发创造有效技能指南. 当:(1)用户想创建新技能,(2)用户想更新现有技能,(3)用户询问技能结构或最佳做法,(4)用户需要帮助写入SKILL.md文件时,使用此技能.
这个
按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Skill Creator Guide、What is a Skill?、Directory Structure、SKILL.md Format、Frontmatter (Required)、Frontmatter Fields。
文件分析:除 SKILL.md 外,正文引用了 references/topic-a.md、references/topic-b.md、references/setup.md、references/patterns.md、scripts/validate.sh、references/apollo-skills.md,属于带资源的技能包,这些文件按需再读。
Guide for creating effective skills for Apollo GraphQL and GraphQL development. Use this skill when: (1) users want to create a new skill, (2) users want to update an existing skill, (3) users ask about skill structure or best practices, (4) users need help writing SKILL.md files.
Skill Creator GuideWhat is a Skill?Directory StructureSKILL.md FormatFrontmatter (Required)Frontmatter FieldsName RulesDescription Best PracticesGood - specific triggers and use casesBad - vague and unhelpfulBody ContentRecommended Sections
兼容:Works with Claude Code and similar AI coding assistants that support Agent Skills. · 许可:MIT · allowed-tools:Read Write Edit Glob Grep
来源分类:skills.sh agent-skill
nameskill-creatordescriptioncompatibilityallowed-toolsreferences/topic-a.mdreferences/topic-b.mdreferences/setup.mdreferences/patterns.mdscripts/validate.shreferences/apollo-skills.md以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。
具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗
先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。
该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。
复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。
把 Agent Skill「skill-creator」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-2562d3fa84212e56-%E6%8A%80%E8%83%BD%E5%88%9B%E5%BB%BA%E8%80%85.html 请存为 .cursor/skills/skill-creator/SKILL.md 或 .claude/skills/skill-creator/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。 该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/apollographql/skills 取完整目录,不要只建一个 SKILL.md。
需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。
npx skills add 'https://github.com/apollographql/skills' --list
npx skills add 'https://github.com/apollographql/skills' --skill 'skill-creator'
CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。
This guide helps you create effective skills for Apollo GraphQL and GraphQL development following the Agent Skills specification.
A skill is a directory containing instructions that extend an AI agent's capabilities with specialized knowledge, workflows, or tool integrations. Skills activate automatically when agents detect relevant tasks.
A skill requires at minimum a SKILL.md file:
skill-name/
├── SKILL.md # Required - main instructions
├── references/ # Optional - detailed documentation
│ ├── topic-a.md
│ └── topic-b.md
├── scripts/ # Optional - executable helpers
│ └── validate.sh
├── templates/ # Optional - config/code templates
│ └── config.yaml
└── assets/ # Optional - static resources (images, schemas, data files)
---
name: skill-name
description: >
A clear description of what this skill does and when to use it.
Include trigger conditions: (1) first condition, (2) second condition.
license: MIT
compatibility: Works with Claude Code and similar AI coding assistants.
metadata:
author: your-org
version: "1.0.0"
allowed-tools: Read Write Edit Glob Grep
---
| Field | Required | Description |
|-------|----------|-------------|
| name | Yes | Lowercase, hyphens only. Must match directory name. Max 64 chars. |
| description | Yes | What the skill does and when to use it. Max 1024 chars. |
| license | No | License name (e.g., MIT, Apache-2.0). |
| compatibility | No | Environment requirements. Max 500 chars. |
| metadata | No | Key-value pairs for author, version, etc. |
| allowed-tools | No | Space-delimited list of pre-approved tools. Do not include Bash(curl:*). |
--)Good: apollo-client, graphql-schema, rover
Bad: Apollo-Client, -apollo, apollo--client
Write descriptions that help agents identify when to activate the skill:
# Good - specific triggers and use cases
description: >
Guide for designing GraphQL schemas following industry best practices. Use this skill when:
(1) designing a new GraphQL schema or API,
(2) reviewing existing schema for improvements,
(3) deciding on type structures or nullability,
(4) implementing pagination or error patterns.
# Bad - vague and unhelpful
description: Helps with GraphQL stuff.
The markdown body contains instructions the agent follows. Structure it for clarity:
# Skill Title
Brief overview of what this skill helps with.
## Process
Follow this process when working on [task]:
- [ ] Step 1: Research and understand requirements
- [ ] Step 2: Implement the solution
- [ ] Step 3: Validate the result
## Quick Reference
### Common Pattern
\`\`\`graphql
type Example {
id: ID!
name: String
}
\`\`\`
## Security
> **Risk: [brief description of what can go wrong].**
> [What the user MUST do to prevent it.]
- ALWAYS [secure default behavior]
- NEVER [dangerous configuration] in production
## Reference Files
- [Topic A](references/topic-a.md) - Detailed guide for topic A
- [Topic B](references/topic-b.md) - Detailed guide for topic B
## Key Rules
### Category One
- Rule about this category
- Another rule
### Category Two
- Rule about this category
## Ground Rules
- ALWAYS do this important thing
- NEVER do this problematic thing
- PREFER this approach over that approach
When a skill generates configuration, code, or guidance that could cause security issues if misused, the skill MUST make those risks explicit and visible to the LLM. An LLM cannot infer security implications from context alone — it needs clearly labeled signals.
If any of these apply, the skill is security-sensitive:
Dedicated Security section in SKILL.md or a reference file, labeled ## Security. Not "Private data" or "Customization" — use the word "Security" so the LLM recognizes the category.
Explicit warnings at the point of risk — place security guidance next to the config or code that creates the risk, not in a separate file the LLM may not load:
### Response caching scope
> **Security: data leakage risk.** All cached data is PUBLIC by default.
> User-specific fields MUST use `scope: PRIVATE` with a `private_id`
> configured, or they will be shared across all users.
Validation checklist items — every security-sensitive feature must have corresponding checks in the validation checklist. Group them under a ## Security heading.
Ground rules — add ALWAYS/NEVER rules for security-critical behavior. These are the strongest signal to the LLM.
Require the data model — if correct security configuration depends on understanding the user's data model (e.g., which fields are user-specific), the skill must instruct the LLM to ask the user before generating config. Do not let the LLM guess.
Structure skills to minimize context usage:
name and description load at startup for all skillsSKILL.md loads when skill activatesreferences/ load only when requiredKeep SKILL.md under 500 lines. Move detailed documentation to reference files.
Use references/ for detailed documentation:
references/
├── setup.md # Installation and configuration
├── patterns.md # Common patterns and examples
├── troubleshooting.md # Error solutions
└── api.md # API reference
Reference files should be:
Link to references from SKILL.md:
## Reference Files
- [Setup](references/setup.md) - Installation and configuration
- [Patterns](references/patterns.md) - Common patterns and examples
Use scripts/ for executable helpers agents can run:
scripts/
├── validate.sh # Validation commands
├── setup.py # Setup automation
└── check-version.sh # Version checking
Scripts should be self-contained, include error handling, and have a usage comment at the top. Pre-approve them in allowed-tools (e.g., Bash(./scripts/validate.sh:*)).
Use templates/ for config files, boilerplate, or starter code:
templates/
├── config.yaml # Default configuration
├── config-v2.yaml # Version-specific variant
└── example-app/ # Starter project
Templates are copied or adapted by the agent — not executed directly.
Follow the Apollo Voice for all skill content:
For Apollo GraphQL-specific guidance:
Use semantic versioning ("X.Y.Z") for the version field in metadata:
metadata:
author: apollographql
version: "1.0.0"
Start new skills at "1.0.0".
Before publishing a skill, verify:
name matches directory name and follows naming rulesdescription clearly states what the skill does and when to use itSKILL.md is under 500 linesallowed-tools to pre-approve tools the skill needsBash(curl:*) in allowed-tools as it grants unrestricted network access and enables curl | sh remote code execution patterns## Security section when the skill generates config or code that controls access, caching, auth, secrets, or data exposure> **Security: ...**) next to config or code that creates security risks## Security heading写作与研究
从文本中删除 AI 生成的写入标记 。 编辑或审查文本时使用,使其声音更自然和人文写作. 基于维基百科的全面"AI写作的标志"指南. 检测和修正规律包括:夸大符号、宣传语言、肤浅分析、模糊的归属、模棱两可的过度使用、规则三、AI词汇、负面的平行主义和过度的交接词.
写作与研究
OpenClaw 的默认网络搜索 。 搜索网络跨越了10个引擎——Google,Reddit,GitHub,arXiv,Hacker News等——使用Prismfy. 包括免费等级,不需要信用卡。 包括用于网络搜索、配额检查和引擎/时间/域过滤器的捆绑 " search.sh …
写作与研究
监控博客和RSS/Atom的种子.
写作与研究
AI-优化了使用Tavily Search API的网络搜索. 需要全面网络研究,时事搜索,域名特定搜索,或AI生成的回答摘要时使用. Tavily是LLM消费的优化型,具有清洁的结构化结果,答案生成,以及原始内容提取. 最适合研究任务、新闻查询、实况调查和收集权威来源.