[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CNN9CPR0J46B300NMVRYZ5":3,"skill-same:01M7CNN9CPR0J46B300NMVRYZ5":56},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7CNN9CPR0J46B300NMVRYZ5","init",null,"Register the developer-plenger skill pack by writing AGENTS.md at the repo root — the pack's workflow, artifacts, skill rules and task-state contract — and create the empty context.md that every later skill updates. Use for \u002Finit, when onboarding a repository to the pack, or when AGENTS.md is missing or has drifted from the pack contract. Asks the user nothing and inspects no project facts; it does not create the project, pick a stack, or describe what the project is.","arbasyaa\u002Fmy-pi-setup","arbasyaa","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F233517565?v=4","01M7CNHFSZRYGVHAPH9HAD7YF0","Arbasya Anandito","01M7CNHFTN4QAT1R8NRS4XRYTP",3,"MIT","https:\u002F\u002Fgithub.com\u002Farbasyaa\u002Fmy-pi-setup\u002Fblob\u002Fmain\u002Fskills\u002Finit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: init\ndescription: >\n  Register the developer-plenger skill pack by writing AGENTS.md at the repo\n  root — the pack's workflow, artifacts, skill rules and task-state contract —\n  and create the empty context.md that every later skill updates. Use for\n  \u002Finit, when onboarding a repository to the pack, or when AGENTS.md is\n  missing or has drifted from the pack contract. Asks the user nothing and\n  inspects no project facts; it does not create the project, pick a stack, or\n  describe what the project is.\n---\n\n# Init — register the skill pack\n\n`\u002Finit` writes two files at the repo root so every later skill knows which skills exist, what each one produces, where each artifact lives, and what the project currently is:\n\n- `AGENTS.md` — the pack contract. Identical in every project; it is the pack's rules, not a description of the project.\n- `context.md` — the project's memory, created **empty**: thirteen sections and nothing in them, because nothing has been planned yet and `\u002Finit` inspects nothing.\n\nThe run is: read what exists, compare it against the contract, write if it does not conform, report. `\u002Finit` asks the user nothing — there is no project-specific content to gather. It never inspects the codebase to infer a stack, a purpose or an architecture; those are project facts and belong to `\u002Fplan`, which records them in `context.md` and in `specs\u002FNN-\u003Cplan-slug>\u002Fspec.md`.\n\nRead `references\u002Fagents-template.md` before step 2 for the `AGENTS.md` contract — the canonical text, the conformance checklist, the merge rule for an existing file, and the `CLAUDE.md` dispositions. Read `skills\u002Fplan\u002Freferences\u002Fcontext.md` before step 5 for the `context.md` shape that step writes.\n\n## Steps\n\n### 1. Read what already exists\n\nRead, in this order, and only if present:\n\n1. `AGENTS.md` at the repo root\n2. `CLAUDE.md` at the repo root\n3. `context.md` at the repo root\n\n**Done when:** you know whether `AGENTS.md` exists, whether `context.md` exists, and whether a `CLAUDE.md` needs a disposition decision.\n\n### 2. Compare AGENTS.md against the contract\n\nOpen `references\u002Fagents-template.md` §3 and check the existing file, section by\nsection, against the canonical text in §2. There is nothing to detect and nothing\nto infer: the expected content is fixed, so this is a comparison.\n\nIf `AGENTS.md` is absent, this step is trivially \"non-conformant\" and you go\nstraight to writing it.\n\n**Done when:** you can name every section that is missing or drifted, or state that none is.\n\n### 3. Write AGENTS.md\n\n- **Absent** — write the canonical text from `references\u002Fagents-template.md` §2\n  verbatim.\n- **Present and conformant** — write nothing.\n- **Present and drifted or incomplete** — write the canonical version into place,\n  following the merge rule in §4: never clobber content that is not a pack\n  section, never reshuffle the user's own sections.\n\nNever resolve a section by guessing project facts. Nothing in this file is\nproject-specific, so there is nothing to infer.\n\n**Done when:** `AGENTS.md` at the repo root matches the contract, or was already matching.\n\n### 4. Resolve CLAUDE.md, if present\n\nIf `CLAUDE.md` exists, apply the dispositions in `references\u002Fagents-template.md`\n§4 and say plainly which file is canonical and whether the other becomes a\nsymlink or a short pointer. If it does not exist, do nothing here.\n\n**Done when:** the user has been told which files you wrote, and — when a `CLAUDE.md` exists — which file is canonical and what happens to the other.\n\n### 5. Create context.md, or reset its cursor\n\nFollow `skills\u002Fplan\u002Freferences\u002Fcontext.md` for the exact shape.\n\n- **Absent** — write the thirteen sections, all empty, with `Current Phase` set to `INIT`. Empty means blank, not `unknown`: `\u002Fplan` is the run that fills this file, and a placeholder here invites a later skill to treat a guess as a fact.\n- **Present** — set `Current Phase` to `INIT` and change nothing else. The project's facts belong to `\u002Fplan`.\n\nCreate no directory here. `specs\u002F` is created by `\u002Fplan`, and a fresh clone should have no `specs\u002F` tree until a plan is actually written.\n\n**Done when:** `context.md` exists with the thirteen sections and `Current Phase: INIT`, or was already present with only its cursor changed.\n\n### 6. Report\n\nTell the user: whether `AGENTS.md` was created, repaired, or already conformant; whether `context.md` was created or left in place; any non-pack content you preserved and where it belongs if it is still sitting in `AGENTS.md`; any decision taken about `CLAUDE.md`; and the next command to run — `\u002Fplan \u003Cidea>`.\n\n**Done when:** the user knows the state of both files and what to run next.\n","# Init — register the skill pack\n\n`\u002Finit` writes two files at the repo root so every later skill knows which skills exist, what each one produces, where each artifact lives, and what the project currently is:\n\n- `AGENTS.md` — the pack contract. Identical in every project; it is the pack's rules, not a description of the project.\n- `context.md` — the project's memory, created **empty**: thirteen sections and nothing in them, because nothing has been planned yet and `\u002Finit` inspects nothing.\n\nThe run is: read what exists, compare it against the contract, write if it does not conform, report. `\u002Finit` asks the user nothing — there is no project-specific content to gather. It never inspects the codebase to infer a stack, a purpose or an architecture; those are project facts and belong to `\u002Fplan`, which records them in `context.md` and in `specs\u002FNN-\u003Cplan-slug>\u002Fspec.md`.\n\nRead `references\u002Fagents-template.md` before step 2 for the `AGENTS.md` contract — the canonical text, the conformance checklist, the merge rule for an existing file, and the `CLAUDE.md` dispositions. Read `skills\u002Fplan\u002Freferences\u002Fcontext.md` before step 5 for the `context.md` shape that step writes.\n\n## Steps\n\n### 1. Read what already exists\n\nRead, in this order, and only if present:\n\n1. `AGENTS.md` at the repo root\n2. `CLAUDE.md` at the repo root\n3. `context.md` at the repo root\n\n**Done when:** you know whether `AGENTS.md` exists, whether `context.md` exists, and whether a `CLAUDE.md` needs a disposition decision.\n\n### 2. Compare AGENTS.md against the contract\n\nOpen `references\u002Fagents-template.md` §3 and check the existing file, section by\nsection, against the canonical text in §2. There is nothing to detect and nothing\nto infer: the expected content is fixed, so this is a comparison.\n\nIf `AGENTS.md` is absent, this step is trivially \"non-conformant\" and you go\nstraight to writing it.\n\n**Done when:** you can name every section that is missing or drifted, or state that none is.\n\n### 3. Write AGENTS.md\n\n- **Absent** — write the canonical text from `references\u002Fagents-template.md` §2\n  verbatim.\n- **Present and conformant** — write nothing.\n- **Present and drifted or incomplete** — write the canonical version into place,\n  following the merge rule in §4: never clobber content that is not a pack\n  section, never reshuffle the user's own sections.\n\nNever resolve a section by guessing project facts. Nothing in this file is\nproject-specific, so there is nothing to infer.\n\n**Done when:** `AGENTS.md` at the repo root matches the contract, or was already matching.\n\n### 4. Resolve CLAUDE.md, if present\n\nIf `CLAUDE.md` exists, apply the dispositions in `references\u002Fagents-template.md`\n§4 and say plainly which file is canonical and whether the other becomes a\nsymlink or a short pointer. If it does not exist, do nothing here.\n\n**Done when:** the user has been told which files you wrote, and — when a `CLAUDE.md` exists — which file is canonical and what happens to the other.\n\n### 5. Create context.md, or reset its cursor\n\nFollow `skills\u002Fplan\u002Freferences\u002Fcontext.md` for the exact shape.\n\n- **Absent** — write the thirteen sections, all empty, with `Current Phase` set to `INIT`. Empty means blank, not `unknown`: `\u002Fplan` is the run that fills this file, and a placeholder here invites a later skill to treat a guess as a fact.\n- **Present** — set `Current Phase` to `INIT` and change nothing else. The project's facts belong to `\u002Fplan`.\n\nCreate no directory here. `specs\u002F` is created by `\u002Fplan`, and a fresh clone should have no `specs\u002F` tree until a plan is actually written.\n\n**Done when:** `context.md` exists with the thirteen sections and `Current Phase: INIT`, or was already present with only its cursor changed.\n\n### 6. Report\n\nTell the user: whether `AGENTS.md` was created, repaired, or already conformant; whether `context.md` was created or left in place; any non-pack content you preserved and where it belongs if it is still sitting in `AGENTS.md`; any decision taken about `CLAUDE.md`; and the next command to run — `\u002Fplan \u003Cidea>`.\n\n**Done when:** the user knows the state of both files and what to run next.\n",{"name":5,"description":7},"main","a77e29f9fe4e5a5ee9cc856535ba243064ce91eb","skills\u002Finit",0,"https:\u002F\u002Fgithub.com\u002Farbasyaa\u002Fmy-pi-setup","https:\u002F\u002Fgithub.com\u002Farbasyaa","Mahasiswa Teknik Informatika politeknik Negeri Cilacap","2026-10-29 12:35:34",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add arbasyaa\u002Fmy-pi-setup --skill init",{"tool":38,"command":39},"bunx","bunx skills add arbasyaa\u002Fmy-pi-setup --skill init",{"tool":41,"command":42},"pnpm","pnpm dlx skills add arbasyaa\u002Fmy-pi-setup --skill init","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Farbasyaa\u002Fmy-pi-setup\u002Fblob\u002Fmain\u002Fskills\u002Finit\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",372,"https:\u002F\u002Fgithub.com\u002Farbasyaa\u002Fmy-pi-setup\u002Fblob\u002Fmain\u002Fskills\u002Finit\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fagents-template.md",12944,"https:\u002F\u002Fgithub.com\u002Farbasyaa\u002Fmy-pi-setup\u002Fblob\u002Fmain\u002Fskills\u002Finit\u002Freferences\u002Fagents-template.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7CNSESD7DRZ47PPA5Y59J8W","writing-shape","Writing, exploit: shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002Farbasyaa\u002Fmy-pi-setup\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-shape\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CNSD0Y1KH71ZYSQY4ZP2PY","writing-fragments","Writing, explore: mine raw fragments, no structure yet.","https:\u002F\u002Fgithub.com\u002Farbasyaa\u002Fmy-pi-setup\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-fragments\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CNSAWBPKXE2C0DBE0HE5YT","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Farbasyaa\u002Fmy-pi-setup\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7CNS93FZ4H60TYTNDVK0KH5","writing-beats","Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.","https:\u002F\u002Fgithub.com\u002Farbasyaa\u002Fmy-pi-setup\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-beats\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CNS65S73NJ7GE8Y6YD4JEF","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Farbasyaa\u002Fmy-pi-setup\u002Fblob\u002Fmain\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7CNS3XM180RKP39NMMXBET3","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Farbasyaa\u002Fmy-pi-setup\u002Fblob\u002Fmain\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[]]