peon-ping-create-pack
Internal — invoked headlessly by `peon create`; humans should run `peon create` instead. Author and render a brand-new PeonPing draft pack — invoked headlessly as: "Use the peon-ping-create-pack skill to draft a pack: name=<n> flavor=<f> vibe=<v> draft_root=<dir>. Follow the skill exactly." Authors all 7 CESP categories honoring the vibe, writes openpeon.json (draft-stamped) and prompts.json, renders every sound via scripts/pack-render.py, and always ends by telling the human to run `peon eval <
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 5050
- Лиценз
- MIT
- Последна проверка на записа
- 21.09.2026 г.
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add PeonPing/peon-pingСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
peon-ping-create-pack
You are drafting ONE brand-new PeonPing pack from scratch. Work only inside the draft directory you create. Do not touch any other directory, do not install anything, do not commit anything, and never finish by declaring the pack "done" or "installed" — a freshly created pack is never installed directly (see Hard rules).
If invoked without name/flavor/vibe/draft_root
This skill is internal: it is only ever invoked headlessly by peon create
with name, flavor, vibe, and draft_root already filled in. If you were
invoked WITHOUT all four (a human ran this directly with missing arguments),
do nothing except tell them to run peon create instead. Do not touch any
files. Exit.
Procedure
- Parse the invocation:
name(already validated by the caller against^[a-z0-9][a-z0-9_-]*$),flavor(sfxorvoice),vibe(a one-line description),draft_root. - Compute
draft_dir = <draft_root>/<name>. If it already exists, STOP — tell the human a draft with that name already exists and to runpeon eval <name>on it (never overwrite an existing draft). Otherwise createdraft_dir/sounds/. - Author a concept honoring the vibe, covering all 7 CESP categories
with at least one sound each:
session.start,task.acknowledge,task.complete,task.error,input.required,resource.limit,user.spam. This mirrors the concept-authoring discipline of thebrand-to-peon-packsskill's step 2:- Every sound needs a
label— short, caption-quality text describing what's heard (not a filename, not a restatement of the category — e.g. "Soft acknowledgement", "Serene completion", not "task_complete_0"). - Keep the aesthetic consistent across all 7 sounds so the pack reads as
one coherent idea, not seven unrelated clips. Let the
vibestring drive instrument palette / tone / register (e.g. "calm bells" implies soft chimes and bowls throughout, never harsh or percussive). flavor: sfx— wordless. Each sound needs aprompt: a concrete, renderable description for ElevenLabs sound-generation (instrument or texture, character, brief shape — e.g. "two gentle bells, soft decay, warm room tone"). Avoid vague adjectives with nothing to render ("nice sound") — describe what would actually produce the sound.flavor: voice— spoken. Each sound needstext(an in-character line fitting the category and vibe) plus a `voi
- Every sound needs a