mg-add-context

Registers external Git and local projects as read-only context references for MG agents.

1|1|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/wonton-web-works/miniature-guacamole --skill mg-add-context
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mg-add-context
Source: https://github.com/wonton-web-works/miniature-guacamole/tree/main/src/framework/skills/mg-add-context
Command: npx skills add https://github.com/wonton-web-works/miniature-guacamole --skill mg-add-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Register external projects as read-only context references for MG agents to enable cross-project learning without memory sharing.

Core Features & Use Cases

  • Read-only cross-project references for agents to inspect code, architecture decisions, and patterns.
  • Lightweight registry in .claude/memory/project-contexts.json to track alias, path/URL, and metadata.
  • Safe GitHub/local context registration with path/URL validation and summary extraction.

Quick Start

Register a local project path or a GitHub URL as a new context and verify it appears in the registry.

Frequently Asked Questions about mg-add-context

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

FAQPage Schema
How do I reference another project's code without sharing memory or write access?▼

You can register external projects as read-only context references for agents. This enables cross-project learning while preserving NDA-safe isolation by restricting writes to external projects.

Can I register a GitHub repository as context for local agent code reviews?▼

Yes, you can register GitHub repositories as context references. The Skill validates the target path or URL, extracts summaries from CLAUDE.md or README.md, and stores the entry in a local registry.

How does cross-project context registration work for feature planning?▼

Cross-project context registration validates the target path exists, extracts documentation summaries, and records the alias and metadata in .claude/memory/project-contexts.json for agents to inspect architecture decisions and patterns.

What is the best way to give an agent read-only access to external project architecture?▼

Registering external projects as read-only context references is the best approach. It creates a lightweight registry entry that allows agents to inspect code and patterns without granting write permissions or sharing memory.

Does context registration work with local directories and GitHub URLs?▼

Yes, context registration applies to both local directories and GitHub repositories. It validates that the target path exists and safely extracts summaries from CLAUDE.md or README.md files.

Why should I not use direct file access instead of a read-only context registry?▼

Direct file access risks unintended modifications and lacks NDA-safe isolation. A read-only context registry restricts writes to external projects and maintains a tracked registry in .claude/memory/project-contexts.json for safe reference.