CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fastapi-repo-security-preflight

Automated security scanner for FastAPI repos to detect secrets, SQLi, insecure CORS, and unverified webhooks. Use when: Identify hardcoded credentials and committed .env files before deployment; Catch SQL injection vulnerabilities in raw database queries; Enforce signature verification on all FastAPI webhook endpoints.

Quality

63%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/fastapi-repo-security-preflight/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

15%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 reads as a product landing page rather than an operational skill: it markets the scanner, duplicates itself in an FAQ, and contains no instructions, commands, or scripts for actually running a scan — which the body itself admits are absent from the folder. Only the section organization keeps progressive disclosure from scoring lower.

Suggestions

Replace the capability bullets and example output with an executable workflow: the actual scan command(s) or inline script, severity levels, and explicit pass/fail criteria for the CI gate.

Delete the FAQ section (it duplicates 'What it does' and 'Why this beats prompting it yourself') and the marketing/purchase sections and footer links, which add no operational value.

Add a numbered scan procedure with a validation checkpoint (e.g., re-run scanner after fixes, verify findings are resolved before passing the gate) so the multi-step audit process is sequenced.

DimensionReasoningScore

Conciseness

The body is noticeably padded: the six-question FAQ largely restates 'What it does' and 'Why this beats prompting it yourself', and sections like 'What is included in the purchase' plus footer catalog links are marketing content. It avoids lecturing on concepts Claude already knows, keeping it above a 1.

2 / 5

Actionability

The body only describes capabilities ('Scans code for hardcoded API keys... using AST analysis') with a sample request/result, and provides no commands, code, or invocation steps — it even states the scanner scripts 'are not in this folder'. This matches the 'only describes rather than instructs' anchor.

1 / 5

Workflow Clarity

No scan procedure or step sequence appears anywhere in the body; there is no ordering of actions and no validation or pass/fail logic beyond a canned example output, matching the 'steps missing or incoherent' anchor.

1 / 5

Progressive Disclosure

Sections are clearly headed and no broken nested references exist, but roughly 40% of the body (FAQ, purchase/marketing content) is redundant inline material that belongs in a separate file or should be removed, fitting 'some structure but could be better organized'.

3 / 5

Total

7

/

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: specific, third-person, with an explicit 'Use when:' clause carrying concrete trigger phrases. Its only weakness is slightly incomplete natural-keyword coverage (missing 'API keys', 'tokens', 'security audit' style phrasing).

DimensionReasoningScore

Specificity

The description lists multiple concrete detection actions — 'detect secrets, SQLi, insecure CORS, and unverified webhooks' — which is comprehensive coverage for the FastAPI security-scanning domain, matching the top anchor rather than the 'minor gaps' of a 4.

5 / 5

Completeness

It clearly answers 'what' ('Automated security scanner for FastAPI repos to detect...') and 'when' with an explicit 'Use when:' clause containing three concrete trigger phrases, exactly matching the top anchor; it is not a 4 because the 'when' is fully explicit rather than merely adequate.

5 / 5

Trigger Term Quality

Good keyword coverage including natural phrases like 'hardcoded credentials', 'committed .env files', 'SQL injection', 'raw database queries', and 'signature verification', but common user terms such as 'API keys', 'tokens', or 'security audit' are missing, so it falls short of the comprehensive-synonyms anchor for 5.

4 / 5

Distinctiveness Conflict Risk

The 'FastAPI repos' scope combined with security-specific triggers (SQLi, CORS, webhook signatures) carves out a clear niche with minimal conflict risk against general code-review or language-agnostic secret-scanning skills.

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.

Repository

NexaiGuy/nex-ai-skills

Path

skills/fastapi-repo-security-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.