CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gha-security-review

Find exploitable vulnerabilities in GitHub Actions workflows. Every finding MUST include a concrete exploitation scenario — if you can't build the attack, don't report it.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/gha-security-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

A well-structured, evidence-driven review methodology with strong validation discipline and a clear report format. The main weaknesses are the shallow treatment of the last three vulnerability classes and minor conciseness leaks such as repeating the description in the body.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — tables carry the checklists and it never explains GitHub Actions basics — but the frontmatter description is repeated verbatim in the body and Checks 6–8 are padded-thin one-liners, so it sits at 'minor instances that could be trimmed' rather than fully lean.

4 / 5

Actionability

Checks 1–5 give exact, executable patterns (e.g. 'actions/checkout with ref: pointing to PR head', mapping every ${{ }} expression in run: blocks, author_association checks) and the report template is concrete, but Checks 6–8 are vague single questions ('Are third-party actions securely pinned?') with minor gaps.

4 / 5

Workflow Clarity

A clear four-step sequence (classify triggers → check vulnerability classes → validate before reporting → report findings) with an explicit validation checklist in Step 3 and a feedback loop ('If any link is broken, mark MEDIUM (needs verification) or drop the finding'), matching the anchor with explicit validation steps and error-recovery loops. The destructive/batch cap does not apply since this is a read-only review skill.

5 / 5

Progressive Disclosure

No bundle files exist and the body explicitly notes the adaptation is self-contained; sections are well-organized and the content is a cohesive single-file checklist with minor organization gaps (e.g. the Safe Patterns table sits between Step 2 and Step 3, slightly breaking the numbered flow).

4 / 5

Total

17

/

20

Passed

Description

57%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 is clear, appropriately concise, and occupies a distinct niche, but it omits any 'when to use' trigger guidance and only names a single capability. Adding an explicit use-when clause with natural trigger phrases would substantially improve it.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when reviewing GitHub Actions workflows, .github/workflows/*.yml files, or CI/CD pipeline security.'

Include natural trigger synonyms users would actually say — 'security review', 'security audit', 'CI/CD pipeline security', 'workflow files' — to improve trigger-term coverage.

Optionally enumerate one or two more concrete actions (e.g. 'trace attack paths from fork PRs, issue comments, and expression injection') to broaden capability coverage.

DimensionReasoningScore

Specificity

The description names the domain and one concrete action — "Find exploitable vulnerabilities in GitHub Actions workflows" — but does not list several specific actions, matching the '1-2 concrete actions, not comprehensive' anchor rather than the level-4 'several specific actions' anchor.

3 / 5

Completeness

The 'what' is clear, but there is no 'Use when...' clause or equivalent trigger guidance — the second sentence ("Every finding MUST include a concrete exploitation scenario") is a reporting constraint, not usage timing, so completeness is capped at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

It includes relevant keywords ("GitHub Actions", "workflows", "exploitable vulnerabilities", "exploitation scenario") but misses common natural variations a user might say, such as "security review", "security audit", "CI/CD pipeline", or ".yml", fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

"GitHub Actions workflows" is a clear, narrow niche with distinct triggers and minimal conflict risk against generic security or code-review skills, matching the 'clear niche with distinct triggers' anchor.

5 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/skills/gha-security-review/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.