[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BXWRZN8WY5RPDC7R9VATDK":3,"skill-same:01M6BXWRZN8WY5RPDC7R9VATDK":81},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":6,"updatedAt":51,"install":52,"resources":64},"01M6BXWRZN8WY5RPDC7R9VATDK","setup-collection-repo",null,"One-time GitHub setup for a silexdata.* collection repository after the Bootstrap collection workflow has run - removes the template-only workflows, stores the release secrets without exposing them, enables GitHub Pages, lets the skeleton sync open its PRs, protects the default branch, and later locks in the required CI checks. Also used to rotate RELEASE_TOKEN or GALAXY_API_KEY.","SilexDataTeam\u002Fsilexdata.meraki","SilexDataTeam","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F109674383?v=4","01M6BXWQ81V4VVFVSFTXMCNTFD","Silex Data Solutions","01M6BXWQCAME2QRCEVJFSYMN8Y",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSilexDataTeam\u002Fsilexdata.meraki\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsetup-collection-repo\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"setup collection repo","setup","collection","repository","template","github pages","open","secrets","api","ci","github","release","run","bootstrap","sync","workflows","workflow","2026-11-10 10:12:30",false,"---\nname: setup-collection-repo\ndescription: >-\n  One-time GitHub setup for a silexdata.* collection repository after the\n  Bootstrap collection workflow has run - removes the template-only workflows,\n  stores the release secrets without exposing them, enables GitHub Pages, lets\n  the skeleton sync open its PRs, protects the default branch, and later locks in\n  the required CI checks. Also used to rotate RELEASE_TOKEN or GALAXY_API_KEY.\ndisable-model-invocation: true\nargument-hint: \"[OWNER\u002FREPO]\"\n---\n\n# Set up a collection repository\n\nA repository created from the collection_skeleton template gets its files but\nnone of its settings: no secrets, no GitHub Pages, no branch protection. This\nskill applies them, in order. Run each script with `bash` -\n`ansible-galaxy collection init` does not preserve the executable bit.\n\nScripts live in `${CLAUDE_SKILL_DIR}\u002Fscripts\u002F`.\n\n## Secrets: rules that are never relaxed\n\n- **Never ask the user to type or paste a token or API key into the\n  conversation**, whole or in part. If one is pasted anyway, stop, and tell the\n  user to revoke it: it is now in a transcript.\n- **Never put a secret value in a command** - not as an argument, not in\n  `--body`, not in a heredoc, not in a file.\n- **Never print or inspect one** - no `echo`, `printenv`, `env`, `set -x`,\n  `declare -p`, or reading a file that holds one.\n- **Only `set-release-secrets.sh` touches the values.** It reads them from the\n  environment or prompts for them with echo off, and passes them to GitHub\n  through stdin. If they are not already exported in the environment you run in,\n  do not try to obtain them: ask the user to run the script themselves in their\n  own terminal, then carry on.\n- Verify with `configure-repo.sh status`, which shows secret *names* only.\n\n## 0. Preconditions\n\nResolve OWNER\u002FREPO from `$ARGUMENTS`, or with\n`gh repo view --json nameWithOwner --jq .nameWithOwner`. Then confirm, stopping\nwith an explanation if any fails:\n\n- the working directory is the collection's repository root, and `galaxy.yml`\n  exists;\n- `skeleton\u002F` does **not** exist - otherwise bootstrap has not run yet; tell the\n  user to run the **Bootstrap collection** workflow from the Actions tab first;\n- `git remote get-url origin` is an SSH URL (`git@...`) - step 1 depends on it;\n- `gh api repos\u002FOWNER\u002FREPO --jq .permissions.admin` prints `true`.\n\n## 1. Remove the template-only workflows\n\nOnly if `.github\u002Fworkflows\u002Fbootstrap.yml`, `refresh-automation-hub-token.yml` or\n`selfcheck.yml` still exist. Do this **before step 4**: once the branch is\nprotected, a direct push is refused.\n\n```sh\ngit pull --ff-only\ngit rm --ignore-unmatch .github\u002Fworkflows\u002Fbootstrap.yml \\\n  .github\u002Fworkflows\u002Frefresh-automation-hub-token.yml .github\u002Fworkflows\u002Fselfcheck.yml\ngit commit -m \"chore: remove collection_skeleton template-only workflows\"\ngit push\n```\n\nShow the user the commit before pushing. This has to go over SSH: GitHub does\nnot let a workflow's `GITHUB_TOKEN` delete files under `.github\u002Fworkflows\u002F`, but\nan SSH push is not subject to that. This push is also what starts the\ncollection's first CI run - bootstrap's own commit did not, because pushes made\nwith `GITHUB_TOKEN` do not trigger workflows.\n\n## 2. Release secrets\n\n```sh\nbash \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fset-release-secrets.sh\" OWNER\u002FREPO\n```\n\nFollow the secrets rules above. The script checks the token works and has push\naccess before storing anything, then prints `RELEASE_TOKEN acts as: \u003Clogin>` -\nnote that login for step 4.\n\n- `RELEASE_TOKEN` - a personal access token whose owner has push access to the\n  repository. Fine-grained: Contents read and write on this repository. Classic:\n  `repo`. The release workflow uses it to push the release commit and tag past\n  branch protection.\n- `GALAXY_API_KEY` - a **galaxy.ansible.com** API token (Collections > API\n  token management there) with rights to the namespace. Not a Red Hat\n  Automation Hub token: Galaxy rejects those with `401`, and only at publish\n  time. The script checks the key against Galaxy, including the namespace,\n  before storing anything. Galaxy tokens do not expire; loading a new one in\n  the Galaxy UI invalidates the old one, so update this secret everywhere it\n  is used when that happens.\n\nThis step can be deferred: until both secrets exist, the Release workflow skips\nwith a notice rather than failing. Nothing is published below 1.0.0 in any case.\n\n## 3. GitHub Pages\n\n```sh\nbash \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fconfigure-repo.sh\" pages OWNER\u002FREPO\n```\n\n### Let the skeleton sync open its PRs\n\n```sh\nbash \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fconfigure-repo.sh\" actions-prs OWNER\u002FREPO\n```\n\nTurns on \"Allow GitHub Actions to create and approve pull requests\", so the\n**Sync from the skeleton** workflow can propose drift in the skeleton-managed\nfiles as a PR. An\norganization policy can forbid it; the script then says so and exits cleanly,\nbecause the workflow falls back to warning with a one-click link. Tell the user\nwhich happened. Either way, a sync PR opened by the workflow needs a maintainer\nto select **Approve workflows to run** on it before its checks report.\n\n## 4. Protect the default branch\n\n```sh\nbash \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fconfigure-repo.sh\" protect OWNER\u002FREPO RELEASE_LOGIN [APPROVALS]\n```\n\nCreates a ruleset requiring a pull request with 1 approving review (pass\nAPPROVALS to change it), and forbidding direct pushes, force-pushes and\ndeletion. Two bypasses, nothing broader:\n\n- `RELEASE_LOGIN`, the owner of `RELEASE_TOKEN`, may push directly, for the\n  release workflow's release commit and tag. GitHub checks the token's owner,\n  not the `github-actions[bot]` name on the commit, so this is a bypass for that\n  account as a whole: tell the user it can also push to the default branch\n  without a PR.\n- Repository admins may bypass, but only inside a PR - for example to merge\n  their own PR, which they cannot approve themselves. They cannot push directly.\n\nRe-running it updates the ruleset and keeps any required checks already locked\nin. Adding a bypass is a permission grant: confirm `RELEASE_LOGIN` with the user\nbefore running it. If step 2 was deferred, ask the user which account will own\n`RELEASE_TOKEN`, and re-run this step if that changes. Do **not** substitute a\nbroader bypass without the user deciding to. The built-in GitHub Actions\nidentity cannot be used instead: GitHub rejects it as a bypass actor.\n\n## 5. Lock in the required checks - after the first PR's CI has passed\n\n```sh\nbash \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fconfigure-repo.sh\" lock-checks OWNER\u002FREPO PR_NUMBER\n```\n\nRequires five fixed-name checks - lint, the nox and coverage result gates,\ndocs, and the changelog check - and refuses to act unless every one has passed\non that PR. It waits for that first PR because a required check that has never\nreported blocks every PR.\n\n## Verify\n\n```sh\nbash \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fconfigure-repo.sh\" status OWNER\u002FREPO\n```\n\n## Rotating a secret\n\nRun step 2 again. If the token's owner changes, re-run step 4 with the new login.\n","# Set up a collection repository\n\nA repository created from the collection_skeleton template gets its files but\nnone of its settings: no secrets, no GitHub Pages, no branch protection. This\nskill applies them, in order. Run each script with `bash` -\n`ansible-galaxy collection init` does not preserve the executable bit.\n\nScripts live in `${CLAUDE_SKILL_DIR}\u002Fscripts\u002F`.\n\n## Secrets: rules that are never relaxed\n\n- **Never ask the user to type or paste a token or API key into the\n  conversation**, whole or in part. If one is pasted anyway, stop, and tell the\n  user to revoke it: it is now in a transcript.\n- **Never put a secret value in a command** - not as an argument, not in\n  `--body`, not in a heredoc, not in a file.\n- **Never print or inspect one** - no `echo`, `printenv`, `env`, `set -x`,\n  `declare -p`, or reading a file that holds one.\n- **Only `set-release-secrets.sh` touches the values.** It reads them from the\n  environment or prompts for them with echo off, and passes them to GitHub\n  through stdin. If they are not already exported in the environment you run in,\n  do not try to obtain them: ask the user to run the script themselves in their\n  own terminal, then carry on.\n- Verify with `configure-repo.sh status`, which shows secret *names* only.\n\n## 0. Preconditions\n\nResolve OWNER\u002FREPO from `$ARGUMENTS`, or with\n`gh repo view --json nameWithOwner --jq .nameWithOwner`. Then confirm, stopping\nwith an explanation if any fails:\n\n- the working directory is the collection's repository root, and `galaxy.yml`\n  exists;\n- `skeleton\u002F` does **not** exist - otherwise bootstrap has not run yet; tell the\n  user to run the **Bootstrap collection** workflow from the Actions tab first;\n- `git remote get-url origin` is an SSH URL (`git@...`) - step 1 depends on it;\n- `gh api repos\u002FOWNER\u002FREPO --jq .permissions.admin` prints `true`.\n\n## 1. Remove the template-only workflows\n\nOnly if `.github\u002Fworkflows\u002Fbootstrap.yml`, `refresh-automation-hub-token.yml` or\n`selfcheck.yml` still exist. Do this **before step 4**: once the branch is\nprotected, a direct push is refused.\n\n```sh\ngit pull --ff-only\ngit rm --ignore-unmatch .github\u002Fworkflows\u002Fbootstrap.yml \\\n  .github\u002Fworkflows\u002Frefresh-automation-hub-token.yml .github\u002Fworkflows\u002Fselfcheck.yml\ngit commit -m \"chore: remove collection_skeleton template-only workflows\"\ngit push\n```\n\nShow the user the commit before pushing. This has to go over SSH: GitHub does\nnot let a workflow's `GITHUB_TOKEN` delete files under `.github\u002Fworkflows\u002F`, but\nan SSH push is not subject to that. This push is also what starts the\ncollection's first CI run - bootstrap's own commit did not, because pushes made\nwith `GITHUB_TOKEN` do not trigger workflows.\n\n## 2. Release secrets\n\n```sh\nbash \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fset-release-secrets.sh\" OWNER\u002FREPO\n```\n\nFollow the secrets rules above. The script checks the token works and has push\naccess before storing anything, then prints `RELEASE_TOKEN acts as: \u003Clogin>` -\nnote that login for step 4.\n\n- `RELEASE_TOKEN` - a personal access token whose owner has push access to the\n  repository. Fine-grained: Contents read and write on this repository. Classic:\n  `repo`. The release workflow uses it to push the release commit and tag past\n  branch protection.\n- `GALAXY_API_KEY` - a **galaxy.ansible.com** API token (Collections > API\n  token management there) with rights to the namespace. Not a Red Hat\n  Automation Hub token: Galaxy rejects those with `401`, and only at publish\n  time. The script checks the key against Galaxy, including the namespace,\n  before storing anything. Galaxy tokens do not expire; loading a new one in\n  the Galaxy UI invalidates the old one, so update this secret everywhere it\n  is used when that happens.\n\nThis step can be deferred: until both secrets exist, the Release workflow skips\nwith a notice rather than failing. Nothing is published below 1.0.0 in any case.\n\n## 3. GitHub Pages\n\n```sh\nbash \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fconfigure-repo.sh\" pages OWNER\u002FREPO\n```\n\n### Let the skeleton sync open its PRs\n\n```sh\nbash \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fconfigure-repo.sh\" actions-prs OWNER\u002FREPO\n```\n\nTurns on \"Allow GitHub Actions to create and approve pull requests\", so the\n**Sync from the skeleton** workflow can propose drift in the skeleton-managed\nfiles as a PR. An\norganization policy can forbid it; the script then says so and exits cleanly,\nbecause the workflow falls back to warning with a one-click link. Tell the user\nwhich happened. Either way, a sync PR opened by the workflow needs a maintainer\nto select **Approve workflows to run** on it before its checks report.\n\n## 4. Protect the default branch\n\n```sh\nbash \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fconfigure-repo.sh\" protect OWNER\u002FREPO RELEASE_LOGIN [APPROVALS]\n```\n\nCreates a ruleset requiring a pull request with 1 approving review (pass\nAPPROVALS to change it), and forbidding direct pushes, force-pushes and\ndeletion. Two bypasses, nothing broader:\n\n- `RELEASE_LOGIN`, the owner of `RELEASE_TOKEN`, may push directly, for the\n  release workflow's release commit and tag. GitHub checks the token's owner,\n  not the `github-actions[bot]` name on the commit, so this is a bypass for that\n  account as a whole: tell the user it can also push to the default branch\n  without a PR.\n- Repository admins may bypass, but only inside a PR - for example to merge\n  their own PR, which they cannot approve themselves. They cannot push directly.\n\nRe-running it updates the ruleset and keeps any required checks already locked\nin. Adding a bypass is a permission grant: confirm `RELEASE_LOGIN` with the user\nbefore running it. If step 2 was deferred, ask the user which account will own\n`RELEASE_TOKEN`, and re-run this step if that changes. Do **not** substitute a\nbroader bypass without the user deciding to. The built-in GitHub Actions\nidentity cannot be used instead: GitHub rejects it as a bypass actor.\n\n## 5. Lock in the required checks - after the first PR's CI has passed\n\n```sh\nbash \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fconfigure-repo.sh\" lock-checks OWNER\u002FREPO PR_NUMBER\n```\n\nRequires five fixed-name checks - lint, the nox and coverage result gates,\ndocs, and the changelog check - and refuses to act unless every one has passed\non that PR. It waits for that first PR because a required check that has never\nreported blocks every PR.\n\n## Verify\n\n```sh\nbash \"${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fconfigure-repo.sh\" status OWNER\u002FREPO\n```\n\n## Rotating a secret\n\nRun step 2 again. If the token's owner changes, re-run step 4 with the new login.\n",{"name":5,"description":7,"argument-hint":41,"disable-model-invocation":42},"[OWNER\u002FREPO]",true,"main","27138905aefd371a3229065be05724b3b449eea3",".claude\u002Fskills\u002Fsetup-collection-repo",0,"https:\u002F\u002Fgithub.com\u002FSilexDataTeam\u002Fsilexdata.meraki","https:\u002F\u002Fwww.silexdata.com\u002F","https:\u002F\u002Fgithub.com\u002FSilexDataTeam","https:\u002F\u002Fwww.silexdata.com","2026-10-03 02:48:35",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":42},[54,57,60],{"tool":55,"command":56},"npx","npx skills add SilexDataTeam\u002Fsilexdata.meraki --skill setup-collection-repo",{"tool":58,"command":59},"bunx","bunx skills add SilexDataTeam\u002Fsilexdata.meraki --skill setup-collection-repo",{"tool":61,"command":62},"pnpm","pnpm dlx skills add SilexDataTeam\u002Fsilexdata.meraki --skill setup-collection-repo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSilexDataTeam\u002Fsilexdata.meraki\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsetup-collection-repo\u002FSKILL.md",[65,71,75],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"scripts\u002Fconfigure-repo.sh","SCRIPT","脚本",10535,"https:\u002F\u002Fgithub.com\u002FSilexDataTeam\u002Fsilexdata.meraki\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsetup-collection-repo\u002Fscripts\u002Fconfigure-repo.sh",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"scripts\u002Fset-release-secrets.sh",4684,"https:\u002F\u002Fgithub.com\u002FSilexDataTeam\u002Fsilexdata.meraki\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsetup-collection-repo\u002Fscripts\u002Fset-release-secrets.sh",{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"SKILL.md.license","OTHER","其他",81,"https:\u002F\u002Fgithub.com\u002FSilexDataTeam\u002Fsilexdata.meraki\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsetup-collection-repo\u002FSKILL.md.license",[]]