CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/codeql-queries

Use when a GitHub-hosted repo needs deep semantic static analysis (SAST) beyond pattern matching, such as cross-file taint and data flow: codeql database create and analyze per language, query packs, SARIF upload to code scanning, and suppressions.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

86%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, highly actionable skill: executable commands at every step, a clean spine-plus-reference split, and an unusually strong anti-patterns/limitations treatment. The gaps are minor — slight over-explanation in the Overview and no explicit validation checkpoint for the silent empty-database failure mode the skill itself warns about.

Suggestions

Trim the Overview's explanation of what CodeQL and SARIF are (Claude already knows); keep only the database-then-query framing and the cross-file taint example that justifies when to use it.

Add an explicit validation checkpoint after Step 2, e.g. a smoke query or database inspection, since the anti-patterns table notes that a missed --command produces a silently empty database.

Cut the redundant Step 4 prose ('persistent + auditable + show in the audit log') that restates the dismissal row in the triage table.

DimensionReasoningScore

Conciseness

The body is mostly lean — tables, terse steps, copy-paste commands — but the Overview re-explains what CodeQL and SARIF are ("CodeQL is GitHub's semantic-analysis SAST: build a database... emit SARIF"), and Step 4 prose ("persistent + auditable + show in the audit log") repeats the table row above it. This is the 'efficient with minor instances of over-explanation' anchor rather than the fully lean 5.

4 / 5

Actionability

Every step ships executable, copy-paste-ready commands: the curl/unzip install with PATH export, `codeql --version` verification, per-language `database create` invocations for both interpreted and compiled builds, the `database analyze` SARIF command, a runnable jq SARIF filter, a complete inline suppression template, and `--threads`/`--ram` flags. Coverage of the common cases is complete, matching the 5 anchor.

5 / 5

Workflow Clarity

Steps 1–5 are clearly sequenced and include checkpoints (`codeql --version` verify, quarterly dismissed-alerts review), landing on the 'clear sequence with most checkpoints' anchor. It is not 5 because the skill itself documents that a missing `--command` yields a silently empty database, yet no explicit post-create validation (e.g., a smoke query or database check) is built into the workflow.

4 / 5

Progressive Disclosure

SKILL.md is a concise spine, and Step 3 points to a single, clearly-signaled, one-level-deep reference (references/codeql-reference.md, verified to exist) while explicitly enumerating what it contains (pack list, suites, custom .ql example, CI integration). The reference file does not nest further, matching the 5 anchor for well-signaled one-level-deep references.

5 / 5

Total

18

/

20

Passed

Description

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

A strong description: it states an explicit, well-scoped trigger condition and enumerates concrete capabilities in third-person imperative style. The only weakness is modest keyword coverage — a few natural synonyms (e.g., "security scan", "vulnerability") that users might say are missing.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions spanning the whole workflow — "codeql database create and analyze per language, query packs, SARIF upload to code scanning, and suppressions" — which matches the comprehensive-coverage anchor. It is not a 4 because the action list covers create, analyze, report, and suppress with no significant gaps.

5 / 5

Completeness

Both halves are explicit: "Use when a GitHub-hosted repo needs deep semantic static analysis (SAST) beyond pattern matching, such as cross-file taint and data flow" answers when, and the colon-delimited capability list answers what. This clearly matches the anchor requiring explicit what and when with concrete triggers, not the 4 anchor where 'when' is only adequate.

5 / 5

Trigger Term Quality

Natural domain terms are present ("static analysis", "SAST", "cross-file taint", "data flow", "code scanning", "SARIF", "CodeQL"), giving good keyword coverage. It falls short of 5 because common user phrasings like "security scan" or "vulnerability scan" are absent.

4 / 5

Distinctiveness Conflict Risk

"GitHub-hosted repo", "beyond pattern matching", and CodeQL-specific terms (SARIF, code scanning, query packs) carve a clear niche with minimal conflict risk against sibling SAST skills. The "beyond pattern matching" qualifier explicitly excludes pattern-matcher tools, keeping it above the 4 anchor's 'minor overlap risk'.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page