richfrem/compile-apm-package
plugins/agent-scaffolders/skills/compile-apm-package/SKILL.md
Activate when the user wants to compile an APM package into top-level context documents such as AGENTS.md, CLAUDE.md, or GEMINI.md, especially for Codex, Gemini, OpenCode, or agents-protocol style hosts. Do not use when the user only needs per-skill installation; use install-apm-package instead.
$ install --global
skillsauthnpx skillsauth add richfrem/agent-plugins-skills compile-apm-packageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 18, 2026, 5:18 AM166.3s3 files scanned
SKILL.md
- name:
- compile-apm-package
- description:
- >-
- allowed-tools:
- Bash, Read, Glob
compile-apm-package Skill 📄
Overview
This skill generates merged context documents from APM primitives. This is primarily required for harnesses that consume a single authoritative file (like Gemini's GEMINI.md) rather than distributed skill directories.
🚫 Non-Negotiables
- Artifact Status — Compiled files (
AGENTS.md, etc.) are generated artifacts. NEVER edit them directly if a.apm/source tree exists. - Conditional Use — Do not run compile if the user's harness (e.g., Claude Code, Copilot Chat) supports native directory-based skills.
- Validation First — Ensure the package is valid before merging primitives.
Decision Tree
- Target supports directory-based skills? -> Use
install-apm-package. - Target needs top-level context? (e.g., Gemini, Codex) -> Run
apm compile. - Authoring shared context? -> Use
apm compileto verify how fragments merge into the final doc.
Workflow
- Verify
apm.ymlexistence. - Execute
python scripts/validate_apm_package.py. - Identify target requirements.
- Run
apm compile [--target <slug>]. - Report the location of generated context files.
Anti-Patterns
- Unnecessary Compilation: Running
apm compilefor a Claude Code project (redundant work). - Direct Artifact Editing: Fixing a typo in
GEMINI.mdinstead of the source.prompt.md.
Related Skills
richfrem/vector-db-ingest
tools
VerifiedTrustedCommunity
Ingests repository files into the ChromaDB vector store. Builds or updates the vector index from a manifest or directory scan using ingest.py. Use when new files need to be indexed or the vector store is out of date. <example> user: "Index these new plugin files into the vector database" assistant: "I'll use vector-db-ingest to add them to the vector store." </example> <example> user: "The vector store is missing recent files -- update it" assistant: "I'll use vector-db-ingest to re-index the changes." </example>
3SKILL.mdUpdated Jun 2, 2026
richfrem/vector-db-cleanup
data-ai
VerifiedTrustedCommunity
Removes stale and orphaned chunks from the ChromaDB vector store for files that have been deleted or renamed. Use after files are removed or moved to keep the vector index in sync with the filesystem. <example> user: "Clean up the vector store after I deleted some files" assistant: "I'll use vector-db-cleanup to remove orphaned chunks." </example> <example> user: "The vector database has chunks for files that no longer exist" assistant: "I'll run vector-db-cleanup to prune them." </example>
3SKILL.mdUpdated Jun 2, 2026
richfrem/vector-db-audit
testing
VerifiedTrustedCommunity
Audit Vector DB coverage -- compares the live filesystem manifest against the ChromaDB index to identify coverage gaps.
3SKILL.mdUpdated Jun 2, 2026
richfrem/rlm-search
development
VerifiedTrustedCommunity
3-Phase Knowledge Search strategy for the RLM Factory ecosystem. Auto-invoked when tasks involve finding code, documentation, or architecture context in the repository. Enforces the optimal search order: RLM Summary Scan (O(1)) -> Vector DB Semantic Search -> Grep/Exact Match. Never skip phases.
3SKILL.mdUpdated Jun 2, 2026