Menu

Individual skill

aweskill-creator

Use when creating, authoring, or improving a skill: scaffold a new skill, draft SKILL.md content, write trigger descriptions, test with realistic prompts, iterate wording, turn a repeated workflow from the current conversation into a reusable skill, or customize an installed skill. 中文触发词：制作技能、创建技能、新建skill、写一个技能、把这段流程做成技能、技能创作、改进技能、改进触发词、定制已安装技能。

resources/skills/aweskill-creator/SKILL.md

Read pinned source

Source commit 89d7bbbca45c2c9e9ff29de5c60438eb885dfe21

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
36
Repository last updated
Oct 2, 2026
License
MPL-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Aweskill Creator

The creative loop is yours; the mechanics belong to the aweskill CLI. You interview, draft, test, and revise. The CLI guarantees valid scaffolding, frontmatter, and lifecycle. Read `references/writing-guide.md` before drafting skill prose.

## The Loop

1. **Capture intent.** If the current conversation already shows a workflow worth capturing, extract it from history first (tools used, step order, corrections, input/output formats). Confirm gaps with the user before drafting: what should the skill enable, when should it trigger, what output format, which examples pin the behavior down.
2. **Check for existing skills first.** Run `aweskill find <query>` and `aweskill store list --verbose`. Reuse, fork, or improve an existing skill before writing a new one.
3. **Scaffold.** Run `aweskill store create <name> --description "<trigger description>"`. The command validates the name, checks for conflicts, and writes a valid SKILL.md skeleton with `references/`.
4. **Draft the body.** Fill the skeleton following `references/writing-guide.md`. Keep the body under ~500 lines; move detail into `references/` files and link them from the body.
5. **Project and test.** Run `aweskill agent add skill <name> --global --agent <agent-id>`, then try 2–3 realistic test prompts in fresh turns. Projections are symlinks: edits to the central-store copy go live immediately, so you can iterate without re-projecting.
6. **Validate the mechanics.** Run `aweskill doctor fix-skills --skill <name>` (dry-run). Fix anything actionable before finishing.
7. **Improve and repeat.** Generalize feedback instead of layering rules, cut guidance that is not pulling its weight, rerun the test prompts. Stop when changes stop helping.
8. **Finish.** Group it with `aweskill bundle add <bundle> <name>`, or publish it: copy the skill directory into its own git repo so others can `aweskill install owner/repo`.