skills.rest
drgaciw
drgaciwCOMMUNITY
Explore all skills by this author →
GitHub

pmos-integration

Connects Foundations and PMOS repositories through a read-only cross-repo skill manifest.

Updated Sep 23, 2026
Search Tags:#integration#yaml#manifest#salesforce#resolver#cross-repo#revenue cloud
One-click install
npx skills add https://github.com/drgaciw/rlm-base-dev-fork --skill pmos-integration-drgaciw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pmos-integration
Source: https://github.com/drgaciw/rlm-base-dev-fork/tree/main/.cursor/skills/pmos-integration
Command: npx skills add https://github.com/drgaciw/rlm-base-dev-fork --skill pmos-integration-drgaciw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers working across the Foundations (rlm-base-dev) and PMOS (pmos-revenue-cloud) repositories need to consume content from the other repo—PRDs, demo scripts, roadmap, schema, Help articles—without forking, duplicating, or breaking standalone operation when the sibling clone is absent. ## Core Features & Use Cases - Cross-repo manifest resolution: Declares skills and grounding artifacts (ERD, Help mirror, qb-scenario reference, API reference) in .claude/skill-manifest.yml and resolves them via scripts/ai/skill_manifest.py using environment variables or sibling-directory fallback. - Temporal split governance: Documents which repo is canonical—PMOS owns future state (PRDs, roadmap, capability map), Foundations owns current state (built schema, deployed flags, real records). - Graceful degradation: Consumer skills operate standalone when the sibling clone is missing; cross-repo lookups are skipped rather than failing. - Use Case: A maintainer authors a PRD in PMOS that cites real schema by reading the Foundations ERD through the resolver instead of relying on stale narrative summaries. ## Quick Start Run python scripts/ai/skill_manifest.py --check to verify the manifest resolves both repository clones and lists available skills.

Frequently Asked Questions about pmos-integration

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

FAQPage Schema
How do I resolve content from another repository in a skill?▼

Use the skill_manifest.py resolver with load_manifest() and resolve_grounding() to locate artifacts by repo and key. It checks $FOUNDATIONS_REPO_ROOT or $PMOS_REPO_ROOT environment variables, falling back to sibling-directory layout like ../pmos-revenue-cloud.

What is the temporal split between PMOS and Foundations?▼

PMOS is canonical for future state such as PRDs, roadmap, and proposed schema changes, while Foundations is canonical for current state like built schema, deployed feature flags, and real records. Do not place proposed content in Foundations or runtime-verified state in PMOS.

Does the manifest work if the PMOS clone is not present?▼

Yes, the manifest degrades gracefully. If a sibling clone is absent, the consumer skill operates standalone and skips cross-repo lookups. Nothing breaks; the cross-repo upgrade simply is not available.

Can I use git submodules or symlinks for cross-repo grounding?▼

No, submodules and symlinks are explicitly prohibited because they are operationally fragile across OS layouts and break Claude Code skill discovery. The manifest uses plain filesystem paths resolved at runtime instead.

What are the limitations of the PMOS integration manifest?▼

The manifest is read-only on both sides and requires per-skill opt-in, so not all skills consume cross-repo content automatically. PMOS is document-centric, so no Python or build tooling should be shipped into it.

Related Skills

Explore More Product & Management Skills→
SalesforceLabsSalesforceLabs
5

pmos-integration

Connects Foundations and PMOS repositories through a read-only cross-repo skill manifest.

Official
Intermediate
bgaldinobgaldino
33

qb-demo-script

Generate per-release QuantumBit Revenue Cloud demo walkthrough Markdown for Slack canvases.

Community
Advanced
stickerdanielstickerdaniel
49

upstream-sync

Automate synchronization and review of changes between a template repository and a fork.

Community
Intermediate
VitaDynamicsVitaDynamics

light-plan(brain-storming)

Transform user ideas into structured design documents through guided questioning.

Official
Intermediate