CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

preflight

Pre-PR validation — working tree status, format, lint, TypeScript check, and protected file check. Workspace-aware: detects which of backend/, frontend/, services/apps/*, services/libs/* were changed and runs only the relevant scripts. Use before submitting any PR, to check if code is ready, or to validate a branch before review.

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 preflight workflow: every check is executable, sequenced, and validated, with error-recovery guidance and a clear results report. The two weaknesses are minor — duplicated git commands across checks, and a dangling reference to commit-workflow.md that is not present in the bundle.

Suggestions

Deduplicate the repeated commands: Checks 1, 5, and 7 all restate `git diff --name-only origin/main...HEAD` (and Checks 0/6 repeat the `git log --format` command) — reference the earlier check's command instead.

Fix the dangling reference: `commit-workflow.md` is cited in Check 6 but no such file exists in the bundle — either add it under references/ or inline the needed commit conventions.

Consider moving the protected-files list (Check 5) to a references/ file if it grows, keeping SKILL.md as the overview of which paths are protected and why.

DimensionReasoningScore

Conciseness

Lean overall — no explanations of concepts Claude already knows, and repo-specific rationale ("Fetch first — every check below diffs against origin/main", fail-fast matching the CI job) earns its place. Falls short of anchor 5 because `git diff --name-only origin/main...HEAD` is repeated verbatim in Checks 1, 5, and 7, and the `git log --format` command appears twice — minor duplication that could be trimmed.

4 / 5

Actionability

Fully executable throughout: exact bash commands (`git fetch origin main`, `./scripts/cli lint-changed`, `cd frontend && pnpm run lint`), an exact protected-file path list, concrete fix steps ("fix with `pnpm format` from the repo root then `git add -p`"), and a copy-paste-ready report template. Anchor 5 match — the commands cover the common cases as-is.

5 / 5

Workflow Clarity

Checks 0–7 are clearly sequenced with per-step evaluation criteria, explicit checkpoints ("Resolve any issues before proceeding"), a documented feedback loop (fail-fast means "fix and re-run to see the next check"), and a final checklist-style report. This matches anchor 5: explicit validation steps, error-recovery loops, and a checklist for a complex process.

5 / 5

Progressive Disclosure

Good structure with content appropriately placed in a single well-sectioned file — nothing is inlined that clearly belongs in a separate file, so this is not anchor 3. However, the body's one reference ("per `commit-workflow.md`") points to a file that does not exist in the bundle (no references/ directory), a minor navigation gap that keeps it below anchor 5.

4 / 5

Total

18

/

20

Passed

Description

88%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 enumerates the skill's concrete checks, explains the workspace-aware scoping behavior, and provides an explicit 'Use when...' clause with natural trigger phrases. Third-person voice is used consistently. Only minor gaps in trigger-synonym coverage and slight overlap risk with generic lint/CI skills keep it from full marks.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — "working tree status, format, lint, TypeScript check, and protected file check" plus workspace detection — giving comprehensive coverage of the skill's checks. It exceeds anchor 4 ("minor gaps in coverage") because every capability of the skill is enumerated, not just several.

5 / 5

Completeness

Explicitly answers both: what ("Pre-PR validation — working tree status, format, lint, TypeScript check, and protected file check") and when ("Use before submitting any PR, to check if code is ready, or to validate a branch before review") with concrete trigger phrases. Anchor 5 is an exact match; anchor 4 would require a less explicit 'when' clause.

5 / 5

Trigger Term Quality

Good natural trigger phrases: "before submitting any PR", "check if code is ready", "validate a branch before review" — phrasings a user would actually say. Falls short of anchor 5 because common variations like "run the checks", "ready to merge", or "pre-push check" are absent.

4 / 5

Distinctiveness Conflict Risk

"Pre-PR validation" carves a clear niche with distinct triggers, but the description overlaps slightly with generic lint/format/CI-check skills that could also fire on "check if code is ready". Mostly distinct with minor overlap risk against closely related skills — anchor 4, not 5, which demands minimal conflict risk.

4 / 5

Total

18

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

14

/

16

Passed

Repository

linuxfoundation/crowd.dev

Path

.claude/skills/preflight/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.