integration

Integrates agent-core configuration into projects via sync for Claude Code and bundle for OpenCode.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/gmolike/Claude-Template --skill integration-gmolike
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration
Source: https://github.com/gmolike/Claude-Template/tree/main/.claude/skills/integration
Command: npx skills add https://github.com/gmolike/Claude-Template --skill integration-gmolike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up AI agent configuration (rules, skills, agents, MCP servers) across different tools like Claude Code and OpenCode is error-prone and inconsistent. This Skill automates the integration of agent-core as the single source of truth, generating the correct target artifacts for each platform and verifying the result. ## Core Features & Use Cases - Context and scope detection: Detects whether the project is an existing repo or fresh bootstrap, whether agent-core is installed or a local checkout, and resolves global vs. project scope. - Target-specific generation: Runs sync for Claude Code (CLAUDE.md, .claude/skills, agents, merged settings.json, .mcp.json) and handles the consume-only .tgz bundle workflow for OpenCode (download or build, then extract to ~/.config/opencode/). - MCP wiring and verification: Identifies required environment variable names (e.g., GITHUB_TOKEN) without hardcoding secrets, then verifies each target against a target-specific Definition of Done. - Use Case: A developer clones a new project and wants the team's shared AI agent rules and MCP setup applied. The Skill detects the context, syncs the project-scope Claude Code config, unpacks the OpenCode bundle, and reports which env vars still need to be set. ## Quick Start Ask the assistant to integrate agent-core into the current project at project scope and verify the generated Claude Code and OpenCode configuration.

Frequently Asked Questions about integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate agent-core into an existing project?

Run agent-core sync with project scope: `agent-core sync --scope project --dir .` for an installed binary, or `pnpm dev sync --scope project --dir .` from a local checkout. This writes CLAUDE.md, .claude/skills, agents, merged settings.json, and .mcp.json into the project.

How do I install the OpenCode configuration from agent-core?

OpenCode is not synced; it uses a consume-only .tgz bundle. Download the published agent-core-opencode-*.tgz release asset or build it with `agent-core bundle`, then extract it into ~/.config/opencode/ with tar using --strip-components=1.

What is the difference between agent-core sync and bundle?

sync generates the Claude Code target (CLAUDE.md, .claude directory, settings.json) non-destructively and idempotently. bundle is a build step that produces the OpenCode .tgz artifact, which is then downloaded or extracted as a consume-only config.

Does agent-core sync overwrite my existing CLAUDE.md?

No. A handwritten CLAUDE.md without the <!-- GENERATED header is never overwritten. The sync is non-destructive and idempotent, and settings.json is merged without losing keys like statusLine, enabledPlugins, env, or theme.

Which environment variables does the MCP setup require?

The required variable names come from shared/mcp/servers.json; currently only the github server needs GITHUB_TOKEN. The bundle's SETUP.md documents this, and secret values must never be hardcoded—only variable names are referenced.

Why does pnpm sync not write to my project directory?

pnpm sync always runs in global scope, writing to ~/.claude/. For project-level output, use `pnpm dev sync --scope project --dir <path>` or the installed binary with the --scope project flag.