secure-workflow-guide
No security findings. Scanned 1 time, most recently 2026-02-06.
Second scanner: NVIDIA SkillSpector
Independent static run, no language model, over the same files as the Cisco scan above. How the two scanners compare across the whole corpus: Two scanners, one corpus.
What this skill does
Guides through Trail of Bits' 5-step secure development workflow. Runs Slither scans, checks special features (upgradeability/ERC conformance/token integration), generates visual security diagrams, helps document security properties for fuzzing/verification, and reviews manual security areas.
- Package
- 3 files, 17 KB
- SKILL.md
- 877 words, 12+ sections
- Code
- None. Instructions only.
SKILL.md covers: Secure Workflow Guide · Purpose · The 5-Step Workflow · Step 1: Check for Known Security Issues · Step 2: Check Special Features · Step 3: Visual Security Inspection · Step 4: Document Security Properties · Step 5: Manual Review Areas · How I Work · Rationalizations (Do Not Skip) · Example Output · What You'll Get
Findings
No findings. SAFE
What is in the package
| File | Kind | Size |
|---|---|---|
SKILL.md | doc | 6.4 KB |
resources/EXAMPLE_REPORT.md | doc | 7.2 KB |
resources/WORKFLOW_STEPS.md | doc | 3.0 KB |
External hosts referenced
meetings.hubspot.com
Hostnames that appear in the skill's files. Referencing a host is not a finding; compare against the findings above and the skill's stated purpose.
Package contents recorded 2026-10-22 at commit a50696e20581. The scan above ran against the version current at scan time; the two can differ if the skill has since been updated.
What we checked
- Static analyzer. Pattern rules over SKILL.md and bundled files: known-bad commands, exfiltration URLs, secrets, obfuscation.
- Behavioral analyzer. Checks what the skill asks the agent to do against what its description claims it does.
- Llm analyzer. A language model reads the skill and reports intent-level issues the rules cannot express.
- Trigger analyzer. Looks for instructions that fire on conditions the user did not ask for.
- Meta analyzer. A second model pass that validates, deduplicates and re-scores the other analyzers' findings.
What we did not check
- Runtime behaviour. The skill was not executed; findings come from reading its files.
- Anything fetched at install or run time, including remote scripts, package dependencies, and URLs the skill tells the agent to open.
- Content the analyzers cannot read: images, binaries, and some non-English text.
- Known scanner bypass classes. See the methodology and limitations page.
Sources
- Repository: https://github.com/trailofbits/skills
- Raw scan result: plugins-building-secure-contracts-skills-secure-workflow-guide-scan.json
- Badge for your README:
- Request a re-scan