[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AYADAYJMFP5S18EQRKN8MW":3,"skill-same:01M7AYADAYJMFP5S18EQRKN8MW":46},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7AYADAYJMFP5S18EQRKN8MW","starintel-repo-bootstrap",null,"github, repositories, adard, issues, bootstrap, provenance","lost-rob0t\u002Fskills","lost-rob0t","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F104283403?v=4","01M7AE2T5GZHE2CF6ANP6TKG0E","nsaspy","01M7AY4Z7QRGZRBX43TN2XT0GR",0,"BSD-3-Clause","https:\u002F\u002Fgithub.com\u002Flost-rob0t\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fstarintel-repo-bootstrap\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: starintel-repo-bootstrap\ndescription: github, repositories, adard, issues, bootstrap, provenance\ncompatibility: Requires GitHub CLI (`gh`), repository access, and an explicit ADARD source and target mapping.\n---\n\n# StarIntel repository bootstrap\n\n## Goal\n\nCreate one explicitly approved repository and seed its issue tracker with a\nsmall, traceable set of issues from the project's ADARD source. This skill\ndoes not implement the application or deploy it.\n\n## Inputs and output\n\nInput must include the target owner\u002Fname, purpose, visibility, authoritative\nADARD source repository, and issue or design scope. Output is a minimal\nrepository plus idempotently created issues that preserve source links,\napproval state, dependencies, and acceptance criteria.\n\n## Rules\n\n- Load `adadr` for research\u002Fdesign approval semantics and\n  `skill-portability` before retaining any source material.\n- Use `gh` for every GitHub operation.\n- Inspect authoritative repositories before creating a target. A missing name\n  is not evidence that a new repository is needed.\n- Never create duplicates, forks, transfers, licenses, application code, or\n  language-specific files during bootstrap.\n- Never close or edit ADARD source issues.\n- Never treat an open issue, green CI, or repository creation as approval.\n- Never infer that a new aggregate repository owns work mapped to an existing\n  implementation repository.\n\n## Workflow\n\n1. Read applicable repository instructions and inspect local Git status. Keep\n   unrelated changes untouched.\n2. Run `gh auth status`, list organization and account-visible repositories,\n   and inspect same-purpose candidates with `gh repo view`.\n3. Confirm the ADARD source repository and inspect the requested source issue\n   or design. Use `gh issue view` for issue metadata and read the linked\n   research\u002Fdesign implementation map.\n4. Require an explicit source-to-target mapping. If the ADARD material names a\n   different authoritative implementation repository, stop and ask rather\n   than reassigning it to the new target.\n5. Build a dry-run manifest of proposed target issues. Include source URL,\n   source state, title, scope, dependencies, and acceptance criteria. Ask for\n   confirmation before remote issue creation unless the operator supplied the\n   exact issue list and mapping.\n6. Immediately before creation, run:\n\n   ```bash\n   gh repo view OWNER\u002FREPOSITORY\n   ```\n\n   If it exists, leave it alone. If it is missing and creation is approved,\n   create it with `gh repo create`, `--private` when requested, the supplied\n   description, and `--add-readme`. The README states only purpose,\n   deployment ownership, and an established public hostname, if applicable.\n7. Before each issue creation, inspect all open and closed target issues for\n   its source marker. Skip an existing marker; do not overwrite a matching\n   title that lacks provenance.\n8. Create each approved issue with `gh issue create`. Preserve ADARD status,\n   source issue\u002Fdesign URLs, bounded scope, acceptance criteria, dependencies,\n   non-goals, and the statement that implementation approval is not inferred.\n9. If a source design is `PENDING` or `BLOCKED`, create a tracking issue only\n   when explicitly requested and preserve that state. Do not create\n   implementation-ready work from it.\n10. If repository documentation is requested, update the canonical registry\n    in the owning infrastructure repository. Do not change live service\n    inventory or deployment configuration as part of bootstrap.\n\n## Issue provenance\n\nUse a stable marker in every seeded issue, for example:\n\n```text\n\u003C!-- starintel-adard-source: SOURCE-ISSUE-OR-DESIGN-URL -->\n```\n\nDo not copy an entire research packet into an issue. Link the source and\nsummarize only the target-relevant scope. Do not split one source into several\nissues unless the source design explicitly splits it or the operator directs\nthe split. Use only labels already present in the target repository.\n\n## Verification\n\nVerify target visibility, description, default branch, intended bootstrap\nfiles, issue count, source markers, preserved ADARD states, and unresolved\nmappings with `gh repo view`, `gh api`, and `gh issue list`. Then run the\ntarget repository's required checks. For this skills repository, run:\n\n```bash\nbash scripts\u002Fvalidate-skills\nbash scripts\u002Fvalidate-support-scripts\ngit diff --check\n```\n\nReport created and pre-existing repositories, each created or skipped issue\nwith its source URL, validation results, and that no implementation or\ndeployment occurred.\n","# StarIntel repository bootstrap\n\n## Goal\n\nCreate one explicitly approved repository and seed its issue tracker with a\nsmall, traceable set of issues from the project's ADARD source. This skill\ndoes not implement the application or deploy it.\n\n## Inputs and output\n\nInput must include the target owner\u002Fname, purpose, visibility, authoritative\nADARD source repository, and issue or design scope. Output is a minimal\nrepository plus idempotently created issues that preserve source links,\napproval state, dependencies, and acceptance criteria.\n\n## Rules\n\n- Load `adadr` for research\u002Fdesign approval semantics and\n  `skill-portability` before retaining any source material.\n- Use `gh` for every GitHub operation.\n- Inspect authoritative repositories before creating a target. A missing name\n  is not evidence that a new repository is needed.\n- Never create duplicates, forks, transfers, licenses, application code, or\n  language-specific files during bootstrap.\n- Never close or edit ADARD source issues.\n- Never treat an open issue, green CI, or repository creation as approval.\n- Never infer that a new aggregate repository owns work mapped to an existing\n  implementation repository.\n\n## Workflow\n\n1. Read applicable repository instructions and inspect local Git status. Keep\n   unrelated changes untouched.\n2. Run `gh auth status`, list organization and account-visible repositories,\n   and inspect same-purpose candidates with `gh repo view`.\n3. Confirm the ADARD source repository and inspect the requested source issue\n   or design. Use `gh issue view` for issue metadata and read the linked\n   research\u002Fdesign implementation map.\n4. Require an explicit source-to-target mapping. If the ADARD material names a\n   different authoritative implementation repository, stop and ask rather\n   than reassigning it to the new target.\n5. Build a dry-run manifest of proposed target issues. Include source URL,\n   source state, title, scope, dependencies, and acceptance criteria. Ask for\n   confirmation before remote issue creation unless the operator supplied the\n   exact issue list and mapping.\n6. Immediately before creation, run:\n\n   ```bash\n   gh repo view OWNER\u002FREPOSITORY\n   ```\n\n   If it exists, leave it alone. If it is missing and creation is approved,\n   create it with `gh repo create`, `--private` when requested, the supplied\n   description, and `--add-readme`. The README states only purpose,\n   deployment ownership, and an established public hostname, if applicable.\n7. Before each issue creation, inspect all open and closed target issues for\n   its source marker. Skip an existing marker; do not overwrite a matching\n   title that lacks provenance.\n8. Create each approved issue with `gh issue create`. Preserve ADARD status,\n   source issue\u002Fdesign URLs, bounded scope, acceptance criteria, dependencies,\n   non-goals, and the statement that implementation approval is not inferred.\n9. If a source design is `PENDING` or `BLOCKED`, create a tracking issue only\n   when explicitly requested and preserve that state. Do not create\n   implementation-ready work from it.\n10. If repository documentation is requested, update the canonical registry\n    in the owning infrastructure repository. Do not change live service\n    inventory or deployment configuration as part of bootstrap.\n\n## Issue provenance\n\nUse a stable marker in every seeded issue, for example:\n\n```text\n\u003C!-- starintel-adard-source: SOURCE-ISSUE-OR-DESIGN-URL -->\n```\n\nDo not copy an entire research packet into an issue. Link the source and\nsummarize only the target-relevant scope. Do not split one source into several\nissues unless the source design explicitly splits it or the operator directs\nthe split. Use only labels already present in the target repository.\n\n## Verification\n\nVerify target visibility, description, default branch, intended bootstrap\nfiles, issue count, source markers, preserved ADARD states, and unresolved\nmappings with `gh repo view`, `gh api`, and `gh issue list`. Then run the\ntarget repository's required checks. For this skills repository, run:\n\n```bash\nbash scripts\u002Fvalidate-skills\nbash scripts\u002Fvalidate-support-scripts\ngit diff --check\n```\n\nReport created and pre-existing repositories, each created or skipped issue\nwith its source URL, validation results, and that no implementation or\ndeployment occurred.\n",{"name":5,"description":7,"compatibility":24},"Requires GitHub CLI (`gh`), repository access, and an explicit ADARD source and target mapping.","main","4b51593eee1b59ce94f1a7bb84b9a1393414906a","skills\u002Fstarintel-repo-bootstrap","https:\u002F\u002Fgithub.com\u002Flost-rob0t\u002Fskills","https:\u002F\u002Fgithub.com\u002Flost-rob0t","HackerMan\r\nLISP\u002Fnim + nixos\r\n\r\nMonero: \r\n8Bk9yV92PqAepeeCHvWVXsLwnpMWMmB99XoGgLaxWEZNfDXXcfzDWyH56XaGs6K5YFZckaPjQGsPXdRZDokgEFbKSUG9H","2026-11-14 09:27:40",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lost-rob0t\u002Fskills --skill starintel-repo-bootstrap",{"tool":38,"command":39},"bunx","bunx skills add lost-rob0t\u002Fskills --skill starintel-repo-bootstrap",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lost-rob0t\u002Fskills --skill starintel-repo-bootstrap","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flost-rob0t\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fstarintel-repo-bootstrap\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7AYCQH81M6KWJF8SXDK3C0C","unknown-frontmatter","validator, fixture","https:\u002F\u002Fgithub.com\u002Flost-rob0t\u002Fskills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Funknown-frontmatter\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7AYBFAATN244PFVY74JWCWM","zara-phone-pair","zara, phone, pairing, adb, wireless-debugging, curve, enrollment, android","https:\u002F\u002Fgithub.com\u002Flost-rob0t\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzara-phone-pair\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7AYB9NY8AX86EN0A1PSVBFK","zara-mcp","zara, mcp, stdio, http, tools, resources, prompts, debugging","https:\u002F\u002Fgithub.com\u002Flost-rob0t\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzara-mcp\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7AYB63ZZTN44G20M900X2WZ","youtube-context","youtube, transcripts, yt-dlp, whisper, video-context","https:\u002F\u002Fgithub.com\u002Flost-rob0t\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-context\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7AYB3JEZGMP6YQ91X7BYYED","worker-orchestration","workers, routing, delegation, fleet, budgets, concurrency","https:\u002F\u002Fgithub.com\u002Flost-rob0t\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworker-orchestration\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7AYAZZCC7TXT978GBHEPV47","task-steward-worker","steward, rage, leases, fencing, heartbeat, receipts","https:\u002F\u002Fgithub.com\u002Flost-rob0t\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftask-steward-worker\u002FSKILL.md",[],[]]