agentsclimarketplace

Integration init

Skill artemrudenko/skill-governance-toolkit/skills/integration-init

Interactive bootstrap for optional integrations (code-review-graph, repomix, serena, plus the Claude-only secret-guard hook). Runs their native installers and injects per-integration documentation into AGENTS.md and agents/code-reviewer.md — only for tools actually installed. Use when: «init», «initialize toolkit», «set up integrations», «add code-review-graph», «add repomix», «add serena», «add secret-guard», «bootstrap toolkit», «configure integrations». Idempotent: re-running syncs documentation to install state. Run with `--advise-only` for non-mutating dry preview.From its SKILL.md

Install
npx -y skills add artemrudenko/skill-governance-toolkit --skill integration-init

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

12.7 KB, as published. Nobody here has run it

Integration Init

Skill type: MUTATING gateway — runs native installers (pipx/npm), injects documentation blocks into AGENTS.md + agents/code-reviewer.md via paired markers. Marker-block append semantics: existing user content OUTSIDE markers is NEVER modified.

Purpose: bootstrap optional integrations into the toolkit. Walk the user through a two-stage selection (which tools, then per-tool config), run native installers, and inject conditional documentation that reflects actual install state — never mention a tool that isn't installed.

This skill is a gateway (clarification prompts permitted per library-audit Phase 1.3).

