How do I install the Orbitant 12 Factor skill?

Run npx skillmds@latest add weorbitant/orbitant-12-factor in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Orbitant 12 Factor safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Orbitant 12 Factor?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Orbitant 12 Factor free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Orbitant 12 Factor?

weorbitant (@weorbitant) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Orbitant 12 Factor by weorbitant — Agent Skill

Name: Orbitant 12 Factor
Author: weorbitant

Orbitant 12 Factor

Use when checking if a repo follows 12-factor app principles — config stored in env vars (not hardcoded), dependency lockfiles present, CI pipeline separation, structured logging to stdout, or dev/prod environment parity. Activates when someone asks about 12-factor compliance, deployment readiness, or config management practices in a Node.js or Python project. Also trigger when someone notices hardcoded localhost URLs, missing .env.example, or asks "is this deploy-ready?" — even without mentioning 12-factor explicitly.

weorbitant e6eb12c 2 files · 5.6 KB Updated Sep 17, 2026

File contents

Overview

Audits the statically-verifiable subset of 12-factor app compliance. Only factors observable from the repo are scored — runtime factors are listed as "not checked" with an explanation.

When to Use

Assessing deployment readiness of a new project
Checking config management practices (hardcoded URLs, missing .env.example)
Reviewing CI pipeline separation
Running a section audit after /orbitant-engineering:ground-control flagged 12-factor issues

How to Run

Load the reference standards:

@plugins/orbitant-engineering/skills/12-factor/references/12-factor.md

Detect the stack first:

ls package.json requirements.txt pyproject.toml 2>/dev/null

Then run checks for all statically-verifiable factors. Note which factors were skipped and why.

Output Format

## 12-Factor Compliance   {rating}

### Passing
- II. Dependencies: lockfile present (package-lock.json), versions pinned
- V. Build/release/run: CI pipeline defined (.github/workflows/)

### Failing
- III. Config: hardcoded URLs found in source
  Finding: "http://localhost:3000" in src/api/client.js:8
  Recommendation: move to process.env.API_URL, add to .env.example

### Not checked (requires runtime)
- Factors I, IV, VI, VII, VIII, IX, XII
  Reason: not observable from static repo analysis

Rating: ⚠️ Partial

Ratings: ❌ Not compliant / ⚠️ Partial / ✅ Good / 🚀 Fully observable compliance

See references/12-factor.md for full criteria and excluded factors explanation.

---name: orbitant-12-factordescription: Use when checking if a repo follows 12-factor app principles — config stored in env vars (not hardcoded), dependency lockfiles present, CI pipeline separation, structured logging to stdout, or dev/prod environment parity. Activates when someone asks about 12-factor compliance, deployment readiness, or config management practices in a Node.js or Python project. Also trigger when someone notices hardcoded localhost URLs, missing .env.example, or asks "is this deploy-ready?" — even without mentioning 12-factor explicitly.license: MIT---## OverviewAudits the statically-verifiable subset of 12-factor app compliance. Only factors observable from the repo are scored — runtime factors are listed as "not checked" with an explanation.---## When to Use- Assessing deployment readiness of a new project- Checking config management practices (hardcoded URLs, missing .env.example)- Reviewing CI pipeline separation- Running a section audit after `/orbitant-engineering:ground-control` flagged 12-factor issues---## How to RunLoad the reference standards:`@plugins/orbitant-engineering/skills/12-factor/references/12-factor.md`Detect the stack first:```bashls package.json requirements.txt pyproject.toml 2>/dev/null```Then run checks for all statically-verifiable factors. Note which factors were skipped and why.---## Output Format```## 12-Factor Compliance {rating}### Passing- II. Dependencies: lockfile present (package-lock.json), versions pinned- V. Build/release/run: CI pipeline defined (.github/workflows/)### Failing- III. Config: hardcoded URLs found in source Finding: "http://localhost:3000" in src/api/client.js:8 Recommendation: move to process.env.API_URL, add to .env.example### Not checked (requires runtime)- Factors I, IV, VI, VII, VIII, IX, XII Reason: not observable from static repo analysisRating: ⚠️ Partial```Ratings: ❌ Not compliant / ⚠️ Partial / ✅ Good / 🚀 Fully observable complianceSee `references/12-factor.md` for full criteria and excluded factors explanation.

Frequently asked questions