CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

scripts-and-automation

Choose or maintain repository Make/script workflows, builds, dependency selection, generated artifacts, and security CLI tools. Routes release work and documents local administration and standalone login commands.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/scripts-and-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, highly actionable command-selection skill: every make target and go command is given with its exact variables, side effects, scope limits, and embedded validation checks, and bundle references are real, well-signaled, and one level deep. Its main weaknesses are token weight — long inline OIDC and go-authcrunch sections duplicate what referenced files could hold, with some repeated caveats — and reference-style rather than sequenced workflow presentation.

Suggestions

Move the detailed OIDC conformance procedure (prepare/test/cleanup specifics, CONFORMANCE_RESULTS handling) into the already-referenced oidc-conformance.md, keeping only a short routing bullet in SKILL.md.

Extract the local go-authcrunch replacement/upgrade procedure into a reference file and deduplicate the repeated 'not a shortcut for focused validation' and 'do not edit the sibling' caveats.

Convert the dependency-upgrade section into a short numbered sequence with its existing checkpoints (go get -> go mod tidy -> go mod verify -> inspect diff -> record checksum) to make the workflow explicit.

DimensionReasoningScore

Conciseness

The body is mostly high-density repository-specific guidance (exact targets, side effects, scoping rules) with almost no explanation of concepts Claude already knows, but it could be tightened: the OIDC conformance bullet runs ~30 lines of detail that largely duplicates the referenced conformance doc, the local go-authcrunch section repeats caveats, and phrases like "These are CI entry points, not shortcuts for focused local validation" restate earlier guidance. It is not 4 because several sections carry detail that belongs in the already-referenced files, and not 2 because nearly every line conveys non-default repo-specific behavior.

3 / 5

Actionability

Guidance is fully executable throughout: exact invocations like `make test TEST='<selected-test-regex>' TEST_DIR='<affected-package>'` and `go test -mod=readonly -count=1 -run '<selected-test-regex>' <affected-package>`, plus two copy-paste-ready bash blocks (`go list -m -f '{{.Version}}' ...` and `go mod edit -replace ...`) with documented variables (TEST, TEST_DIR, TEST_TIMEOUT, CODEQL_LANGUAGE, CONFORMANCE_RESULTS). Each target's behavior, prerequisites, and side effects are specified, covering the common cases.

5 / 5

Workflow Clarity

Decision flows are clear and consistently patterned ("Use X for Y", focused vs. full-suite vs. CI gates, explicit routing to owning skills), and validation checkpoints appear at the risky points: "Verify the report contains every intended test; a successful empty selection does not validate a change", "Record the module checksum and verify the built command's dependency identity", "Review the diff before deciding whether to keep them", and cleanup safeguards ("refuses active runs", "only when cleanup is requested"). It is not 5 because the material is organized as a reference rather than sequenced procedures with explicit error-recovery loops, so some multi-step flows (e.g., dependency upgrade) require the reader to assemble the checkpoints themselves.

4 / 5

Progressive Disclosure

The four bundle references (caddy-authenticator.md, test-resources.md, codeql.md, local-user-commands.md) all exist, are one level deep, and are clearly signaled with what each contains ("Read [test resource controls](references/test-resources.md) for concurrency, memory, wall-time limits..."); cross-links to sibling skills serve routing rather than nesting. It is not 5 because sizable self-contained topics — the OIDC conformance workflow (~40 lines) and the local go-authcrunch replacement procedure (~60 lines) — are inlined in SKILL.md instead of split into references, leaving the overview heavier than ideal.

4 / 5

Total

16

/

20

Passed

Description

55%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description communicates a concrete, multi-part 'what' for repository automation ownership, but completely lacks a 'when' clause and omits testing/CI trigger terms even though testing dominates the skill body. It is serviceable but below the standard of the good examples, which pair capabilities with explicit trigger phrases.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to run or maintain make targets, builds, dependency upgrades, test runs, or security CLI commands in this repository."

Include natural testing/CI trigger terms ("make test", "run the tests", "CI", "test reports") since command selection for testing is the body's largest section.

Sharpen the generic verbs ("Choose or maintain", "Routes", "documents") into concrete actions like "Select make targets", "Upgrade go-authcrunch", "Issue and revoke API keys" to reduce overlap with sibling skills.

DimensionReasoningScore

Specificity

The description lists several concrete capability areas — "Make/script workflows, builds, dependency selection, generated artifacts, and security CLI tools" plus "release work", "local administration and standalone login commands" — which matches the anchor for several specific actions with minor gaps. It falls short of 5 because the verbs ("Choose or maintain", "Routes", "documents") are generic and coverage omits the testing/CI work the skill actually governs.

4 / 5

Completeness

The 'what' is clearly stated ("Choose or maintain repository Make/script workflows, builds, dependency selection, generated artifacts, and security CLI tools"), but there is no 'Use when...' clause or equivalent trigger guidance anywhere, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' is concrete and multi-part, not vague.

3 / 5

Trigger Term Quality

It includes relevant terms users would say ("Make", "script", "builds", "dependency", "release", "login commands"), but common variations are missing — most notably any testing/CI trigger ("run the tests", "make test", "CI") despite testing being the body's largest subject, plus "automation"-adjacent synonyms. This fits 'some relevant keywords but missing common variations' better than the 'a few natural terms missing' of level 4 because entire request categories are uncovered.

3 / 5

Distinctiveness Conflict Risk

The scope is somewhat specific ("repository Make/script workflows") and boundary-aware ("Routes release work" elsewhere), but "builds", "dependency selection" and "security CLI tools" overlap materially with the sibling testing-and-ci, release-and-versioning, and configuration-* skills this very skill routes to, so it could still trigger for the wrong skill. It is not 4 because the overlap is with several closely related skills, not a minor risk with one.

3 / 5

Total

13

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 18 suspicious

Warning

referenced_paths_exist

Referenced path issues: 5 possibly missing (assets/cla/signatures.json, assets/config, assets/docs/images/logo.png, assets/scripts/generate_downloads.sh, assets/scripts/update_doc_refs.sh), 4 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

greenpau/caddy-security

Path

.codex/skills/scripts-and-automation/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.