[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MR4NDSXEY5CDR6RK5DASAC":3,"skill-same:01M6MR4NDSXEY5CDR6RK5DASAC":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":14,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":39,"install":40,"resources":53},"01M6MR4NDSXEY5CDR6RK5DASAC","skill-creator",null,"Use this skill to create a skill for yourself.","tschmz\u002Fimp","tschmz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F250745188?v=4","01M6MR47EQHGG14Z0BE94P1XPY","Thomas Schmitz","01M6MR47K8ZV2H8T8Y5N0CAPQY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Ftschmz\u002Fimp\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fskill-creator\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28],"skill creator","creator","create","use","for","2026-11-10 10:12:30",false,"---\nname: skill-creator\ndescription: Use this skill to create a skill for yourself.\n---\n\n# Skill Creator\n\nUse this skill to add new skills for yourself.\n\n{{#if agent.home}}\nCreate these skills under `{{agent.home}}\u002F.skills\u002F\u003Cskill-name>`.\n{{else}}\nYour home path is not available in this turn. Ask the user for the target directory before creating a skill.\n{{\u002Fif}}\n\n## Hard Rules\n\n- Create skills under `{{agent.home}}\u002F.skills\u002F\u003Cskill-name>`.\n- Put the main instructions in `SKILL.md`.\n- Keep skill names lowercase with hyphens: `^[a-z0-9]+(?:-[a-z0-9]+)*$`.\n- Write the `description` as a direct statement of what the skill helps you do. Avoid phrasing it as \"when the user asks\".\n- Keep the body procedural and short. Put only instructions needed at use time.\n- Add `references\u002F` only for optional longer guidance that should be read on demand.\n- Add `scripts\u002F` only when the workflow needs repeatable executable helpers.\n- Avoid `README.md`, changelogs, install notes, and placeholder files inside the skill.\n\n## Location And Discovery\n\nUse this skill directory:\n\n```text\n{{agent.home}}\u002F.skills\u002F\u003Cskill-name>\n```\n\nDirectory shape:\n\n```text\n{{agent.home}}\u002F\n  .skills\u002F\n    hello-world\u002F\n      SKILL.md\n      scripts\u002F\n        say-hello.sh\n      references\u002F\n        hello-world.md\n```\n\nThe runtime scans one directory level below `.skills`. Each child directory with a `SKILL.md` file is one skill.\n\nA newly created or changed skill is available on your next turn. The current turn's skill list was already resolved before the skill was written.\n\n## Validation\n\n- Check that the skill is a direct child of `{{agent.home}}\u002F.skills`.\n- Check that `name` matches `^[a-z0-9]+(?:-[a-z0-9]+)*$` and stays under 64 characters.\n- Check that the YAML frontmatter contains at least `name` and `description`; additional metadata may be present but should not be required for basic skill loading.\n- Check that `SKILL.md` starts with valid YAML frontmatter. Prefer a concrete example over placeholders:\n\n```markdown\n---\nname: hello-world\ndescription: Use this skill to generate a hello-world greeting for yourself.\n---\n\n# Hello World\n\n1. Run `scripts\u002Fsay-hello.sh`.\n2. Read `references\u002Fhello-world.md`.\n3. Tell the user whether the script succeeded and include one fact from the reference.\n```\n\n- When useful, show a fuller skill layout with bundled resources:\n\n```text\nhello-world\u002F\n  SKILL.md\n  scripts\u002F\n    say-hello.sh\n  references\u002F\n    hello-world.md\n```\n\n- Example bundled script:\n\n```bash\n#!\u002Fusr\u002Fbin\u002Fenv bash\nset -euo pipefail\n\ntarget=\"${1:-world}\"\nprintf 'Hello, %s!\\n' \"$target\"\n```\n\n- Example bundled reference:\n\n```markdown\n# Hello World Reference\n\n`Hello, World!` is the conventional first program in many languages.\n\n## Interesting facts\n\n- Brian Kernighan used `hello` and `world` together in a B tutorial from 1972, which is one of the earliest well-known ancestors of the pattern.\n- A direct C `hello, world` example appeared in Brian Kernighan's Bell Labs memo `Programming in C: A Tutorial` in 1974.\n- The phrase became widely known through the 1978 first edition of `The C Programming Language` by Brian Kernighan and Dennis Ritchie.\n- Early canonical examples used `hello, world` in lowercase and without an exclamation mark.\n- `Hello, World!` is often used as a smoke test to confirm that a language runtime, compiler, or development environment is working.\n- In graphics programming, `Hello Triangle` often plays a similar role: the first milestone is to render one triangle on screen.\n- `helloworldcollection.de` describes itself as a collection with 603 Hello World programs in programming languages plus 78 human languages.\n```\n\n## Runtime Notes\n\n- Skills are re-discovered on each user turn; edits under auto-discovered catalogs do not require a daemon restart.\n- `load_skill` returns the selected `SKILL.md` body and lists bundled `scripts\u002F` and `references\u002F` files.\n- `load_skill` does not read bundled resource contents automatically. Write skills so `SKILL.md` tells the agent what to run or read without needing to inspect script contents first; bundled scripts should usually be executable helpers, not files the agent must read to understand the workflow.\n","# Skill Creator\n\nUse this skill to add new skills for yourself.\n\n{{#if agent.home}}\nCreate these skills under `{{agent.home}}\u002F.skills\u002F\u003Cskill-name>`.\n{{else}}\nYour home path is not available in this turn. Ask the user for the target directory before creating a skill.\n{{\u002Fif}}\n\n## Hard Rules\n\n- Create skills under `{{agent.home}}\u002F.skills\u002F\u003Cskill-name>`.\n- Put the main instructions in `SKILL.md`.\n- Keep skill names lowercase with hyphens: `^[a-z0-9]+(?:-[a-z0-9]+)*$`.\n- Write the `description` as a direct statement of what the skill helps you do. Avoid phrasing it as \"when the user asks\".\n- Keep the body procedural and short. Put only instructions needed at use time.\n- Add `references\u002F` only for optional longer guidance that should be read on demand.\n- Add `scripts\u002F` only when the workflow needs repeatable executable helpers.\n- Avoid `README.md`, changelogs, install notes, and placeholder files inside the skill.\n\n## Location And Discovery\n\nUse this skill directory:\n\n```text\n{{agent.home}}\u002F.skills\u002F\u003Cskill-name>\n```\n\nDirectory shape:\n\n```text\n{{agent.home}}\u002F\n  .skills\u002F\n    hello-world\u002F\n      SKILL.md\n      scripts\u002F\n        say-hello.sh\n      references\u002F\n        hello-world.md\n```\n\nThe runtime scans one directory level below `.skills`. Each child directory with a `SKILL.md` file is one skill.\n\nA newly created or changed skill is available on your next turn. The current turn's skill list was already resolved before the skill was written.\n\n## Validation\n\n- Check that the skill is a direct child of `{{agent.home}}\u002F.skills`.\n- Check that `name` matches `^[a-z0-9]+(?:-[a-z0-9]+)*$` and stays under 64 characters.\n- Check that the YAML frontmatter contains at least `name` and `description`; additional metadata may be present but should not be required for basic skill loading.\n- Check that `SKILL.md` starts with valid YAML frontmatter. Prefer a concrete example over placeholders:\n\n```markdown\n---\nname: hello-world\ndescription: Use this skill to generate a hello-world greeting for yourself.\n---\n\n# Hello World\n\n1. Run `scripts\u002Fsay-hello.sh`.\n2. Read `references\u002Fhello-world.md`.\n3. Tell the user whether the script succeeded and include one fact from the reference.\n```\n\n- When useful, show a fuller skill layout with bundled resources:\n\n```text\nhello-world\u002F\n  SKILL.md\n  scripts\u002F\n    say-hello.sh\n  references\u002F\n    hello-world.md\n```\n\n- Example bundled script:\n\n```bash\n#!\u002Fusr\u002Fbin\u002Fenv bash\nset -euo pipefail\n\ntarget=\"${1:-world}\"\nprintf 'Hello, %s!\\n' \"$target\"\n```\n\n- Example bundled reference:\n\n```markdown\n# Hello World Reference\n\n`Hello, World!` is the conventional first program in many languages.\n\n## Interesting facts\n\n- Brian Kernighan used `hello` and `world` together in a B tutorial from 1972, which is one of the earliest well-known ancestors of the pattern.\n- A direct C `hello, world` example appeared in Brian Kernighan's Bell Labs memo `Programming in C: A Tutorial` in 1974.\n- The phrase became widely known through the 1978 first edition of `The C Programming Language` by Brian Kernighan and Dennis Ritchie.\n- Early canonical examples used `hello, world` in lowercase and without an exclamation mark.\n- `Hello, World!` is often used as a smoke test to confirm that a language runtime, compiler, or development environment is working.\n- In graphics programming, `Hello Triangle` often plays a similar role: the first milestone is to render one triangle on screen.\n- `helloworldcollection.de` describes itself as a collection with 603 Hello World programs in programming languages plus 78 human languages.\n```\n\n## Runtime Notes\n\n- Skills are re-discovered on each user turn; edits under auto-discovered catalogs do not require a daemon restart.\n- `load_skill` returns the selected `SKILL.md` body and lists bundled `scripts\u002F` and `references\u002F` files.\n- `load_skill` does not read bundled resource contents automatically. Write skills so `SKILL.md` tells the agent what to run or read without needing to inspect script contents first; bundled scripts should usually be executable helpers, not files the agent must read to understand the workflow.\n",{"name":5,"description":7},"main","5c55adc9bc538ca2feda7f1e3cc1ed32de1d472a","assets\u002Fskills\u002Fskill-creator","https:\u002F\u002Fgithub.com\u002Ftschmz\u002Fimp","https:\u002F\u002Fgithub.com\u002Ftschmz","2026-08-23 22:45:40",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add tschmz\u002Fimp --skill skill-creator",{"tool":46,"command":47},"bunx","bunx skills add tschmz\u002Fimp --skill skill-creator",{"tool":49,"command":50},"pnpm","pnpm dlx skills add tschmz\u002Fimp --skill skill-creator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftschmz\u002Fimp\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fskill-creator\u002FSKILL.md",true,[],[55,72,90,101,112],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":29},"01M6MR4VPKDWZFS9857JWHQ4MC","release-preparation","Use this skill when the user wants to prepare, document, version, tag, or validate a software release.","https:\u002F\u002Fgithub.com\u002Ftschmz\u002Fimp\u002Fblob\u002Fmain\u002Fplugins\u002Fimp-agents\u002Fskills\u002Frelease-preparation\u002FSKILL.md",[],[62,63,64,65,66,67,27,68,69,70,71],"release","release preparation","preparation","validate","prepare","user","version","document","software release","software",{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":29},"01M6MR4QWADESAXV08P0BBSX73","imp-administration","Use this skill to inspect, configure, diagnose, back up, restore, or manage the live Imp installation.","https:\u002F\u002Fgithub.com\u002Ftschmz\u002Fimp\u002Fblob\u002Fmain\u002Fplugins\u002Fimp-agents\u002Fskills\u002Fimp-administration\u002FSKILL.md",[],[79,80,81,82,83,84,85,86,87,88,27,89],"imp administration","administration","manage","live","installation","inspect","back","configure","restore","diagnose","up",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":29},"01M6MR4J402XBC5JWEE4SEECMY","plugin-creator","Use this skill to create or debug a plugin that adds tools for yourself.","https:\u002F\u002Fgithub.com\u002Ftschmz\u002Fimp\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fplugin-creator\u002FSKILL.md",[],[97,98,25,99,26,100,27,28],"plugin","plugin creator","debug","Tools",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":29},"01M6MR4FZ0XT2R11JRHH3G4YHK","current-time","Use this skill to get the current local date and time.","https:\u002F\u002Fgithub.com\u002Ftschmz\u002Fimp\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fcurrent-time\u002FSKILL.md",[],[108,109,110,27,111],"current time","time","get","local",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":29},"01M6MR4C14YA6CPH620RM6KPPK","commit","Use this skill when creating commits in this repository; enforce the repository commit message format.","https:\u002F\u002Fgithub.com\u002Ftschmz\u002Fimp\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcommit\u002FSKILL.md",[],[114,119,120,121,122,27,123,124],"commit message","repository","commits","format","message","enforce"]