yaojingang
38 lines
3.0 KiB
JSON
38 lines
3.0 KiB
JSON
{
|
|
"job": "Turn repeated workflows, prompts, transcripts, runbooks, documents, or existing skill packages into routeable, evaluable, packageable, and governable agent skills for personal, team, library, or governed reuse.",
|
|
"real_inputs": [
|
|
"rough workflow notes, SOPs, runbooks, prompts, transcripts, documents, or repeated task descriptions",
|
|
"an existing skill directory that needs refactor, evaluation, packaging, or governance hardening",
|
|
"target platform requirements such as OpenAI, Claude, generic Agent Skills, or team distribution",
|
|
"benchmark references, local constraints, desired maturity tier, and review standards"
|
|
],
|
|
"primary_output": "A working skill package with lean SKILL.md, aligned agents/interface.yaml, justified references, scripts only when useful, eval evidence, reports, packaging metadata, and clear next iteration recommendations.",
|
|
"description": "Create, refactor, evaluate, and package agent skills from workflows, prompts, transcripts, docs, or notes. Use when asked to create a skill, turn a repeated process into a reusable skill, improve an existing skill, add evals, or package a skill for team reuse.",
|
|
"exclusions": [
|
|
"one-off writing, translation, explanation, or brainstorming requests that do not need a reusable skill",
|
|
"general code review or debugging unless the user is packaging that workflow as a skill",
|
|
"raw private material that was not intentionally supplied as skill evidence",
|
|
"platform-specific plugin creation when the request is not about an agent skill package"
|
|
],
|
|
"constraints": [
|
|
"keep SKILL.md lean and route primarily through frontmatter description",
|
|
"put durable guidance in references, executable logic in scripts, and evidence in reports",
|
|
"default to the lightest reliable mode before adding governance weight",
|
|
"preserve portability across OpenAI, Claude, generic, and Agent Skills compatible targets",
|
|
"avoid raw prompt, output, transcript, or private content in telemetry"
|
|
],
|
|
"standards": [
|
|
"trigger boundaries must be tested with should-trigger and should-not-trigger cases",
|
|
"production and higher maturity work needs output eval, trust, runtime conformance, and Review Studio evidence",
|
|
"governed work needs owner, review cadence, permission approvals, registry metadata, package verification, and install simulation",
|
|
"generated reports should be bilingual or reviewer-friendly when they are user-facing",
|
|
"each new asset must earn its place by reducing ambiguity, risk, or repeated work"
|
|
],
|
|
"correction": "The 2.0 direction reframes this package from a Meta Skill factory into a Skill OS with Skill IR, compiler contracts, output eval, runtime conformance, trust, registry, Review Studio, Skill Atlas, and telemetry loops.",
|
|
"user_references": [
|
|
"Yao Meta Skill 2.0 upgrade plan",
|
|
"Kami-style white report layout requirements for generated skill reports",
|
|
"local Waza engineering habits for review, design, diagnosis, and implementation discipline"
|
|
]
|
|
}
|