[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EFPR2VTC3X4GNBS9DNETRS":3,"skill-same:01M7EFPR2VTC3X4GNBS9DNETRS":47},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":46},"01M7EFPR2VTC3X4GNBS9DNETRS","source-init",null,"Create a team source for akg in an empty folder or repo — a dedicated repo, no code, that projects extend. Asks the team conventions and the team's stacks, then builds a plugin marketplace from the developer's installed plugins, official Anthropic plugins fitting those stacks, and plugins copied from existing projects. Use when the user runs \u002Fakg:source-init or asks to create a team config for akg.","anthonykgross\u002Fakg","anthonykgross","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5046196?v=4","01M7EFNWY7SQZZSTEJH8WD1G9J","Anthony K GROSS","01M7EFNWYYN410HM5WYPTQRGRG",0,"MIT","https:\u002F\u002Fgithub.com\u002Fanthonykgross\u002Fakg\u002Fblob\u002Fmain\u002Fskills\u002Fsource-init\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: source-init\ndescription: Create a team source for akg in an empty folder or repo — a dedicated repo, no code, that projects extend. Asks the team conventions and the team's stacks, then builds a plugin marketplace from the developer's installed plugins, official Anthropic plugins fitting those stacks, and plugins copied from existing projects. Use when the user runs \u002Fakg:source-init or asks to create a team config for akg.\ndisable-model-invocation: true\nallowed-tools: Read(\u002F${CLAUDE_PLUGIN_ROOT}\u002F**), Bash(git rev-parse *), Bash(git config user.name), Bash(git remote *), Bash(claude plugin list *), Bash(claude plugin marketplace list *), Bash(claude plugin validate *)\n---\n\n# \u002Fakg:source-init\n\nCreate the team source in the current folder: a dedicated repo, with no code, that projects `extends`. Its answers become the defaults of every project extending it. Rules for layers, marketplaces and plugin relevance are in [rules.md](${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Frules.md) — read it first.\n\n## Ground rules\n\n- **Gather everything in the first turn** (step 1): `allowed-tools` pre-approves only during the turn that started the skill; a later turn would prompt for each read and command.\n- **Stay within the pre-approved tools**: read files with Read and find them with Glob\u002FGrep, never `cat`\u002F`ls`\u002F`find` in Bash; run each `allowed-tools` command on its own, never chained (`;`, `&&`, pipes) or prefixed with `cd`.\nSame as `\u002Fakg:setup`: short messages in the user's language (generated files stay in English); asked as an interview (rules.md: Asking): plain text, numbered answers with a guess first, free values (paths, URLs, keywords) asked directly, never `AskUserQuestion`; **never write a file without showing it and getting approval**; nothing is imposed. A dismissed or empty answer never ends the flow: take the conservative choice (recommended option, no plugin), say it in one line, and continue.\n\n## 1. Gather and check (first turn)\n\nBefore the first question, in this turn: read rules.md and `${CLAUDE_PLUGIN_ROOT}\u002Fdefaults\u002Fquestions.md`, list the folder, run `git rev-parse --is-inside-work-tree`, `git config user.name`, `claude plugin list --available --json` and `claude plugin marketplace list --json` (used in steps 2 and 4). Then:\n\n- The folder has code (a manifest: `package.json`, `pyproject.toml`, `go.mod`, `composer.json`, `pom.xml`, `Cargo.toml`…, or a `src\u002F`) → say in one line that a team source is a dedicated repo without code, and ask: 1. Stop ← guess (then suggest an empty folder, e.g. `..\u002F\u003Corg>-claude-team`) · 2. Continue here.\n- `.claude\u002Fakg\u002Fconfig.yaml` or `.claude-plugin\u002Fmarketplace.json` already exists → this is already a source: its values are the guesses, source \"current\", and its plugins stay; say so in one line.\n\n## 2. Team stacks\n\nAsk, as a `multiple` question: \"Which stacks does the team work with?\" — 1. Front-end JS\u002FTS · 2. Node back-end · 3. PHP · 4. Python · 5. Go · 6. Java\u002FKotlin · 7. Mobile · 8. Infra (Terraform, Kubernetes); free text for the rest. Guess from an existing marketplace's `relevance`, otherwise from the developer's installed plugins (`claude plugin list --json`: `typescript-lsp` → 1), with the reason; nothing to go on → 1, 2, saying it is only a starting point. Not stored: it only drives the plugin choice and their `relevance` (step 4).\n\n## 3. Team conventions\n\nAsk every active question of the akg catalog (rules.md: Active questions, layer akg only, plus `questions.md` if it exists here), as `\u002Fakg:setup` step 5 does, with these differences:\n- Say once, before the first question, that these answers become the defaults of every project extending this source.\n- Phrase each question for the team (\"Where does the team track tickets?\").\n- No scan: the guess is the recommended option (or the current value of an existing `config.yaml`), so questions come one per message, except where the stacks make the guess obvious (Infra checked → container questions). \"I don't know\" stores the recommended value with a comment.\n- **Skip `per-project`** questions and follow-ups (rules.md), and questions whose condition depends on the project's files (\"Ask only if a container setup is detected\"); list them in one line (\"Left to each project: command environment, local environment, architecture, tracker project, migrations\").\n- `→` checks (CLI on the PATH, MCP configured) are skipped: they belong to each developer's setup. `→` CLAUDE.md and settings lines are not generated here: projects derive them from the answers.\n\nThen ask, as a `multiple` question, \"Which optional questions should projects answer?\": the off-by-default catalog prefixes (`deploy`, `git`, `tests`, `db`, `docs`), each with a one-line description; guess: none. Checked ones are added to `questions:` (with the default prefixes) and asked right away like the others.\n\n## 4. Candidate plugins (no questions)\n\nUse the catalog gathered in step 1: `claude plugin list --available --json` (`installed`, and `available`: `pluginId`, `name`, `description`, `marketplaceName`, `source`) and `claude plugin marketplace list --json`. A marketplace entry here reuses the plugin's `source` object **as is** (`url`, `git-subdir`, `github`…).\n\n- **Installed**: plugins the developer has installed (`installed`), except akg itself.\n  - `source` is an object → reuse it.\n  - `source` is a relative path (`.\u002Fplugins\u002Fx`) in a marketplace from a git or GitHub repo → `{ \"source\": \"git-subdir\", \"url\": \"\u003Cmarketplace repo URL>\", \"path\": \"\u003Cpath without .\u002F>\" }`.\n  - marketplace from a local directory → not shareable: excluded, one line.\n- **Official**: `anthropic-plugin-directory` entries whose `source.url` is under `github.com\u002Fanthropics\u002F`. Pick **at most 6** fitting the stacks and the answers, each with a one-line reason: language servers for the stacks (`typescript-lsp`, `pyright-lsp`, `gopls-lsp`, `php-lsp`, `jdtls-lsp`, `kotlin-lsp-anthropics`…), `frontend-design` for front-end, `terraform` for infra, the tracker's plugin (`linear`, `asana`) or code host's (`github`, `gitlab`), review and commit helpers (`code-review`, `pr-review-toolkit`, `commit-commands`), `security-guidance`. Never a domain plugin (legal, finance, bio…) nothing points to. Skip those already in Installed.\n- **Relevance** for each candidate, with the fixed signals of rules.md, from what the plugin is for: a language server or stack plugin → `manifestDeps` or `filesRead` for that stack (`typescript-lsp` → `filesRead: [\"**\u002F*.ts\", \"**\u002F*.tsx\"]`; a React plugin → `manifestDeps` on `\"react\"`; `terraform` → `filesRead: [\"**\u002F*.tf\"]`). General-purpose plugins (review, commits, tracker) → no `relevance` (proposed on every project).\n\n## 5. Pick the plugins\n\nPropose them as one numbered list (rules.md: Asking, Approvals), under two headings — **Installed**, **Official** — numbering running across both: name, reason, relevance (\"TypeScript projects\" \u002F \"every project\"). Guess: all. Replies like \"ok\", \"all but 4\", \"none\". Empty group → no heading.\n\nThen ask: \"Add more plugins?\" — 1. No ← guess · 2. From an existing project (give its path) · 3. Search the community catalog (give keywords) · 4. From a repo (give `github:owner\u002Frepo` or git URLs). The developer can give the value right away (\"2 ..\u002Fshop\"). Repeat it after each addition until \"no\".\n- **From an existing project**: ask its path if not given. List its skills (`.claude\u002Fskills\u002F\u003Cname>\u002F`), agents (`.claude\u002Fagents\u002F`), commands (`.claude\u002Fcommands\u002F`) and hooks whose script lives in that repo, and offer them as a numbered list, guess: all. Each one becomes a plugin `plugins\u002F\u003Cname>\u002F` here, **copied**; the project is never modified. Relevance from that project's stack, when the item is stack-specific.\n- **Search the community catalog**: ask keywords if not given, match them against `name` and `description` of the other `anthropic-plugin-directory` entries, offer the best matches as a numbered list, guess: none (unreviewed). Say in one line that community plugins are not reviewed by Anthropic.\n- **From a repo**: ask `github:owner\u002Frepo` or git URLs if not given, one per line. Read each repo's `.claude-plugin\u002Fplugin.json` when reachable for its name and description; otherwise use the repo name.\n\nPlugin names must not start with `claude-`: rename a copied one (`claude-review` → `review`) and say it.\n\n## 6. Generate\n\nPrepare, without writing yet:\n\n1. **`.claude\u002Fakg\u002Fconfig.yaml`**: `questions` (only if it differs from the default list) and every answer at its key (format in rules.md). No `extends`, no `synced`.\n2. **`.claude-plugin\u002Fmarketplace.json`**: `name` = `\u003Cfolder name>` (no `claude-` prefix), `owner.name` from `git config user.name`, `plugins` = the chosen ones, each with `name`, `source` (`.\u002Fplugins\u002F\u003Cname>` for copied content, the reused object otherwise), `description`, and `relevance` (`topic` + `signals`, same shape as rules.md) when inferred. Existing file → merge: keep its entries, add the new ones, show conflicts on the same name.\n3. **`plugins\u002F\u003Cname>\u002F`** for each copied item: `.claude-plugin\u002Fplugin.json` (`name`, `description`) and the content in plugin layout — `skills\u002F\u003Cskill>\u002F`, `agents\u002F\u003Cagent>.md`, `commands\u002F\u003Ccommand>.md`, `hooks\u002Fhooks.json`. For hooks, copy the script too and rewrite its path from `$CLAUDE_PROJECT_DIR\u002F…` to `${CLAUDE_PLUGIN_ROOT}\u002F…`.\n4. **`.claude\u002Fakg\u002Fteam.md`** (only if absent): instructions developers read with `\u002Fakg:team`, shown at the end of `\u002Fakg:setup` and diffed by `\u002Fakg:pull`. A short skeleton for the maintainer to fill, with the stacks and the tracker answer as hints:\n   ```markdown\n   # \u003CTeam> — Claude Code\n\n   ## Getting started\n   \u003C!-- What a new developer does first. -->\n\n   ## Tools to install\n   \u003C!-- CLIs, MCP servers (with how to get a token), plugins or skills installed by hand. One line each: what, why, the command. -->\n\n   ## Rules\n   \u003C!-- Team rules that are not in the questions. -->\n   ```\n5. **`README.md`** (only if absent), short: what this repo is, how a project uses it (`\u002Fakg:setup`, give this repo's URL as the team config), how to add a plugin (an entry in `marketplace.json`), developer instructions (`.claude\u002Fakg\u002Fteam.md`) or a team question (`.claude\u002Fakg\u002Fquestions.md`, format in the akg catalog).\n6. **`git init`** if `git rev-parse` says this is not a repo: listed in the review as an action.\n\n## 7. Review and write\n\nSame as `\u002Fakg:setup` step 8: each file's content or diff, copied content shown as a list (`\u003Cproject>\u002F.claude\u002Fskills\u002Freact-forms\u002F → plugins\u002Freact-forms\u002Fskills\u002Freact-forms\u002F`), then one numbered list of the files, guess: write all.\n\nRun `claude plugin validate .` and report errors only.\n\nThen, in at most 3 lines:\n- what was written;\n- next step: commit and push (create the remote first if there is none), then each project runs `\u002Fakg:setup` and gives this repo's URL as the team config;\n- plugins with an external source are installed once per developer: `\u002Fakg:setup` gives the command.\n","# \u002Fakg:source-init\n\nCreate the team source in the current folder: a dedicated repo, with no code, that projects `extends`. Its answers become the defaults of every project extending it. Rules for layers, marketplaces and plugin relevance are in [rules.md](${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Frules.md) — read it first.\n\n## Ground rules\n\n- **Gather everything in the first turn** (step 1): `allowed-tools` pre-approves only during the turn that started the skill; a later turn would prompt for each read and command.\n- **Stay within the pre-approved tools**: read files with Read and find them with Glob\u002FGrep, never `cat`\u002F`ls`\u002F`find` in Bash; run each `allowed-tools` command on its own, never chained (`;`, `&&`, pipes) or prefixed with `cd`.\nSame as `\u002Fakg:setup`: short messages in the user's language (generated files stay in English); asked as an interview (rules.md: Asking): plain text, numbered answers with a guess first, free values (paths, URLs, keywords) asked directly, never `AskUserQuestion`; **never write a file without showing it and getting approval**; nothing is imposed. A dismissed or empty answer never ends the flow: take the conservative choice (recommended option, no plugin), say it in one line, and continue.\n\n## 1. Gather and check (first turn)\n\nBefore the first question, in this turn: read rules.md and `${CLAUDE_PLUGIN_ROOT}\u002Fdefaults\u002Fquestions.md`, list the folder, run `git rev-parse --is-inside-work-tree`, `git config user.name`, `claude plugin list --available --json` and `claude plugin marketplace list --json` (used in steps 2 and 4). Then:\n\n- The folder has code (a manifest: `package.json`, `pyproject.toml`, `go.mod`, `composer.json`, `pom.xml`, `Cargo.toml`…, or a `src\u002F`) → say in one line that a team source is a dedicated repo without code, and ask: 1. Stop ← guess (then suggest an empty folder, e.g. `..\u002F\u003Corg>-claude-team`) · 2. Continue here.\n- `.claude\u002Fakg\u002Fconfig.yaml` or `.claude-plugin\u002Fmarketplace.json` already exists → this is already a source: its values are the guesses, source \"current\", and its plugins stay; say so in one line.\n\n## 2. Team stacks\n\nAsk, as a `multiple` question: \"Which stacks does the team work with?\" — 1. Front-end JS\u002FTS · 2. Node back-end · 3. PHP · 4. Python · 5. Go · 6. Java\u002FKotlin · 7. Mobile · 8. Infra (Terraform, Kubernetes); free text for the rest. Guess from an existing marketplace's `relevance`, otherwise from the developer's installed plugins (`claude plugin list --json`: `typescript-lsp` → 1), with the reason; nothing to go on → 1, 2, saying it is only a starting point. Not stored: it only drives the plugin choice and their `relevance` (step 4).\n\n## 3. Team conventions\n\nAsk every active question of the akg catalog (rules.md: Active questions, layer akg only, plus `questions.md` if it exists here), as `\u002Fakg:setup` step 5 does, with these differences:\n- Say once, before the first question, that these answers become the defaults of every project extending this source.\n- Phrase each question for the team (\"Where does the team track tickets?\").\n- No scan: the guess is the recommended option (or the current value of an existing `config.yaml`), so questions come one per message, except where the stacks make the guess obvious (Infra checked → container questions). \"I don't know\" stores the recommended value with a comment.\n- **Skip `per-project`** questions and follow-ups (rules.md), and questions whose condition depends on the project's files (\"Ask only if a container setup is detected\"); list them in one line (\"Left to each project: command environment, local environment, architecture, tracker project, migrations\").\n- `→` checks (CLI on the PATH, MCP configured) are skipped: they belong to each developer's setup. `→` CLAUDE.md and settings lines are not generated here: projects derive them from the answers.\n\nThen ask, as a `multiple` question, \"Which optional questions should projects answer?\": the off-by-default catalog prefixes (`deploy`, `git`, `tests`, `db`, `docs`), each with a one-line description; guess: none. Checked ones are added to `questions:` (with the default prefixes) and asked right away like the others.\n\n## 4. Candidate plugins (no questions)\n\nUse the catalog gathered in step 1: `claude plugin list --available --json` (`installed`, and `available`: `pluginId`, `name`, `description`, `marketplaceName`, `source`) and `claude plugin marketplace list --json`. A marketplace entry here reuses the plugin's `source` object **as is** (`url`, `git-subdir`, `github`…).\n\n- **Installed**: plugins the developer has installed (`installed`), except akg itself.\n  - `source` is an object → reuse it.\n  - `source` is a relative path (`.\u002Fplugins\u002Fx`) in a marketplace from a git or GitHub repo → `{ \"source\": \"git-subdir\", \"url\": \"\u003Cmarketplace repo URL>\", \"path\": \"\u003Cpath without .\u002F>\" }`.\n  - marketplace from a local directory → not shareable: excluded, one line.\n- **Official**: `anthropic-plugin-directory` entries whose `source.url` is under `github.com\u002Fanthropics\u002F`. Pick **at most 6** fitting the stacks and the answers, each with a one-line reason: language servers for the stacks (`typescript-lsp`, `pyright-lsp`, `gopls-lsp`, `php-lsp`, `jdtls-lsp`, `kotlin-lsp-anthropics`…), `frontend-design` for front-end, `terraform` for infra, the tracker's plugin (`linear`, `asana`) or code host's (`github`, `gitlab`), review and commit helpers (`code-review`, `pr-review-toolkit`, `commit-commands`), `security-guidance`. Never a domain plugin (legal, finance, bio…) nothing points to. Skip those already in Installed.\n- **Relevance** for each candidate, with the fixed signals of rules.md, from what the plugin is for: a language server or stack plugin → `manifestDeps` or `filesRead` for that stack (`typescript-lsp` → `filesRead: [\"**\u002F*.ts\", \"**\u002F*.tsx\"]`; a React plugin → `manifestDeps` on `\"react\"`; `terraform` → `filesRead: [\"**\u002F*.tf\"]`). General-purpose plugins (review, commits, tracker) → no `relevance` (proposed on every project).\n\n## 5. Pick the plugins\n\nPropose them as one numbered list (rules.md: Asking, Approvals), under two headings — **Installed**, **Official** — numbering running across both: name, reason, relevance (\"TypeScript projects\" \u002F \"every project\"). Guess: all. Replies like \"ok\", \"all but 4\", \"none\". Empty group → no heading.\n\nThen ask: \"Add more plugins?\" — 1. No ← guess · 2. From an existing project (give its path) · 3. Search the community catalog (give keywords) · 4. From a repo (give `github:owner\u002Frepo` or git URLs). The developer can give the value right away (\"2 ..\u002Fshop\"). Repeat it after each addition until \"no\".\n- **From an existing project**: ask its path if not given. List its skills (`.claude\u002Fskills\u002F\u003Cname>\u002F`), agents (`.claude\u002Fagents\u002F`), commands (`.claude\u002Fcommands\u002F`) and hooks whose script lives in that repo, and offer them as a numbered list, guess: all. Each one becomes a plugin `plugins\u002F\u003Cname>\u002F` here, **copied**; the project is never modified. Relevance from that project's stack, when the item is stack-specific.\n- **Search the community catalog**: ask keywords if not given, match them against `name` and `description` of the other `anthropic-plugin-directory` entries, offer the best matches as a numbered list, guess: none (unreviewed). Say in one line that community plugins are not reviewed by Anthropic.\n- **From a repo**: ask `github:owner\u002Frepo` or git URLs if not given, one per line. Read each repo's `.claude-plugin\u002Fplugin.json` when reachable for its name and description; otherwise use the repo name.\n\nPlugin names must not start with `claude-`: rename a copied one (`claude-review` → `review`) and say it.\n\n## 6. Generate\n\nPrepare, without writing yet:\n\n1. **`.claude\u002Fakg\u002Fconfig.yaml`**: `questions` (only if it differs from the default list) and every answer at its key (format in rules.md). No `extends`, no `synced`.\n2. **`.claude-plugin\u002Fmarketplace.json`**: `name` = `\u003Cfolder name>` (no `claude-` prefix), `owner.name` from `git config user.name`, `plugins` = the chosen ones, each with `name`, `source` (`.\u002Fplugins\u002F\u003Cname>` for copied content, the reused object otherwise), `description`, and `relevance` (`topic` + `signals`, same shape as rules.md) when inferred. Existing file → merge: keep its entries, add the new ones, show conflicts on the same name.\n3. **`plugins\u002F\u003Cname>\u002F`** for each copied item: `.claude-plugin\u002Fplugin.json` (`name`, `description`) and the content in plugin layout — `skills\u002F\u003Cskill>\u002F`, `agents\u002F\u003Cagent>.md`, `commands\u002F\u003Ccommand>.md`, `hooks\u002Fhooks.json`. For hooks, copy the script too and rewrite its path from `$CLAUDE_PROJECT_DIR\u002F…` to `${CLAUDE_PLUGIN_ROOT}\u002F…`.\n4. **`.claude\u002Fakg\u002Fteam.md`** (only if absent): instructions developers read with `\u002Fakg:team`, shown at the end of `\u002Fakg:setup` and diffed by `\u002Fakg:pull`. A short skeleton for the maintainer to fill, with the stacks and the tracker answer as hints:\n   ```markdown\n   # \u003CTeam> — Claude Code\n\n   ## Getting started\n   \u003C!-- What a new developer does first. -->\n\n   ## Tools to install\n   \u003C!-- CLIs, MCP servers (with how to get a token), plugins or skills installed by hand. One line each: what, why, the command. -->\n\n   ## Rules\n   \u003C!-- Team rules that are not in the questions. -->\n   ```\n5. **`README.md`** (only if absent), short: what this repo is, how a project uses it (`\u002Fakg:setup`, give this repo's URL as the team config), how to add a plugin (an entry in `marketplace.json`), developer instructions (`.claude\u002Fakg\u002Fteam.md`) or a team question (`.claude\u002Fakg\u002Fquestions.md`, format in the akg catalog).\n6. **`git init`** if `git rev-parse` says this is not a repo: listed in the review as an action.\n\n## 7. Review and write\n\nSame as `\u002Fakg:setup` step 8: each file's content or diff, copied content shown as a list (`\u003Cproject>\u002F.claude\u002Fskills\u002Freact-forms\u002F → plugins\u002Freact-forms\u002Fskills\u002Freact-forms\u002F`), then one numbered list of the files, guess: write all.\n\nRun `claude plugin validate .` and report errors only.\n\nThen, in at most 3 lines:\n- what was written;\n- next step: commit and push (create the remote first if there is none), then each project runs `\u002Fakg:setup` and gives this repo's URL as the team config;\n- plugins with an external source are installed once per developer: `\u002Fakg:setup` gives the command.\n",{"name":5,"description":7,"allowed-tools":24,"disable-model-invocation":25},"Read(\u002F${CLAUDE_PLUGIN_ROOT}\u002F**), Bash(git rev-parse *), Bash(git config user.name), Bash(git remote *), Bash(claude plugin list *), Bash(claude plugin marketplace list *), Bash(claude plugin validate *)",true,"main","30512499b4db8c7dc6594c5bd329b19caa7cae99","skills\u002Fsource-init","https:\u002F\u002Fgithub.com\u002Fanthonykgross\u002Fakg","https:\u002F\u002Fgithub.com\u002Fanthonykgross","https:\u002F\u002Fanthonykgross.fr","«Do something. If it works, do more of it. If it doesn't, do something else.» - F. D. Roosevelt.","2026-10-30 00:05:47",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":25},[36,39,42],{"tool":37,"command":38},"npx","npx skills add anthonykgross\u002Fakg --skill source-init",{"tool":40,"command":41},"bunx","bunx skills add anthonykgross\u002Fakg --skill source-init",{"tool":43,"command":44},"pnpm","pnpm dlx skills add anthonykgross\u002Fakg --skill source-init","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthonykgross\u002Fakg\u002Fblob\u002Fmain\u002Fskills\u002Fsource-init\u002FSKILL.md",[],[48,54,61,68,75,82],{"skillNo":49,"name":50,"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":51,"categories":52,"keywords":53,"publishedAt":19},"01M7EFPXPJN6WR1BBP2ZANWW3K","team","https:\u002F\u002Fgithub.com\u002Fanthonykgross\u002Fakg\u002Fblob\u002Fmain\u002Fskills\u002Fteam\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},"01M7EFPJJT87MP5KM7977Z2HQ8","setup","First-run setup of Claude Code on a project with akg. Links an optional team config, detects the stack and commands, asks the team\u002Fproject questions, then proposes CLAUDE.md, .claude\u002Fsettings.json and plugins. Use when the user runs \u002Fakg:setup or asks to set up Claude Code for this project with akg.","https:\u002F\u002Fgithub.com\u002Fanthonykgross\u002Fakg\u002Fblob\u002Fmain\u002Fskills\u002Fsetup\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},"01M7EFPD6D7KPZ99PKX99YXR9T","pull","Pull team config updates into a project set up with akg, without overwriting local overrides. Shows what changed on the team side, surfaces conflicts with local overrides, proposes new questions and plugins. Use when the user runs \u002Fakg:pull or the akg session reminder says the team config was updated.","https:\u002F\u002Fgithub.com\u002Fanthonykgross\u002Fakg\u002Fblob\u002Fmain\u002Fskills\u002Fpull\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},"01M7EFP9ZGE5MQAYQ0KGB2G2P9","terraform","Apply the team's Terraform conventions. Fixture skill for akg tests.","https:\u002F\u002Fgithub.com\u002Fanthonykgross\u002Fakg\u002Fblob\u002Fmain\u002Ffixtures\u002Fteam\u002Fplugins\u002Fterraform-helpers\u002Fskills\u002Fterraform\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},"01M7EFP8JWDCDVFG83FZCVFPH1","react","Apply the team's React conventions. Fixture skill for akg tests.","https:\u002F\u002Fgithub.com\u002Fanthonykgross\u002Fakg\u002Fblob\u002Fmain\u002Ffixtures\u002Fteam\u002Fplugins\u002Freact-conventions\u002Fskills\u002Freact\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},"01M7EFP74CSFFXGRE4XYQRFK4S","review","Review the current diff against the team's standards. Fixture skill for akg tests.","https:\u002F\u002Fgithub.com\u002Fanthonykgross\u002Fakg\u002Fblob\u002Fmain\u002Ffixtures\u002Fteam\u002Fplugins\u002Fcode-review\u002Fskills\u002Freview\u002FSKILL.md",[],[]]