[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B1PASPJRDWHAP2CYGWZ1ZX":3,"skill-same:01M7B1PASPJRDWHAP2CYGWZ1ZX":49},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7B1PASPJRDWHAP2CYGWZ1ZX","initial-publish",null,"First-time publish of a new @grafana\u002F* package in this monorepo, before OIDC trusted publishing can be wired up. Creates a publishable stub (package.json + README + LICENSE), walks the user through `pnpm login` with the grafanabot credentials from 1Password, runs `pnpm publish`, prompts the user to configure the trusted publisher on npmjs.com, then logs out. Use when adding a brand-new package that isn't yet on the npm registry. Do NOT use for routine releases of already-published packages — those go through changesets and the release workflow.","torkelo\u002Fscenes2","torkelo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10999?v=4","01M7B1G6RRGVK2TZGTJ2813VJ4","Torkel Ödegaard","01M7B1G6SAYVTDC3NWMBPX16TB",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Ftorkelo\u002Fscenes2\u002Fblob\u002Fmain\u002F.hatch\u002F_skills\u002Finitial-publish\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ntargets: [claude, codex]\nname: initial-publish\ndescription: First-time publish of a new @grafana\u002F* package in this monorepo, before OIDC trusted publishing can be wired up. Creates a publishable stub (package.json + README + LICENSE), walks the user through `pnpm login` with the grafanabot credentials from 1Password, runs `pnpm publish`, prompts the user to configure the trusted publisher on npmjs.com, then logs out. Use when adding a brand-new package that isn't yet on the npm registry. Do NOT use for routine releases of already-published packages — those go through changesets and the release workflow.\n---\n\n# Initial publish\n\nWalks a human through the first publish of a new `@grafana\u002F*` package,\nautomating the mechanical steps and pausing where the user must act.\n\nWhen invoked, work through the phases in order. Don't skip ahead.\n\n## Phase 0 — Preconditions\n\nConfirm all three with the user before doing anything else. If any are false,\nstop and tell them what to fix first.\n\n1. **The package is brand new on npm.** Verify:\n\n   ```bash\n   cd \u002Ftmp && npm view @grafana\u002F\u003Cpackage-name> 2>&1 | head -5\n   ```\n\n   A `code E404` response is the confirmation. If npm returns metadata, the\n   package already exists and this skill doesn't apply.\n\n2. **The user has access to the `grafanabot` 1Password entry.** Ask them\n   explicitly. Don't proceed if they don't.\n\n3. **The `release` environment exists** in the repo's GitHub settings\n   (Settings → Environments). If it doesn't, instruct the user to create it.\n   No protection rules are required for the bootstrap.\n\n## Phase 1 — Gather inputs\n\nAsk the user for:\n\n- The **package name** (without the `@grafana\u002F` prefix), e.g. `icons`,\n  `theme`, `motion`.\n- A **one-line description** for the package.\n\nValidate the name against `^[a-z][a-z0-9-]*$`. If not, ask again.\n\n## Phase 2 — Choose the publishing path\n\nDecide which sub-flow applies by checking the workspace:\n\n```bash\n[ -d packages\u002F\u003Cpackage-name> ] && echo \"exists\" || echo \"absent\"\n```\n\n- **`absent`** — Cold start. The user is bootstrapping before any real code\n  exists. Use **Path A (in-tree stub)** below.\n- **`exists`** — The real package has already been built on this or another\n  branch. Use **Path B (scratch-dir publish)** below.\n\nIf unsure, ask the user. The paths diverge only through Phase 4; Phase 5\nonward is identical.\n\n### Path A — In-tree stub (cold start)\n\nThe stub lives in the workspace, goes through a PR, and is merged to `main`\nbefore the publish.\n\n1. Switch to a fresh branch off `main`:\n\n   ```bash\n   git checkout main && git pull --ff-only\n   git checkout -b bootstrap-\u003Cpackage-name>\n   ```\n\n2. If the repo has no root `LICENSE`, copy one from a sibling package now:\n\n   ```bash\n   [ -f LICENSE ] || cp packages\u002F\u003Cany-existing-package>\u002FLICENSE LICENSE\n   ```\n\n   Grafana packages are all Apache-2.0.\n\n3. Invoke the generator non-interactively. The two `--args` values are the\n   package name and description in that order:\n\n   ```bash\n   pnpm turbo gen stub --args \"\u003Cpackage-name>\" --args \"\u003Cdescription>\"\n   ```\n\n   This writes `packages\u002F\u003Cpackage-name>\u002F{package.json,README.md,LICENSE}`. If\n   any of those files already exist, the generator refuses — that means you're\n   in Path B territory and should switch.\n\n4. Verify the workspace is happy:\n\n   ```bash\n   pnpm install\n   pnpm preflight\n   ```\n\n5. Stage and commit:\n\n   ```bash\n   git add LICENSE packages\u002F\u003Cpackage-name>\u002F pnpm-lock.yaml\n   git commit -m \"feat(\u003Cpackage-name>): publishable stub for @grafana\u002F\u003Cpackage-name>\"\n   ```\n\n   (Stage `LICENSE` only if you created it in step 2.)\n\n6. Tell the user the stub is ready, and pause:\n\n   ```\n   Stub is ready on branch `bootstrap-\u003Cpackage-name>`. Next steps for you:\n\n     1. Push:        git push -u origin bootstrap-\u003Cpackage-name>\n     2. Open a PR:   gh pr create\n     3. Get it reviewed and merged\n\n   Tell me once the PR is merged and I'll move on to authentication.\n   ```\n\n   Don't push, open PRs, or merge on the user's behalf.\n\n7. After the user confirms the merge, switch back to `main`:\n\n   ```bash\n   git checkout main && git pull --ff-only\n   ```\n\n### Path B — Scratch-dir publish (real package exists)\n\nThe user is on a branch where `packages\u002F\u003Cpackage-name>\u002F` already has real\ncode. We publish a stub straight to npm from a scratch directory — no git\nchanges, no PR, no rebasing the feature branch. The package name gets claimed\non npm, the trusted publisher gets configured, and the user goes right back to\ntheir feature work.\n\n1. Pick a scratch directory and write the stub files there directly. The\n   templates the in-tree generator uses live at\n   `turbo\u002Fgenerators\u002Ftemplates\u002Fstub\u002F` — substitute `{{ name }}` and\n   `{{ description }}` ourselves:\n\n   ```bash\n   SCRATCH=\u002Ftmp\u002Fgrafana-stub-\u003Cpackage-name>\n   rm -rf \"$SCRATCH\" && mkdir -p \"$SCRATCH\"\n   cp LICENSE \"$SCRATCH\u002FLICENSE\" 2>\u002Fdev\u002Fnull || \\\n     cp turbo\u002Fgenerators\u002Ftemplates\u002Fstub\u002FLICENSE \"$SCRATCH\u002FLICENSE\"\n   ```\n\n2. Write `$SCRATCH\u002Fpackage.json` with the standard stub content (use the same\n   shape as `turbo\u002Fgenerators\u002Ftemplates\u002Fstub\u002Fpackage.json.hbs`):\n\n   ```json\n   {\n     \"name\": \"@grafana\u002F\u003Cpackage-name>\",\n     \"version\": \"0.0.0\",\n     \"private\": false,\n     \"description\": \"\u003Cdescription>\",\n     \"license\": \"Apache-2.0\",\n     \"files\": [\"LICENSE\", \"README.md\"],\n     \"repository\": {\n       \"type\": \"git\",\n       \"url\": \"https:\u002F\u002Fgithub.com\u002Fgrafana\u002Fdesign.git\",\n       \"directory\": \"packages\u002F\u003Cpackage-name>\"\n     },\n     \"publishConfig\": {\n       \"access\": \"public\",\n       \"registry\": \"https:\u002F\u002Fregistry.npmjs.org\u002F\"\n     }\n   }\n   ```\n\n3. Write `$SCRATCH\u002FREADME.md`:\n\n   ```md\n   # @grafana\u002F\u003Cpackage-name>\n\n   \u003Cdescription>\n\n   > This is a placeholder release. The first usable version of the package is forthcoming.\n   ```\n\n4. Tell the user nothing in their workspace was touched:\n\n   ```\n   Scratch stub prepared at \u002Ftmp\u002Fgrafana-stub-\u003Cpackage-name>. Your current\n   branch and the real packages\u002F\u003Cpackage-name>\u002F are untouched.\n   ```\n\n## Phase 3 — Authenticate as grafanabot (user action + verify)\n\nPrompt the user:\n\n```\nTime to authenticate as grafanabot.\n\n  1. In 1Password, find the \"grafanabot\" npm entry.\n  2. Run:  pnpm login --registry=https:\u002F\u002Fregistry.npmjs.org\n  3. Enter the username, password, OTP, and email when prompted.\n\nTell me once you're logged in.\n```\n\nWhen they confirm, verify:\n\n```bash\npnpm whoami --registry=https:\u002F\u002Fregistry.npmjs.org\n```\n\nIf the output is not exactly `grafanabot`, stop and report. Don't continue\nwith the wrong account.\n\n## Phase 4 — Publish\n\nThe command depends on which path you took in Phase 2.\n\n- **Path A** (on `main` after the stub PR merged):\n\n  ```bash\n  pnpm --filter @grafana\u002F\u003Cpackage-name> publish --no-git-checks\n  ```\n\n- **Path B** (publishing from the scratch dir; the user's current branch is\n  unchanged):\n\n  ```bash\n  cd \u002Ftmp\u002Fgrafana-stub-\u003Cpackage-name>\n  npm publish --access public\n  ```\n\n  Use `npm publish` here, not `pnpm`. The scratch dir is intentionally outside\n  the workspace, so pnpm's workspace-aware tooling isn't relevant. `npm\npublish` reads the local `package.json` directly.\n\nEither way, verify the publish landed:\n\n```bash\ncd \u002Ftmp && npm view @grafana\u002F\u003Cpackage-name>\n```\n\nIf `view` returns 404, wait 60s and retry. If it still 404s, troubleshoot\nbased on the publish command's output.\n\n## Phase 5 — Configure trusted publisher (user action)\n\nPrompt the user:\n\n```\nOpen https:\u002F\u002Fwww.npmjs.com\u002F in your browser, signed in as grafanabot, then\nnavigate to the new package's settings page. The Trusted Publishers section\nneeds a new entry with these values:\n\n  Publisher              GitHub Actions\n  Organization or user   grafana\n  Repository             design\n  Workflow filename      release.yml\n  Environment name       release\n\nSave it. Tell me when it's done.\n```\n\nWait for confirmation. The exact UI path on npmjs.com can shift; the user\nwill navigate themselves rather than have you assume a URL.\n\n## Phase 6 — Log out\n\nLog out and confirm:\n\n```bash\npnpm logout --registry=https:\u002F\u002Fregistry.npmjs.org\npnpm whoami --registry=https:\u002F\u002Fregistry.npmjs.org   # should error with ENEEDAUTH\n```\n\nIf `whoami` succeeds, the logout didn't take effect — investigate.\n\nIf you used Path B, also clean up the scratch dir:\n\n```bash\nrm -rf \u002Ftmp\u002Fgrafana-stub-\u003Cpackage-name>\n```\n\n## Phase 7 — Summary\n\nReport to the user:\n\n```\nDone.\n\n  ✓ @grafana\u002F\u003Cpackage-name>@0.0.0 is published as a stub\n  ✓ Trusted publisher is configured on npmjs.com\n  ✓ grafanabot is logged out locally\n\nThe next PR that lands real code with a changeset will publish via OIDC\nthrough release.yml. No more laptop publishes.\n\nOptional cleanup: mark the 0.0.0 stub deprecated so no one installs the\nempty placeholder. You'll need to log back in as grafanabot:\n\n  pnpm login --registry=https:\u002F\u002Fregistry.npmjs.org\n  npm deprecate @grafana\u002F\u003Cpackage-name>@0.0.0 \"Placeholder release. Install 0.1.0 or later.\"\n  pnpm logout --registry=https:\u002F\u002Fregistry.npmjs.org\n```\n\n## Rules of the road\n\n- Never store, log, or echo the grafanabot credentials. They go directly from\n  1Password into the npm login prompt and nowhere else.\n- Never push, open PRs, or merge on the user's behalf. PR review is a human\n  step.\n- If anything goes wrong — wrong account, publish 403, trusted publisher\n  rejected — stop and tell the user what happened rather than retrying.\n- If the user invokes this skill in the wrong state (already-published\n  package, no `release` environment, etc.), stop in Phase 0 and explain.\n- When in doubt about Path A vs Path B, ask the user. The cost of asking is\n  near zero; the cost of clobbering their real package files is high.\n","# Initial publish\n\nWalks a human through the first publish of a new `@grafana\u002F*` package,\nautomating the mechanical steps and pausing where the user must act.\n\nWhen invoked, work through the phases in order. Don't skip ahead.\n\n## Phase 0 — Preconditions\n\nConfirm all three with the user before doing anything else. If any are false,\nstop and tell them what to fix first.\n\n1. **The package is brand new on npm.** Verify:\n\n   ```bash\n   cd \u002Ftmp && npm view @grafana\u002F\u003Cpackage-name> 2>&1 | head -5\n   ```\n\n   A `code E404` response is the confirmation. If npm returns metadata, the\n   package already exists and this skill doesn't apply.\n\n2. **The user has access to the `grafanabot` 1Password entry.** Ask them\n   explicitly. Don't proceed if they don't.\n\n3. **The `release` environment exists** in the repo's GitHub settings\n   (Settings → Environments). If it doesn't, instruct the user to create it.\n   No protection rules are required for the bootstrap.\n\n## Phase 1 — Gather inputs\n\nAsk the user for:\n\n- The **package name** (without the `@grafana\u002F` prefix), e.g. `icons`,\n  `theme`, `motion`.\n- A **one-line description** for the package.\n\nValidate the name against `^[a-z][a-z0-9-]*$`. If not, ask again.\n\n## Phase 2 — Choose the publishing path\n\nDecide which sub-flow applies by checking the workspace:\n\n```bash\n[ -d packages\u002F\u003Cpackage-name> ] && echo \"exists\" || echo \"absent\"\n```\n\n- **`absent`** — Cold start. The user is bootstrapping before any real code\n  exists. Use **Path A (in-tree stub)** below.\n- **`exists`** — The real package has already been built on this or another\n  branch. Use **Path B (scratch-dir publish)** below.\n\nIf unsure, ask the user. The paths diverge only through Phase 4; Phase 5\nonward is identical.\n\n### Path A — In-tree stub (cold start)\n\nThe stub lives in the workspace, goes through a PR, and is merged to `main`\nbefore the publish.\n\n1. Switch to a fresh branch off `main`:\n\n   ```bash\n   git checkout main && git pull --ff-only\n   git checkout -b bootstrap-\u003Cpackage-name>\n   ```\n\n2. If the repo has no root `LICENSE`, copy one from a sibling package now:\n\n   ```bash\n   [ -f LICENSE ] || cp packages\u002F\u003Cany-existing-package>\u002FLICENSE LICENSE\n   ```\n\n   Grafana packages are all Apache-2.0.\n\n3. Invoke the generator non-interactively. The two `--args` values are the\n   package name and description in that order:\n\n   ```bash\n   pnpm turbo gen stub --args \"\u003Cpackage-name>\" --args \"\u003Cdescription>\"\n   ```\n\n   This writes `packages\u002F\u003Cpackage-name>\u002F{package.json,README.md,LICENSE}`. If\n   any of those files already exist, the generator refuses — that means you're\n   in Path B territory and should switch.\n\n4. Verify the workspace is happy:\n\n   ```bash\n   pnpm install\n   pnpm preflight\n   ```\n\n5. Stage and commit:\n\n   ```bash\n   git add LICENSE packages\u002F\u003Cpackage-name>\u002F pnpm-lock.yaml\n   git commit -m \"feat(\u003Cpackage-name>): publishable stub for @grafana\u002F\u003Cpackage-name>\"\n   ```\n\n   (Stage `LICENSE` only if you created it in step 2.)\n\n6. Tell the user the stub is ready, and pause:\n\n   ```\n   Stub is ready on branch `bootstrap-\u003Cpackage-name>`. Next steps for you:\n\n     1. Push:        git push -u origin bootstrap-\u003Cpackage-name>\n     2. Open a PR:   gh pr create\n     3. Get it reviewed and merged\n\n   Tell me once the PR is merged and I'll move on to authentication.\n   ```\n\n   Don't push, open PRs, or merge on the user's behalf.\n\n7. After the user confirms the merge, switch back to `main`:\n\n   ```bash\n   git checkout main && git pull --ff-only\n   ```\n\n### Path B — Scratch-dir publish (real package exists)\n\nThe user is on a branch where `packages\u002F\u003Cpackage-name>\u002F` already has real\ncode. We publish a stub straight to npm from a scratch directory — no git\nchanges, no PR, no rebasing the feature branch. The package name gets claimed\non npm, the trusted publisher gets configured, and the user goes right back to\ntheir feature work.\n\n1. Pick a scratch directory and write the stub files there directly. The\n   templates the in-tree generator uses live at\n   `turbo\u002Fgenerators\u002Ftemplates\u002Fstub\u002F` — substitute `{{ name }}` and\n   `{{ description }}` ourselves:\n\n   ```bash\n   SCRATCH=\u002Ftmp\u002Fgrafana-stub-\u003Cpackage-name>\n   rm -rf \"$SCRATCH\" && mkdir -p \"$SCRATCH\"\n   cp LICENSE \"$SCRATCH\u002FLICENSE\" 2>\u002Fdev\u002Fnull || \\\n     cp turbo\u002Fgenerators\u002Ftemplates\u002Fstub\u002FLICENSE \"$SCRATCH\u002FLICENSE\"\n   ```\n\n2. Write `$SCRATCH\u002Fpackage.json` with the standard stub content (use the same\n   shape as `turbo\u002Fgenerators\u002Ftemplates\u002Fstub\u002Fpackage.json.hbs`):\n\n   ```json\n   {\n     \"name\": \"@grafana\u002F\u003Cpackage-name>\",\n     \"version\": \"0.0.0\",\n     \"private\": false,\n     \"description\": \"\u003Cdescription>\",\n     \"license\": \"Apache-2.0\",\n     \"files\": [\"LICENSE\", \"README.md\"],\n     \"repository\": {\n       \"type\": \"git\",\n       \"url\": \"https:\u002F\u002Fgithub.com\u002Fgrafana\u002Fdesign.git\",\n       \"directory\": \"packages\u002F\u003Cpackage-name>\"\n     },\n     \"publishConfig\": {\n       \"access\": \"public\",\n       \"registry\": \"https:\u002F\u002Fregistry.npmjs.org\u002F\"\n     }\n   }\n   ```\n\n3. Write `$SCRATCH\u002FREADME.md`:\n\n   ```md\n   # @grafana\u002F\u003Cpackage-name>\n\n   \u003Cdescription>\n\n   > This is a placeholder release. The first usable version of the package is forthcoming.\n   ```\n\n4. Tell the user nothing in their workspace was touched:\n\n   ```\n   Scratch stub prepared at \u002Ftmp\u002Fgrafana-stub-\u003Cpackage-name>. Your current\n   branch and the real packages\u002F\u003Cpackage-name>\u002F are untouched.\n   ```\n\n## Phase 3 — Authenticate as grafanabot (user action + verify)\n\nPrompt the user:\n\n```\nTime to authenticate as grafanabot.\n\n  1. In 1Password, find the \"grafanabot\" npm entry.\n  2. Run:  pnpm login --registry=https:\u002F\u002Fregistry.npmjs.org\n  3. Enter the username, password, OTP, and email when prompted.\n\nTell me once you're logged in.\n```\n\nWhen they confirm, verify:\n\n```bash\npnpm whoami --registry=https:\u002F\u002Fregistry.npmjs.org\n```\n\nIf the output is not exactly `grafanabot`, stop and report. Don't continue\nwith the wrong account.\n\n## Phase 4 — Publish\n\nThe command depends on which path you took in Phase 2.\n\n- **Path A** (on `main` after the stub PR merged):\n\n  ```bash\n  pnpm --filter @grafana\u002F\u003Cpackage-name> publish --no-git-checks\n  ```\n\n- **Path B** (publishing from the scratch dir; the user's current branch is\n  unchanged):\n\n  ```bash\n  cd \u002Ftmp\u002Fgrafana-stub-\u003Cpackage-name>\n  npm publish --access public\n  ```\n\n  Use `npm publish` here, not `pnpm`. The scratch dir is intentionally outside\n  the workspace, so pnpm's workspace-aware tooling isn't relevant. `npm\npublish` reads the local `package.json` directly.\n\nEither way, verify the publish landed:\n\n```bash\ncd \u002Ftmp && npm view @grafana\u002F\u003Cpackage-name>\n```\n\nIf `view` returns 404, wait 60s and retry. If it still 404s, troubleshoot\nbased on the publish command's output.\n\n## Phase 5 — Configure trusted publisher (user action)\n\nPrompt the user:\n\n```\nOpen https:\u002F\u002Fwww.npmjs.com\u002F in your browser, signed in as grafanabot, then\nnavigate to the new package's settings page. The Trusted Publishers section\nneeds a new entry with these values:\n\n  Publisher              GitHub Actions\n  Organization or user   grafana\n  Repository             design\n  Workflow filename      release.yml\n  Environment name       release\n\nSave it. Tell me when it's done.\n```\n\nWait for confirmation. The exact UI path on npmjs.com can shift; the user\nwill navigate themselves rather than have you assume a URL.\n\n## Phase 6 — Log out\n\nLog out and confirm:\n\n```bash\npnpm logout --registry=https:\u002F\u002Fregistry.npmjs.org\npnpm whoami --registry=https:\u002F\u002Fregistry.npmjs.org   # should error with ENEEDAUTH\n```\n\nIf `whoami` succeeds, the logout didn't take effect — investigate.\n\nIf you used Path B, also clean up the scratch dir:\n\n```bash\nrm -rf \u002Ftmp\u002Fgrafana-stub-\u003Cpackage-name>\n```\n\n## Phase 7 — Summary\n\nReport to the user:\n\n```\nDone.\n\n  ✓ @grafana\u002F\u003Cpackage-name>@0.0.0 is published as a stub\n  ✓ Trusted publisher is configured on npmjs.com\n  ✓ grafanabot is logged out locally\n\nThe next PR that lands real code with a changeset will publish via OIDC\nthrough release.yml. No more laptop publishes.\n\nOptional cleanup: mark the 0.0.0 stub deprecated so no one installs the\nempty placeholder. You'll need to log back in as grafanabot:\n\n  pnpm login --registry=https:\u002F\u002Fregistry.npmjs.org\n  npm deprecate @grafana\u002F\u003Cpackage-name>@0.0.0 \"Placeholder release. Install 0.1.0 or later.\"\n  pnpm logout --registry=https:\u002F\u002Fregistry.npmjs.org\n```\n\n## Rules of the road\n\n- Never store, log, or echo the grafanabot credentials. They go directly from\n  1Password into the npm login prompt and nowhere else.\n- Never push, open PRs, or merge on the user's behalf. PR review is a human\n  step.\n- If anything goes wrong — wrong account, publish 403, trusted publisher\n  rejected — stop and tell the user what happened rather than retrying.\n- If the user invokes this skill in the wrong state (already-published\n  package, no `release` environment, etc.), stop in Phase 0 and explain.\n- When in doubt about Path A vs Path B, ask the user. The cost of asking is\n  near zero; the cost of clobbering their real package files is high.\n",{"name":5,"targets":24,"description":7},[25,26],"claude","codex","main","9b85ba995139627c15a6ef1cec1daec64659cf75",".hatch\u002F_skills\u002Finitial-publish","https:\u002F\u002Fgithub.com\u002Ftorkelo\u002Fscenes2","https:\u002F\u002Fgithub.com\u002Ftorkelo","https:\u002F\u002Fgrafana.com","Grafana Labs Co-Founder, Grafana Creator & product manager & lead architect.  ","2026-11-14 19:30:54",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add torkelo\u002Fscenes2 --skill initial-publish",{"tool":41,"command":42},"bunx","bunx skills add torkelo\u002Fscenes2 --skill initial-publish",{"tool":44,"command":45},"pnpm","pnpm dlx skills add torkelo\u002Fscenes2 --skill initial-publish","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftorkelo\u002Fscenes2\u002Fblob\u002Fmain\u002F.hatch\u002F_skills\u002Finitial-publish\u002FSKILL.md",true,[],[50,57,64,69,74,81],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7B1QT196EFM12F7737ZFBJ3","validate-plugin","validate a Grafana plugin using the official Grafana plugin validator","https:\u002F\u002Fgithub.com\u002Ftorkelo\u002Fscenes2\u002Fblob\u002Fmain\u002Fapps\u002Fdemo-app\u002F.codex\u002Fskills\u002Fvalidate-plugin\u002FSKILL.md",[],[],{"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},"01M7B1QQGHG8JJ9MK4BY2V8879","build-plugin","build a Grafana plugin using the standard build process (frontend and backend if applicable)","https:\u002F\u002Fgithub.com\u002Ftorkelo\u002Fscenes2\u002Fblob\u002Fmain\u002Fapps\u002Fdemo-app\u002F.codex\u002Fskills\u002Fbuild-plugin\u002FSKILL.md",[],[],{"skillNo":65,"name":52,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7B1QPP9RN7E1KNMRK9D8V6M","https:\u002F\u002Fgithub.com\u002Ftorkelo\u002Fscenes2\u002Fblob\u002Fmain\u002Fapps\u002Fdemo-app\u002F.claude\u002Fskills\u002Fvalidate-plugin\u002FSKILL.md",[],[],{"skillNo":70,"name":59,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7B1QN3V9SQ7H6WXNZDMQ57Q","https:\u002F\u002Fgithub.com\u002Ftorkelo\u002Fscenes2\u002Fblob\u002Fmain\u002Fapps\u002Fdemo-app\u002F.claude\u002Fskills\u002Fbuild-plugin\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7B1QJEW06858M7GC4EM46B5","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.","https:\u002F\u002Fgithub.com\u002Ftorkelo\u002Fscenes2\u002Fblob\u002Fmain\u002F.hatch\u002F_skills\u002Fstop-slop\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7B1QGEPPZQQNRJRXTQVZAKC","snag-fixer","Lightweight agent for quick fixes, tweaks, and small improvements. Optimized for single-task focused work without bloating context. Used by snag workflow for sequential fix processing.","https:\u002F\u002Fgithub.com\u002Ftorkelo\u002Fscenes2\u002Fblob\u002Fmain\u002F.hatch\u002F_skills\u002Fsnag-fixer\u002FSKILL.md",[],[]]