Earliest supported layer
Rules distinguish availability, discovery, parsing, configuration, dependency, connection, authentication, registration, exposure, activation, authorization, execution, and persistence.
Codex capability diagnosis
Find the first failing capability layer
Use a small evidence excerpt. The result separates discovery, parsing, configuration, connection, authentication, exposure, activation, authorization, execution, and persistence.
Local redaction. Save only by choice.
Diagnosis workspace
Not checkedEvidence in.
One useful next step.
Your result appears here after you review and submit the sanitized evidence.
- First supported boundary
- Waiting for evidence
- Next check
- Not selected yet
- Private report
- Not created
Worked example — not your diagnosis Parsing A compact output computed by the current deterministic ruleset. PARSED
Example evidence
The Codex skill was discovered, but the loader reports: invalid frontmatter YAML at line 4. The skill is never exposed in a new session.
Result
Parsing · PARSED
The earliest supported failure is parsing: the capability was found, but its definition could not be read as a valid manifest, schema, or frontmatter document.
Why this boundary
The supplied evidence explicitly names a parse/schema failure, so connection, activation, and execution are downstream and not yet reached.
Next safe check
Inspect only the exact parser field or line
Turn a broad 'not loading' symptom into one structural correction without rewriting the whole capability definition.
Method and limits
A capability chain, not an AI guess
- Redacted on this device
- Inspectable deterministic ruleset · 15 checkpoints
- Saved only when you choose
Deterministic rules over your redacted evidence. What the tool cannot support, it declines to claim.
Evidence before verdict
A rule must meet a deterministic threshold. Conflicting or incomplete evidence becomes partial or unknown; it is not converted into a confident root cause.
No unknown execution
The site does not install capabilities, execute packages, contact private endpoints, edit configuration, or ask for credentials.
Private by explicit choice
A diagnosis is stateless by default. Saved reports use random URLs, expire after seven days, can be deleted immediately, and are excluded from indexing.