CD authentication
How auth works in agent-native apps. Use when wiring login/signup, configuring auth modes, setting up organizations, protecting routes, or debugging session issues.
How auth works in agent-native apps.
As a process D 45/100 · Unfinished process — References files that are not bundled: /docs/cross-app-sso, scripts/dev-session.ts, scripts/guard-no-localhost-fallback.mjs
IntegrationAI and agentsSoftware developmenttype and topics are labelled automatically from the skill text
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 7283 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: /docs/cross-app-sso - warning
missing-refreference to a missing file: scripts/dev-session.ts - warning
missing-refreference to a missing file: scripts/guard-no-localhost-fallback.mjs - note
frontmatter-keyunknown frontmatter key "scope" - note
edit-residuethe text marks something as outdated (lines 100, 108, 237, 380): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 45/100
Will not run. References files that are not bundled: /docs/cross-app-sso, scripts/dev-session.ts, scripts/guard-no-localhost-fallback.mjs
- 0Tools and files. 3 referenced file(s) missing: /docs/cross-app-sso, scripts/dev-session.ts, scripts/guard-no-localhost-fallback.mjs
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 23 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 70Execution cost. Instruction body is 7283 tokens
- 85Steps. 25 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (7 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 164: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.