apc-context

Reads and migrates APC project context from .apc/ directories and AGENTS.md files.

6|1|Updated May 8, 2026
One-click install
npx skills add https://github.com/agentprojectcontext/apx --skill apc-context-agentprojectcontext
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: apc-context
Source: https://github.com/agentprojectcontext/apx/tree/main/skills/apc-context
Command: npx skills add https://github.com/agentprojectcontext/apx --skill apc-context-agentprojectcontext

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents often lack awareness of project-specific context such as agent definitions, shared rules, and curated memory, and teams risk mixing durable project knowledge with private runtime state like sessions and secrets. This Skill teaches the agent how to read, interpret, and safely migrate APC (Agent Project Context) files. ## Core Features & Use Cases - Context Discovery: Automatically activates when a project contains a .apc/ directory or AGENTS.md file and reads agent definitions, skills, memory, and MCP hints before answering. - Guided Migration: Detects .apc/migrate.md, offers to migrate legacy context files, and classifies content into agent definitions, shared rules, curated memory, or content that must stay local. - Visibility Enforcement: Applies strict rules about what may be committed (agent definitions, curated memory) versus what must stay local or private (sessions, conversations, secrets, caches). - Use Case: A developer opens a repository initialized with APC; the agent reads .apc/agents/ and AGENTS.md first, answers questions about which agents exist, and offers to migrate leftover context files without leaking runtime sessions into git. ## Quick Start Ask the agent which agents are defined in this project and have it read the .apc directory and AGENTS.md before answering.

Frequently Asked Questions about apc-context

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

FAQPage Schema
How do I give an AI agent project context with APC?▼

Place an AGENTS.md file at the repository root and a .apc/ directory containing project.json, agent definitions under .apc/agents/, and optional memory.md and mcps.json files. The agent reads these files before making assumptions about project structure.

What files belong in the .apc directory?▼

The .apc/ directory holds project.json, agent definitions in .apc/agents/<name>.md, reusable instructions in .apc/skills/, curated memory in memory.md, and MCP hints in mcps.json. Sessions, conversations, caches, and secrets must never be stored there.

Should agent memory be committed to git in APC?▼

Only curated, team-safe project memory in .apc/memory.md should be committed. An individual agent's own memory is runtime state and lives under ~/.apx/projects/<apx_id>/agents/<slug>/, never inside the repository.

How does APC migration of legacy context files work?▼

When .apc/migrate.md exists, the agent offers to migrate listed files, classifying content into agent definitions, shared rules, skills, or curated memory. Raw sessions, secrets, and IDE settings are left in place, and migrate.md is deleted afterward.

Can APC store conversation history or session logs?▼

No. Sessions, conversations, messages, and tool logs belong to the runtime that created them, such as Codex, Claude Code, or APX storage under ~/.apx/. APC only stores portable, durable project context.