Runtime notes: Interactive clarification in Phase 1/2 only. Use AskUserQuestion only on hosts that provide it; otherwise ask plainly in chat. For non-interactive use, the bash fallback is $SGT_ROOT/scripts/init.sh (resolve $SGT_ROOT per references/path-resolution.md — under a plugin/global install the runtime CWD is the user's project, not the install dir). Claude/Copilot/Cursor/Codex — full skill flow. Gemini — same skill flow but structured prompt fallback may differ.

When to use

Always:

  • First-time setup: user has just dropped the toolkit into a project and types «init», «initialize», «set up integrations».
  • User explicitly asks to add a specific optional tool: «add code-review-graph», «install repomix», «add serena».
  • After cloning the repo for a new team member — bootstrap their environment.

ESPECIALLY when:

  • User has a large codebase (> 50 files) and code-reviewer agent is overflowing context — CRG addresses this directly.
  • User runs multi-repo / monorepo setup — CRG's multi-repo daemon helps.
  • User does external code review (reviewing third-party repos) — repomix gives one-shot context.

Skip / Don't use for:

  • Production deployments where shell access is restricted — use --advise-only flag instead.
  • User just wants to score one skill → use skill-evaluate.
  • User just wants to audit library → use library-audit.
  • User wants to convert a non-portable skill → use skill-build-portable.

Don't skip when:

  • «I'll just npm install manually» — manual installs leave documentation out of sync. This skill keeps AGENTS.md, code-reviewer.md handoffs, and active install state in lock-step.

Predecessor

Required upstream: none — entry-point skill invoked directly by user phrase or /integration-init slash command. (Gateway skill: no predecessor required.)

Successor

Default downstream: terminal — emit installation report, suggest first-run command for each newly active integration.


Required inputs

All optional; defaults drive interactive flow.

InputTypeDefaultDescription
MODEenum: auto-install / advise-onlyauto-installadvise-only prints commands instead of running them — safer on locked-down corporate machines
WITHcomma listnoneNon-interactive selection from crg / repomix / serena / secret-guard / all (e.g. WITH=crg,repomix); skips Phase 1 user prompt. all expands to the three cross-host tools (crg,repomix,serena) and EXCLUDES secret-guard — it is Claude-hook-specific, opt-in by name only
USE_FORKbooleanfalseIf true and CRG selected, install better-code-review-graph fork instead of upstream main
USE_MCPenum: mcp / cli / askaskFor CRG: MCP server mode vs CLI mode; ask prompts through the host's clarification mechanism
BUILD_MODEenum: full-now / full-later / skip / askaskFor CRG: initial graph build strategy
INSTALL_PRECOMMITenum: yes / no / askaskFor CRG: optional supplementary pre-commit hook (CRG already installs its own post-edit hook)

Workflow

Phase 0 — Environment detection

Detect host runtime, package managers (python3 ≥ 3.10, pipx, node, npm), currently-installed integrations (which {tool}), and repo context (AGENTS.md, agents/code-reviewer.md, .git/). Hard-fail if a selected tool's prereq is missing — warn only if the prereq is for a tool not selected.

Full detection logic, prereq matrix, and state-snapshot schema → references/env-detection.md.

Phase 1 — Ask which tools to install

If WITH input is provided, skip this phase and use that list. Otherwise ask a multi-select clarification across code-review-graph · repomix · serena · secret-guard. If user selects nothing → emit no-op report and exit cleanly.

secret-guard is special — Claude-Code-only, opt-in, defense-in-depth. Offer it only when the host runtime is Claude Code (hooks have no cross-tool equivalent). Present it with the honest framing: a best-effort PreToolUse tripwire blocking obvious secret-read / exfil Bash commands — NOT a security boundary, bypassable, and it does NOT relax the SEC/SCR/HOOK audit gates. On non-Claude hosts, do not list it. Full spec → references/integrations.md §secret-guard.

Phase 2 — Per-tool configuration

For each selected tool, run sub-config via the host's clarification mechanism. Skip configs already answered via CLI inputs.

  • CRG: Q-CRG-1 variant · Q-CRG-2 MCP/CLI · Q-CRG-3 enrichment · Q-CRG-4 build · Q-CRG-5 pre-commit
  • repomix: Q-RPX-1 --init y/n
  • serena: Q-SRN-1 languages multi-select

Full question definitions, options, and decision hints → references/sub-configs.md.

Phase 3 — Install (or advise)

For each selected integration with its sub-config: run install commands (MODE=auto-install) or print them (MODE=advise-only). Per-tool install state checkpointed after each tool completes (network failure recovery).

Per-tool install command sequences (CRG variants, repomix, serena) → references/integrations.md §Install commands.

Phase 4 — Verify install

For each newly installed integration, run a verification command ({tool} --version / which {tool}). Verification result gates Phase 5 doc injection: pass → inject; fail → log error and skip injection for that tool. Suggest --advise-only re-run on failure to see commands.

Phase 5 — Inject documentation (only for installed integrations)

For each successfully verified integration (see Phase 4 verify-before-inject in Hard rules), insert a marker block into AGENTS.md (outer marker <!-- skill-init: integrations BEGIN/END -->) and agents/code-reviewer.md (outer marker <!-- skill-init: handoffs BEGIN/END -->). The inner per-integration marker differs per file: <!-- skill-init: integration:{tool} BEGIN/END --> in AGENTS.md, and <!-- skill-init: handoff:{tool} BEGIN/END --> in code-reviewer.md. Append-or-update on install, remove on deselect. Edit these blocks directly (atomic write) — marker_block.py manages only the outer installer block (<!-- {marker_id}: BEGIN/END --> grammar), not the skill-init: marker family.

Full per-tool marker-block templates (AGENTS.md + code-reviewer handoffs, CRG / repomix / serena) → references/integrations.md §Documentation block template / §Handoff template.

secret-guard injects differently — Claude-only target, never AGENTS.md. Hooks are not portable, so its doc block must NOT enter the portable AGENTS.md body (doing so would break the toolkit's own portability claim). Inject the <!-- skill-init: integration:secret-guard BEGIN/END --> block into the Claude-only path (e.g. CLAUDE.md below the «Claude Code specifics» section), and only after the user has registered the hook in .claude/settings.json. The hook ships as a skill asset (assets/secret-guard-hook.py) — no installer binary; register it via the .claude/settings.json hooks.PreToolUse snippet in references/integrations.md §secret-guard. There is no code-reviewer.md handoff (passive guard, not a dispatch target).

Phase 6 — Report

Emit final summary: Selected: / Installed: (with versions) / Failed: (with errors) / Skipped: (re-detected) / documentation blocks injected / next-step commands per active integration.


State persistence (resumable runs)

Highest-risk skill for partial completion: a network failure mid-install can leave one of three tools half-installed and AGENTS.md out of sync with reality. Checkpointing makes each per-tool install atomic from the user's perspective.

PhaseCheckpoint?What is stored
P0 — environment detectionyesdetected runtime + package managers + currently-installed tools
P1 — ask which toolsyesselected tools
P2 — per-tool configurationyesper-tool sub-config answers
P3 — install/adviseyes — after each per-tool install completesinstall status per tool + version
P4 — verify installyesper-tool verification results
P5 — inject documentationyeswhich marker blocks were updated
P6 — reportno (terminal)—
  • Default RESUME=ask (gateway skill — user expects prompts; if a prior run is unfinished, ask whether to resume).
  • On resume: skip already-installed tools (verified via which); pick up at first unverified tool.
  • State location: ${CWD}/.skill-state/integration-init/run-{utc-timestamp}.json.

Hard rules

  • ❌ Never inject documentation for tools that are not actually installed (verified via which).
  • ❌ Never modify content outside paired BEGIN/END markers.
  • ❌ Never auto-install in --advise-only mode.
  • ❌ Never overwrite user-customized content outside paired markers. Content inside toolkit-managed markers is owned by this skill and may be replaced on re-run; users customize outside markers.
  • ✅ Verify-before-inject: after pipx install / npm install etc., MUST run a verification command (e.g. which {tool} or {tool} --version). ONLY if verification passes, inject the per-tool documentation block. If verification fails, log the failure AND skip the doc injection for that tool.
  • ✅ Rollback for marker-block writes: edits are atomic, so partial state is impossible. To uninstall a tool's docs, delete its block from BOTH files: the <!-- skill-init: integration:{tool} BEGIN -->…END block in AGENTS.md, and the <!-- skill-init: handoff:{tool} BEGIN -->…END block in agents/code-reviewer.md. (Do NOT use marker_block.py remove for these — its {marker_id}: BEGIN grammar cannot match the skill-init: marker family and silently no-ops. The bash fallback scripts/init.sh removes them on deselect.)
  • ✅ --advise-only mode emits commands to stdout for user copy-paste; runs NO installers, injects NO docs. For locked-down environments where the skill cannot execute installers.
  • ✅ Idempotent — re-running with no changes produces no diff.
  • ✅ Re-running with a tool deselected removes its blocks from both files.
  • ✅ Detection via which {tool} is authoritative — markers reflect reality, not user intent.
  • ✅ Clarification policy: permitted ONLY in Phase 1, Phase 2, and the resume prompt. Non-interactive runs must provide WITH and per-tool inputs or use $SGT_ROOT/scripts/init.sh (resolve $SGT_ROOT per references/path-resolution.md).
  • ✅ Resumable — per-tool checkpoint in Phase 3 makes mid-install crashes recoverable without re-prompting the user.

Examples

Three end-to-end walkthroughs (first install / advise-only / re-run with deselection) → references/examples.md.


What this skill does NOT do

  • Uninstall binaries — if you deselect a tool, only documentation is removed; uninstall the binary manually.
  • Configure tool-specific behavior beyond initial setup — e.g. won't tune repomix.config.json rules or pick CRG embedding model.
  • Skill-level operations — that's the job of skill-find / skill-evaluate / skill-compare / library-audit / skill-build-portable.

Keep looking

Skills are one crate of 608,475. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.