SKILLEMALL.ai
GitHub ↗ RU Sign in

CD app-auth

This skill should be used when the user asks to "standardize app authentication", "share login across web, mobile and TV", "reuse the Google login flow", "simplify signup", "fix password recovery", or "fix popup-blocked login". Use shared account/session contracts, email and Google web adapters, and an optional auth panel. Native and TV flows are integration contracts awaiting device validation.

fcakyon/claude-codex-settings Agent Skills author: fcakyon 9 files body ≈ 849 tokens Open the sourcegithub.com↗ analyzed 7 h ago

This skill should be used when the user asks to "standardize app authentication", "share login across web, mobile and TV", "reuse the Google login flow"…

As a process D 44/100 · Unfinished process — References files that are not bundled: assets/google-sign-in.css, assets/auth-panel.css, assets/email-auth.css

ReferenceSoftware developmentInfrastructureAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
73
Run on models
none yet
Process rating
D
44/100
Unfinished process
References files that are not bundled: assets/google-sign-in.css, assets/auth-panel.css, assets/email-auth.css
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. 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: 9. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: assets/google-sign-in.css
  • warning missing-ref reference to a missing file: assets/auth-panel.css
  • warning missing-ref reference to a missing file: assets/email-auth.css
  • warning missing-ref reference to a missing file: ../email-design/SKILL.md

Process rating: all ten parameters 44/100

Will not run. References files that are not bundled: assets/google-sign-in.css, assets/auth-panel.css, assets/email-auth.css
  • 0Tools and files. 4 referenced file(s) missing: assets/google-sign-in.css, assets/auth-panel.css, assets/email-auth.css
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 3 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 7 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 849 tokens

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

  • +4Description does not say when NOT to use the skill (false activations)
  • +4Structure: 2 headings, hard to scan
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 6 example trigger phrases
  • +3Description length 398: enough signal without eating the budget
  • +3Step-by-step instructions: 7 items
  • +4Reference files are cited in the instructions (5 of 5)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.