Skip to content
Back to skills

Speckit.Checker

ASecurity

Static Analysis Aggregator - Run applicable static, configuration, container, security, and stack checks with evidence.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 24, 2026
ai-agentssqlrailsdockersecurityperformancedocumentation

Security analysis

A100/100

Scanned September 24, 2026

npx -y skills add wedabro/bro-skills --skill speckit.checker --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Speckit.Checker?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Speckit.Checker
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/wedabro-speckit-checker/badge)](https://www.skillsdirectory.com/skills/wedabro-speckit-checker)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: speckit.checker
description: Static Analysis Aggregator - Run applicable static, configuration, container, security, and stack checks with evidence.
---

## Mission
Detect actionable code, configuration, security, and performance risks using checks supported by the actual project.

## Inputs and Outputs
- Read source, manifests, constitution, project config, Docker files, and documented commands.
- Write `.agents/memory/checker-report.md` with command, scope, timestamp, findings, and N/A reasons.

## Protocol
1. Discover language, package manager, framework, services, containerization, and available formatter/type/lint/test/build commands.
2. Build an applicability matrix. Run every applicable check; mark unavailable checks N/A with reason, never PASS.
3. Run compile/type/lint and configured tests in Docker when required. Capture exit code and bounded output.
4. Validate Compose config, Docker COPY paths, non-root runtime, health checks, ENV ports, dependency lockfiles, and production mounts when applicable.
5. Scan tracked source for secrets, unsafe URLs, injection sinks, unsafe HTML/eval, SQL concatenation, and dependency risks; redact values and exclude generated/vendor paths.
6. Apply stack-specific checks only after detection and report file plus line for each finding. Classify Critical/High/Medium/Low/Info.

## Completion Gate
The report names every applicable check, evidence command, result, and remaining limitation. Any Critical finding yields FAIL.

## Guard Rails
Read-only. Do not edit code or hide failures. Do not flag intentional documentation URLs as secrets without evidence.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.