richfrem/os-architect
plugins/agent-agentic-os/skills/os-architect/SKILL.md
SME-facing front-door skill for Agentic OS ecosystem evolution. Invokes the os-architect interview flow: classifies intent, audits existing capabilities, proposes evolution path (orchestrate / update / create), and dispatches work. Use when evolving plugins, skills, or agents — whether applying a new pattern, setting up an improvement lab, filling a capability gap, or coordinating multiple loops.
$ install --global
skillsauthnpx skillsauth add richfrem/agent-plugins-skills os-architectInstall 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: Jun 29, 2026, 5:40 AM346.3s2 files scanned
SKILL.md
- name:
- os-architect
- plugin:
- agent-agentic-os
- description:
- >
- interview flow:
- classifies intent, audits existing capabilities, proposes evolution path
- model:
- inherit
- color:
- purple
- tools:
- ["Bash", "Read", "Write"]
Role
os-architect is the single entry point to the Agentic OS evolution ecosystem. The user
invokes it when they want to evolve or build anything in the agent/skill/plugin ecosystem.
It interviews, audits, and routes — never implements directly. The full behavior spec lives
in agents/os-architect-agent.md.
How to Invoke
/os-architect
No arguments needed. Start with a plain-language description of what you want to evolve.
What It Does
- Phase 1 — Intent Interview: classifies the request into one of 5 evolution categories
- Phase 2 — Ecosystem Audit: verifies what capabilities exist vs what's missing
- Phase 3 — Proposal + Dispatch: proposes Path A/B/C and dispatches via the user's CLI tools
Dispatch Paths
| Path | When | Mechanism |
|------|------|-----------|
| A+ — No Action | audit shows full match + all patterns present | tell user, no dispatch |
| A — Orchestrate | capability exists, current | route to existing agent/skill + run_agent.py |
| B — Update | capability exists, outdated/incomplete | os-evolution-planner writes plan + prompt → dispatch + optional improvement loop |
| C — Create | gap confirmed | create-sub-agent scaffold → os-evolution-planner plan + prompt → eval lab → evals HARD-GATE → os-architect-tester validates |
Related Capabilities
| Skill / Agent | Purpose |
|---------------|---------|
| os-evolution-planner skill | Called for Path B/C: writes structured task plan + Copilot CLI delegation prompt |
| os-architect-tester agent | Validates os-architect correctness via scenario simulation — run after any changes |
| improvement-intake-agent | Called for Category 3 (Lab Setup): configures the skill improvement run |
| create-sub-agent | Called for Path C (Gap Fill): scaffolds the new agent/skill file |
Gotchas
- Invoked without clear intent: If the user says only "help me" or "I don't know where to start", run Phase 1 open question first — do not assume intent category.
- PATH detection gives false positive:
which ghreturns a result but Copilot CLI is not configured. Always confirm tool availability with the user before using a detected tool for dispatch. - Path C evals HARD-GATE is non-negotiable: The evals review gate before the first improvement loop must not be skipped even if the user says "just run it." Bad evals waste improvement loop compute.
Smoke Test
- Given "I found a new browser harness pattern and want to apply it to my skills" → classifies as Category 1 (Pattern Abstraction), proposes Path A or B, within 2 turns
- Given "I need an agent that audits plugin evals for staleness, it doesn't exist yet" → classifies as Category 4 (Gap Fill), proposes Path C, surfaces eval HARD-GATE
- Given "run 50 iterations on my os-eval-runner skill" → classifies as Category 3 (Lab Setup), routes to improvement-intake-agent, asks about CLI tools before proposing dispatch strategy
- Given "I want to explore improving how we generate agents and maybe create one" → agent identifies Low confidence (Cat 3 + Cat 4 overlap), asks clarifying question before proceeding to Phase 2
Related Skills
richfrem/issue-worktree-agent
testing
VerifiedTrustedCommunity
Skill for creating and managing isolated git worktrees (`.worktrees/issue-NNN`) for issue execution branches. USE ONLY when setting up or cleaning up isolated git worktrees for specific issue execution. DO NOT USE for managing local task files (use `task-agent`) or escalating tasks to issues (use `github-issue-backlog-agent`).
4SKILL.mdUpdated Jul 29, 2026
richfrem/issue-pr-lifecycle-agent
data-ai
VerifiedTrustedCommunity
Skill for orchestrating the end-to-end GitHub issue lifecycle flow: Issue -> Worktree -> Implementation -> PR Creation -> Resolution Closure. USE ONLY when running or dry-running full lifecycle orchestration for resolving an issue with a PR. DO NOT USE for isolated worktree management only (use `issue-worktree-agent`) or logging issues (use `github-issue-agent`).
4SKILL.mdUpdated Jul 29, 2026
richfrem/github-issue-prioritizer
tools
VerifiedTrustedCommunity
Automatically ranks GitHub issues (P0-P3) based on friction tier, frequency, and blockages, synchronizing priority labels and GitHub Projects v2 custom fields.
4SKILL.mdUpdated Jul 29, 2026
richfrem/github-issue-backlog-agent
testing
VerifiedTrustedCommunity
Bridge skill for escalating ephemeral local task scratchpad items (`tasks/*.md`) into durable, taxonomy-validated, evidence-rich GitHub Issues. USE ONLY when promoting a single-session local task into durable repository backlog. DO NOT USE for managing local kanban boards (use `task-agent` instead) or directly querying/commenting on issues (use `github-issue-agent` instead).
4SKILL.mdUpdated Jul 29, 2026