12 Factor Apps Analysis

perform 12-Factor App compliance analysis on a codebase

Security Scan

The skill's requested actions and requirements match its stated purpose (analyzing a codebase for 12‑Factor compliance); it is an instruction-only skill that will read the target repository and produce findings, which is consistent with its description.

Purpose & Capability

Name and description (12‑Factor compliance analysis) match the instructions: the skill reads a codebase, runs searches, collects file:line evidence, and produces recommendations. There are no unrelated environment variables, binaries, or install steps requested.

Instruction Scope

The SKILL.md explicitly instructs the agent to examine the target path (default: current working directory) and produce file:line evidence using grep/search patterns. That behavior is appropriate for the stated purpose, but it means the skill will access all files in the provided directory (including any secrets or config files present). The skill also refers to another skill named `12-factor-apps` for search patterns; if that helper skill is missing or untrusted, results/behavior may be incomplete or depend on third-party logic.

Install Mechanism

Instruction-only; no install spec, no downloads, and no code files. This is the lowest-risk install profile and matches the skill's stated purpose.

Credentials

The skill declares no required environment variables, credentials, or config paths. Its request to read the repository is proportional to the analysis task.

Persistence & Privilege

The skill is not marked always:true and model invocation is disabled (disable-model-invocation: true), so it cannot be invoked autonomously; it does not request persistent system presence or modify other skills' configurations.

Assessment

This skill appears coherent and appropriate for auditing a repository for 12‑Factor compliance. Before running it, point it at the correct project directory (don't point it at your whole home or root filesystem), and be aware it will read all files under that path — any secrets or private config in the repository may be included in the output. Also confirm you trust the referenced helper skill `12-factor-apps` (if present) because the SKILL.md delegates search patterns to it; if that helper isn't available, results may be incomplete. If you are analyzing sensitive code, run the skill in an isolated environment or remove/rotate secrets before analysis.

12-Factor App Compliance Analysis

You are performing a comprehensive compliance analysis against the 12-Factor App methodology for building SaaS applications.

Use the 12-factor-apps skill to guide this analysis.

Target Codebase

Path: $ARGUMENTS (default: current working directory)

Analysis Scope

Evaluate all 12 factors:

1. Codebase - One codebase tracked in revision control, many deploys
2. Dependencies - Explicitly declare and isolate dependencies
3. Config - Store config in the environment
4. Backing Services - Treat backing services as attached resources
5. Build, Release, Run - Strictly separate build and run stages
6. Processes - Execute the app as one or more stateless processes
7. Port Binding - Export services via port binding
8. Concurrency - Scale out via the process model
9. Disposability - Maximize robustness with fast startup and graceful shutdown
10. Dev/Prod Parity - Keep development, staging, and production as similar as possible
11. Logs - Treat logs as event streams
12. Admin Processes - Run admin/management tasks as one-off processes

Workflow

1. Use the skill - Read the 12-factor-apps skill for search patterns
2. Run searches - Use grep patterns from the skill for each factor
3. Evaluate compliance - Strong/Partial/Weak per factor
4. Document evidence - File:line references for findings
5. Identify gaps - What's missing vs. 12-Factor ideal
6. Provide recommendations - Actionable improvements

Output Format

Executive Summary

Factor	Status	Key Finding
I. Codebase	Strong/Partial/Weak	[Summary]
II. Dependencies	Strong/Partial/Weak	[Summary]
...	...	...

Overall: X Strong, Y Partial, Z Weak

Detailed Findings

For each factor with gaps:

• Current State: What exists
• Evidence: File:line references
• Gap: What's missing
• Recommendation: How to improve

Priority Recommendations

1. High Priority - Critical gaps affecting scalability/reliability
2. Medium Priority - Improvements for better compliance
3. Low Priority - Nice-to-have optimizations

Rules

• Use the skill's search patterns systematically
• Provide file:line evidence for all findings
• Be honest about compliance levels (don't inflate)
• Focus on actionable recommendations
• Reference the official 12-Factor App methodology