update-skill

Name: update-skill
Author: warpdotdev

15kinstalls1forks

How to install update-skill?

warpdotdev/common-skills/update-skill

$npx -y skills add warpdotdev/common-skills --skill update-skill

Installs into the current project.

Summary

Create or update skills by generating, editing, or refining SKILL.md files in this repository. Use when authoring new skills or revising the structure, frontmatter, or guidance for existing ones.

Files · 1

View on GitHub

SKILL.md

1	# update-skill
2
3	This guide provides instructions for creating or updating skills in this repository. It covers the required structure, frontmatter, and best practices for skills.
4
5	## Quick Start
6
7	Every skill is a directory containing a `SKILL.md` file with YAML frontmatter and markdown body:
8
9	```markdown
10	---
11	name: pdf-processing
12	description: Extract text and tables from PDF files, fill forms, merge documents.
13	---
14
15	# PDF Processing
16
17	## When to use this skill
18	Use this skill when the user needs to work with PDF files...
19
20	## How to extract text
21	1. Use pdfplumber for text extraction...
22
23	## How to fill forms
24	...
25	```
26
27	## Requirements
28
29	### Frontmatter (Required)
30
31	Every SKILL.md must start with YAML frontmatter containing:
32
33	- name: Kebab-case identifier (lowercase letters, numbers, hyphens only)
34	- Example: `add-feature-flag`, `pdf-processing`, `update-skill`
35	- description: Specific description of what the skill does and when to use it
36	- Must be non-empty
37	- Should include key terms for skill discovery
38	- Begin with an action verb to clearly state what the skill accomplishes (e.g., "Adds feature flags..." instead of "Helps with features..."), and immediately follow with a specific use case or context (e.g., "Use when working with feature flags")
39	- Write in third person (e.g., "Adds feature flags..." not "I can help you add...")
40
41	### Writing Effective Descriptions
42
43	The description field is critical for skill discovery. Include both what the skill does and when to use it. Some good examples:
44
45	- `git-commit`: "Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes."
46	- `pdf-processing`: "Extract text and tables from PDF files, fill forms, merge documents. Use when working with PDF files or when the user mentions PDFs, forms, or document extraction."
47
48	Avoid vague descriptions like "Helps with code" or "Does development tasks". For more context, see "Description Best Practices" in [references/best-practices.md](references/best-practices.md).
49
50	### Skill Structure
51
52	Typical sections in Warp skills:
53
54	1. Title and brief summary – Clear title and a concise overview of the skill's purpose and primary use cases. Link to sections, reference files or related skills if useful
55	2. Overview - Context about the skill's purpose (optional but common), extends the summary with more details and context
56	3. Main content - Steps, usage instructions, or workflow guidance
57	4. Best Practices - Guidelines and recommendations (optional)
58	5. Examples / Reference PRs - Links to real examples (optional)
59
60	Keep the structure flexible based on the skill's needs. Simple skills can omit the optional sections.
61
62	### Validation
63
64	Optionally, use the [skills-ref](https://github.com/agentskills/agentskills/tree/main/skills-ref) reference library to validate your skills:
65
66	```bash
67	skills-ref validate ./my-skill
68	```
69
70	This checks that your SKILL.md frontmatter is valid and follows all naming conventions. If not installed, use the WebSearch tool to get context around this package.
71
72	### Main Content Best Practices
73
74	- For guidance on what qualifies as good main content, see "Conciseness Principles" in [references/best-practices.md](references/best-practices.md)
75	- When formatting code examples, see "Code Example Formatting" in [references/best-practices.md](references/best-practices.md).
76
77	### File Organization
78
79	- Simple skills (<=200 lines): Keep everything in SKILL.md
80	- Complex skills (>200 lines): Split detailed content into `references/` subdirectory
81	- Reference files from SKILL.md with clear links
82	- Example: "See [references/best-practices.md](references/best-practices.md) for detailed guidance"
83
84	## When to Split Content
85
86	Create `references/` subdirectory when:
87
88	- SKILL.md approaches 200+ lines
89	- Skill covers multiple domains or workflows that can be loaded independently
90	- Detailed reference material would clutter the main instructions
91
92	Keep only essential workflow and procedural instructions in SKILL.md. Move detailed reference material, schemas, and extensive examples to `references/` files.
93
94	## Examples from Existing Skills
95
96	For reference on structure and style:
97
98	- `.agents/skills/add-feature-flag/SKILL.md` - Multi-step workflow with clear sequential steps
99	- `.agents/skills/remove-feature-flag/SKILL.md` - Cleanup workflow with search commands
100
101	## Best Practices
102
103	See [references/best-practices.md](references/best-practices.md) for detailed authoring guidance including:
104
105	- Progressive disclosure patterns
106	- Writing concise, effective instructions
107	- Code example formatting
108	- Common anti-patterns to avoid

People who liked this also viewed

6 picks

Type

lark-drive飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sSkillsJul 2026382k16k
lark-sharedUse for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handlingSkillsJul 2026382k16k
lark-whiteboard飞书画板：查询和编辑飞书云文档中的画板。支持导出画板为预览图片、导出原始节点结构、使用多种格式更新画板内容。当用户需要查看画板内容、导出画板图片、编辑画板时使用此 skill。不负责：飞书云文档内容编辑（lark-doc）、文档内嵌电子表格/Base（lark-sheets / lark-base）。SkillsJul 2026380k16k
lark-task飞书任务：管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更新智能体主页数据、写入任务记录时使用。SkillsJul 2026380k16k
lark-attendance飞书考勤打卡：查询自己的考勤打卡记录SkillsJul 2026330k16k
lark-apps妙搭（Spark/Miaoda）应用开发与托管：应用创建、本地全栈开发、云端生成迭代、创意设计（UI mockup / 可交互原型 / 线框图 / 落地页 / 仪表盘 / 幻灯片 deck / 视觉探索）、AI相关能力和飞书平台能力或者其他外部能力集成、日志/Trace/监控指标/PV/UV 查询、环境变量管理、应用角色与成员管理、自动化触发器（定时/记录变更/Webhook/飞书审批）。当用户要SkillsJul 2026227k16k

update-skill

15kinstalls1forks

View on GitHub

How to install update-skill?

warpdotdev/common-skills/update-skill

$npx -y skills add warpdotdev/common-skills --skill update-skill

Installs into the current project.

Summary

Create or update skills by generating, editing, or refining SKILL.md files in this repository. Use when authoring new skills or revising the structure, frontmatter, or guidance for existing ones.

Files · 1

View on GitHub

SKILL.md

1	# update-skill
2
3	This guide provides instructions for creating or updating skills in this repository. It covers the required structure, frontmatter, and best practices for skills.
4
5	## Quick Start
6
7	Every skill is a directory containing a `SKILL.md` file with YAML frontmatter and markdown body:
8
9	```markdown
10	---
11	name: pdf-processing
12	description: Extract text and tables from PDF files, fill forms, merge documents.
13	---
14
15	# PDF Processing
16
17	## When to use this skill
18	Use this skill when the user needs to work with PDF files...
19
20	## How to extract text
21	1. Use pdfplumber for text extraction...
22
23	## How to fill forms
24	...
25	```
26
27	## Requirements
28
29	### Frontmatter (Required)
30
31	Every SKILL.md must start with YAML frontmatter containing:
32
33	- name: Kebab-case identifier (lowercase letters, numbers, hyphens only)
34	- Example: `add-feature-flag`, `pdf-processing`, `update-skill`
35	- description: Specific description of what the skill does and when to use it
36	- Must be non-empty
37	- Should include key terms for skill discovery
38	- Begin with an action verb to clearly state what the skill accomplishes (e.g., "Adds feature flags..." instead of "Helps with features..."), and immediately follow with a specific use case or context (e.g., "Use when working with feature flags")
39	- Write in third person (e.g., "Adds feature flags..." not "I can help you add...")
40
41	### Writing Effective Descriptions
42
43	The description field is critical for skill discovery. Include both what the skill does and when to use it. Some good examples:
44
45	- `git-commit`: "Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes."
46	- `pdf-processing`: "Extract text and tables from PDF files, fill forms, merge documents. Use when working with PDF files or when the user mentions PDFs, forms, or document extraction."
47
48	Avoid vague descriptions like "Helps with code" or "Does development tasks". For more context, see "Description Best Practices" in [references/best-practices.md](references/best-practices.md).
49
50	### Skill Structure
51
52	Typical sections in Warp skills:
53
54	1. Title and brief summary – Clear title and a concise overview of the skill's purpose and primary use cases. Link to sections, reference files or related skills if useful
55	2. Overview - Context about the skill's purpose (optional but common), extends the summary with more details and context
56	3. Main content - Steps, usage instructions, or workflow guidance
57	4. Best Practices - Guidelines and recommendations (optional)
58	5. Examples / Reference PRs - Links to real examples (optional)
59
60	Keep the structure flexible based on the skill's needs. Simple skills can omit the optional sections.
61
62	### Validation
63
64	Optionally, use the [skills-ref](https://github.com/agentskills/agentskills/tree/main/skills-ref) reference library to validate your skills:
65
66	```bash
67	skills-ref validate ./my-skill
68	```
69
70	This checks that your SKILL.md frontmatter is valid and follows all naming conventions. If not installed, use the WebSearch tool to get context around this package.
71
72	### Main Content Best Practices
73
74	- For guidance on what qualifies as good main content, see "Conciseness Principles" in [references/best-practices.md](references/best-practices.md)
75	- When formatting code examples, see "Code Example Formatting" in [references/best-practices.md](references/best-practices.md).
76
77	### File Organization
78
79	- Simple skills (<=200 lines): Keep everything in SKILL.md
80	- Complex skills (>200 lines): Split detailed content into `references/` subdirectory
81	- Reference files from SKILL.md with clear links
82	- Example: "See [references/best-practices.md](references/best-practices.md) for detailed guidance"
83
84	## When to Split Content
85
86	Create `references/` subdirectory when:
87
88	- SKILL.md approaches 200+ lines
89	- Skill covers multiple domains or workflows that can be loaded independently
90	- Detailed reference material would clutter the main instructions
91
92	Keep only essential workflow and procedural instructions in SKILL.md. Move detailed reference material, schemas, and extensive examples to `references/` files.
93
94	## Examples from Existing Skills
95
96	For reference on structure and style:
97
98	- `.agents/skills/add-feature-flag/SKILL.md` - Multi-step workflow with clear sequential steps
99	- `.agents/skills/remove-feature-flag/SKILL.md` - Cleanup workflow with search commands
100
101	## Best Practices
102
103	See [references/best-practices.md](references/best-practices.md) for detailed authoring guidance including:
104
105	- Progressive disclosure patterns
106	- Writing concise, effective instructions
107	- Code example formatting
108	- Common anti-patterns to avoid

People who liked this also viewed

6 picks

Type