om-framework-context

Resolves exact installed Open Mercato package versions, AGENTS.md chains, and bounded source context.

1.7k|382|Updated Sep 10, 2025
One-click install
npx skills add https://github.com/open-mercato/open-mercato --skill om-framework-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: om-framework-context
Source: https://github.com/open-mercato/open-mercato/tree/main/packages/create-app/agentic/shared/ai/skills/om-framework-context
Command: npx skills add https://github.com/open-mercato/open-mercato --skill om-framework-context

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

When generated facts cannot answer a question about the Open Mercato framework, developers risk guessing against stale contracts or dumping unbounded node_modules searches. This Skill resolves the exact installed package/module versions, the original AGENTS.md instruction hierarchy, and source roots as a narrow, read-only evidence chain.

Core Features & Use Cases

  • Exact Version Resolution: Runs yarn framework:context --module <id> or --package <name> to identify the precise installed contract, verified against src/modules.ts and generated fact stamps.
  • Bounded Source Search: Uses a globally capped boundedSearch.result for narrow queries instead of unbounded node_modules scans.
  • Skew and Escalation Handling: Provides procedures for duplicate versions, missing source or AGENTS files, snapshot mismatches, and contradictions, including when to regenerate facts or escalate upstream.
  • Use Case: An AI agent needs to know how an installed CRM module implements a feature. The Skill resolves the exact package version, reads the AGENTS.md chain in precedence order, inspects only relevant source files, and reports a writable app-side conclusion.

Quick Start

Ask the agent to inspect the installed framework source for a specific module, for example: resolve the exact installed context for the catalog module and find how it registers custom fields.

Frequently Asked Questions about om-framework-context

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

FAQPage Schema
How do I inspect the installed Open Mercato framework source?

Run yarn framework:context with the --module or --package flag and an optional narrow --query. The resolver returns the exact installed version, the AGENTS.md instruction chain, source roots, and a globally capped bounded search result without scanning all of node_modules.

How do I find the AGENTS.md files for an installed module?

The framework context resolver reports the full instruction chain in precedence order: app root rules, compatibility snapshot, nearest package or module guide, and generated facts. Read them in that order and only the relevant source files.

What should I do when generated facts mismatch the installed package version?

Do not use stale facts with newer source. After registry inputs change, run yarn generate followed by yarn mercato agentic:init --update-harness; after a dependency-only upgrade, run only the update command to refresh harness facts.

Can this skill modify files inside node_modules?

No. Installed source, AGENTS.md files, compatibility snapshots, and generated facts are treated as read-only evidence. The workflow only reports an app-side implementation conclusion and never edits the installed packages.

What happens when duplicate module versions are installed?

The escalation procedure requires an explicit package and version selected by app-root resolution, and all duplicate candidates must be reported. Never mix contracts across package versions or guess through an unresolved contradiction.