pactile-skill-creator
Create or improve Pactile-compatible agent skills. Use when the user asks to author a project-local skill, shared .agents skill, platform-specific skill, or upstream Pactile bundled skill.
- License 许可
- AGPL-3.0
- 所属仓库
- blxzer77/pactile
- 最近更新
- 2026-10-01
- Stars
- ★ 16
- Forks
- 0
01 前言 Front Matter
- name
- pactile-skill-creator
- description
- Create or improve Pactile-compatible agent skills. Use when the user asks to author a project-local skill, shared .agents skill, platform-specific skill, or upstream Pactile bundled skill.
02 资源文件 4
- 参考文档references/authoring-rules.md6.6 KB
- 参考文档references/general-authoring.md5.9 KB
- 参考文档references/pactile-skill-locations.md763 B
- 参考文档references/review-checklist.md2.5 KB
03 SKILL.md 正文
Pactile Skill Creator
Create high-quality skills for Pactile-managed projects and Pactile bundled templates. This unified guide covers general authoring method plus Pactile packaging constraints.
This skill is the authoring and review guide for skill files. It is not the local Pactile architecture map. Use pactile-meta first when the user needs to understand or customize .pactile/, hooks, settings, commands, prompts, workflows, agents, or platform directory layout.
Hard Constraints
- Always inspect existing skill directories and platform conventions before creating or changing a skill.
- Always keep
SKILL.mdunder 500 lines, in English, and focused on trigger, constraints, workflow, references, and boundaries. - Always use lowercase letters, numbers, and hyphens in the frontmatter
name. - Always write a trigger-rich frontmatter
descriptionthat states what the skill does (WHAT) and when it should trigger (WHEN). - Always place safety, sequencing, and reliability rules in a
## Hard Constraintssection before## Workflow. - Always write Hard Constraints (and any other rule list) as imperative one-liners ("Always X. Never Y."). Never bury rules in prose paragraphs.
- Always move long guidance, examples, prompts, and reference material into directly linked files.
- Always make helper scripts deterministic, runnable from the skill directory, and explicit about inputs and outputs.
- Never repeat the same rule in two sections — Hard Constraints is the single source of truth.
- Never duplicate
pactile-metaarchitecture guidance or project-private conventions inside a public Pactile skill. - Never edit a host's built-in Skill creator to implement a Pactile project Skill.
Workflow
- Classify the target skill location and read
references/pactile-skill-locations.md. - Gather requirements (six elements): purpose and scope, trigger scenarios, target location, domain constraints (tools / APIs / reliability), output style, and existing patterns. Infer from conversation context when available; ask the user when discrete choices are ambiguous. Capture tool budget and overlap with existing skills.
- Design, then draft: choose a specific skill name, write a trigger-rich description, decide script / no-script, and define success and stop criteria. Draft or revise
SKILL.mdusingreferences/authoring-rules.mdandreferences/general-authoring.md. - Add
references/,examples/,prompts/, orscripts/only when they reduce entry-file size or make execution more deterministic. - Verify the result with
references/review-checklist.md. - Report changed files, validation performed, and any boundaries or follow-up work.
References
references/pactile-skill-locations.md: Choose project-local, shared, platform-specific, or upstream bundled skill locations.references/authoring-rules.md: Frontmatter, trigger descriptions, hard-constraint form, progressive disclosure, writing-for-agents techniques, deterministic scripts, and anti-patterns.references/general-authoring.md: General authoring method — principles, directory layout, patterns, utility scripts, and the minimal template.references/review-checklist.md: Final quality checklist before handing off a skill change.
When NOT To Use
- Do not use for general Pactile architecture discovery; use
pactile-meta. - Do not use for project coding conventions that belong in
.pactile/spec/. - Do not use for one-off commands or prompts unless the user wants a durable auto-triggered capability.
- Do not use for non-Pactile global skill installation or platform configuration unless the user explicitly asks for that scope.
04 同仓库更多 Skills
external-review
User-installed review workflow that Pactile may borrow but never delete.
team-skill
Existing team workflow with no Pactile ownership record.
verify-basic
Verify observable behavior at pre-agreed public seams.
observability-local
Record sanitized local execution and decision evidence.
intake-basic
Scope new work before creating an independently acceptable Task.
execute-agent
Implement the approved change inside the frozen write set.