CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sarif-parsing

Parse, analyze, and process SARIF (Static Analysis Results Interchange Format) files. Use when reading security scan results, aggregating findings from multiple tools, deduplicating alerts, extracting specific vulnerabilities, or integrating SARIF data into CI/CD pipelines.

Quality

77%

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 ./.claude/cloud-profile/skills/sarif-parsing/SKILL.md

The canonical home for this skill is sarif-parsing in trailofbits/skills

SKILL.md
Quality
Evals
Security

Quality

Content

53%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 rich in concrete, executable code covering jq, Python, and CI/CD integration, but it reads as a strategy buffet rather than a guided workflow, repeats content it claims to externalize, and its two resource references point to files that don't exist in the bundle. Fixing the broken references and consolidating the duplicated helper code would raise both organization scores.

Suggestions

Create the referenced resources/jq-queries.md and resources/sarif_helpers.py (or remove the "Skill Resources" section) — both links are currently dead, and the helper code they promise is duplicated inline.

Replace the parallel "Strategy 1–5" sections with a sequenced decision workflow (validate schema → choose tool → parse → filter/dedup → output) with explicit validation checkpoints, especially for the batch aggregation path.

Trim conceptual explanation such as the "Why Fingerprinting Matters" rhetorical questions and the unused .NET/JS/Go tool rows to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete code, but the "Why Fingerprinting Matters" section explains concepts via rhetorical questions ("Is this a new finding or did we see it before?") that Claude doesn't need, and the dedup/normalize/fingerprint code is fully inlined even though the "Skill Resources" section claims it lives in a separate helper file. The tool table's .NET/JS/Go rows also add breadth without use-case grounding.

3 / 5

Actionability

Abundant executable guidance — copy-paste jq one-liners, complete Python functions, sarif-tools CLI commands, and GitHub Actions YAML. Minor gaps keep it below 5: `check_for_regressions` calls an undefined `get_fingerprint`, and the sarif-tools report API example is unverified, so not every block is self-contained.

4 / 5

Workflow Clarity

The five "Strategies" form a parallel menu rather than a sequenced process; the tool-selection table hints at routing but no ordered workflow (e.g., validate → parse → filter → dedup → report) exists. Validation appears only as Key Principle 1 and a pitfalls subsection, with no validate→fix→retry checkpoint wired into the batch aggregation/dedup workflows, so checkpoints are implicit rather than explicit.

3 / 5

Progressive Disclosure

The "Skill Resources" section points to {baseDir}/resources/jq-queries.md and {baseDir}/resources/sarif_helpers.py, but no resources directory exists in the bundle — both references are dead. Meanwhile the content those files would hold (dedup, path normalization, fingerprinting) is duplicated inline, so material that clearly belongs in separate files is inlined and navigation to the referenced files is impossible.

2 / 5

Total

12

/

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 capability list, explicit trigger phrases, and a clear negative boundary against neighboring skills. The only weakness is minor missing natural terms such as the ".sarif" extension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Parses and processes SARIF files", "Handles filtering, deduplication, format conversion, and CI/CD integration" — giving comprehensive coverage of the domain's capabilities. It goes beyond the 4-anchor example in both breadth and concreteness, with no noticeable coverage gaps.

5 / 5

Completeness

Clearly answers "what" (parses, filters, deduplicates, converts, integrates into CI/CD) and "when" (explicit "Triggers on..." clause with concrete phrases), plus a negative boundary ("Does NOT run scans"). This matches the 5 anchor, which requires both what and when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Five explicit natural trigger phrases ("parse sarif", "read scan results", "aggregate findings", "deduplicate alerts", "process sarif output") with multiple phrasings of the core term. A few natural terms are still missing — the ".sarif" file extension and variants like "static analysis results" or "scan output" — so it falls just below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (SARIF post-processing) and explicitly disambiguates from adjacent skills: "Does NOT run scans — use the Semgrep or CodeQL skills for that". The tool-specific triggers (CodeQL, Semgrep, SARIF) minimize conflict risk with generic scanning or code-analysis skills.

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: 2 possibly missing ({baseDir}/resources/jq-queries.md, {baseDir}/resources/sarif_helpers.py), 2 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

BigSimmo/PsychSift

Path

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