CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

codeql

Scans a codebase for security vulnerabilities using CodeQL's interprocedural data flow and taint tracking analysis. Triggers on "run codeql", "codeql scan", "codeql analysis", "build codeql database", or "find vulnerabilities with codeql". Supports "run all" (security-and-quality + security-experimental suites) and "important only" (high-precision security findings) scan modes. Also handles creating data extension models and processing CodeQL SARIF output.

Quality

83%

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

The canonical home for this skill is codeql in trailofbits/skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is well-structured and actionable for setup, discovery, and workflow selection, with executable bash snippets and a strong success-criteria checklist. Its two real weaknesses are redundancy (the Rationalizations section and triple-stated database-selection logic repeat earlier content) and the fact that the three core workflow files it delegates to are missing from the bundle.

Suggestions

Create the missing workflows/build-database.md, workflows/create-data-extensions.md, and workflows/run-analysis.md (or fix the references) — the skill's core execution steps currently point to files that do not exist in the bundle.

Consolidate "Essential Principles" and "Rationalizations to Reject" into a single section: the rationalizations restate the principles point-for-point and could be folded in as brief "reject this shortcut" notes, cutting substantial token cost.

Merge the database-selection guidance that currently appears in Database Discovery, Auto-Detection Logic, and Database Selection Prompt into one canonical section with the discovery command, metadata loop, and AskUserQuestion template.

DimensionReasoningScore

Conciseness

The body is operational rather than tutorial-style (no explanations of concepts Claude already knows), but it is noticeably duplicated: "Rationalizations to Reject" restates nearly every "Essential Principle" point-for-point (database quality, zero findings, build-mode=none, data extensions, suite filtering), and database-selection guidance appears in three separate sections (Database Discovery, Auto-Detection Logic, Database Selection Prompt). This fits "mostly efficient but includes some unnecessary explanation or could be tightened" better than the noticeably-padded anchor 2, but a tightened version could cut substantial length.

3 / 5

Actionability

Guidance in the body is executable and copy-paste ready — the output-directory resolution loop, the `find . -maxdepth 3 -name "codeql-database.yml"` discovery command, the per-database metadata extraction loop, and the version check — plus concrete decision tables and AskUserQuestion option blocks. It is not a 5 because the core pipeline steps ("build database → create data extensions → run analysis using the workflows below") delegate to workflows/build-database.md, workflows/create-data-extensions.md, and workflows/run-analysis.md, none of which exist in the bundle, leaving the actual analysis commands unspecified.

4 / 5

Workflow Clarity

The three workflows are laid out in a selection table with explicit gating ("execute it step by step without skipping phases. Each phase gates the next"), auto-detection is a condition/action table, and a Success Criteria checklist provides end-state validation including zero-finding investigation. Minor validation gaps remain — per-phase checkpoints and error-recovery loops are promised inside the three missing workflow files, so they cannot be verified here — which keeps it below the anchor-5 explicit-validation example.

4 / 5

Progressive Disclosure

Structure is good: a clear Reference Index table signals all 12 references/*.md files (all of which exist) with one-line content descriptions, links are one level deep, and overview-level content stays in SKILL.md. This is more than anchor 3 (references are clearly signaled, not buried) but short of anchor 5 because the organization gap is not minor: the three workflow files central to execution — workflows/build-database.md, workflows/create-data-extensions.md, workflows/run-analysis.md — are referenced in the Workflow Selection table, Reference Index, and body text but do not exist in the bundle.

4 / 5

Total

15

/

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: concrete capabilities, an explicit trigger clause with natural user phrasing, and a clearly bounded CodeQL niche. The only gap is that trigger terms are all tool-prefixed, missing tool-agnostic synonyms like "static analysis" or "security scan" that a user might say without naming CodeQL.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Scans a codebase for security vulnerabilities using CodeQL's interprocedural data flow and taint tracking analysis", "creating data extension models and processing CodeQL SARIF output" — plus two named scan modes ("run all" with named suites, "important only"), giving comprehensive coverage of the skill's capabilities. It is not a 4 because no meaningful action in the skill's scope is left uncovered.

5 / 5

Completeness

It explicitly answers both questions: the "what" is stated up front (scanning for vulnerabilities via data flow/taint tracking, data extension models, SARIF processing) and the "when" is an explicit "Triggers on ..." clause with concrete trigger phrases, matching the anchor-5 example pattern. Not a 4, because the when-clause is fully explicit rather than merely adequate.

5 / 5

Trigger Term Quality

Five natural trigger phrases are quoted verbatim ("run codeql", "codeql scan", "codeql analysis", "build codeql database", "find vulnerabilities with codeql") — phrases a user would naturally say. It falls short of the 5 anchor because coverage is entirely CodeQL-prefixed and misses common synonyms a user might say without naming the tool, such as "static analysis", "security scan", or "SAST".

4 / 5

Distinctiveness Conflict Risk

CodeQL is a specific named tool and every trigger phrase names it, giving a clear niche with minimal conflict risk against adjacent skills (e.g., Semgrep, which the body itself distinguishes in "When NOT to Use"). No overlap concerns arise.

5 / 5

Total

19

/

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

relative_links

Relative link issues: 3 possibly missing (workflows/build-database.md, workflows/create-data-extensions.md, workflows/run-analysis.md)

Warning

Total

15

/

16

Passed

Repository

BigSimmo/PsychSift

Path

.claude/cloud-profile/skills/codeql/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.