technical-blog-writing
Verdict safe, but 1 finding (1 info), mainly policy violation. Most recent scan 2026-10-22.
Byte-identical copies of this skill are also published by magentosh, qu-skills. Same SKILL.md, same files; each copy is scanned separately so divergence shows up here.
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
Technical blog post writing with structure, code examples, and developer audience conventions. Covers post types, code formatting, explanation depth, and developer-specific engagement patterns. Use for: engineering blogs, dev tutorials, technical writing, developer content, documentation posts. Triggers: technical blog, dev blog, engineering blog, technical writing, developer tutorial, tech post, code tutorial, programming blog, developer content, technical article, engineering post, coding tutorial, technical content
- Package
- 1 file, 12 KB
- SKILL.md
- 1510 words, 12+ sections
- Code
- None. Instructions only.
- Allowed tools
Bash(belt*)
SKILL.md covers: Technical Blog Writing · Quick Start · Research topic depth · Generate header image · Post Types · 1. Tutorial / How-To · 2. Deep Dive / Explainer · 3. Postmortem / Incident Report · 4. Benchmark / Comparison · 5. Architecture / System Design · Writing Rules for Developers · Voice and Tone
Findings
INFO Skill does not specify a license Policy Violationstatic
Skill manifest does not include a 'license' field. Specifying a license helps users understand usage terms.
SKILL.md
What is in the package
| File | Kind | Size |
|---|---|---|
SKILL.md | doc | 12 KB |
External hosts referenced
inference.sh raw.githubusercontent.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 becc25649700. 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.
- Bytecode analyzer.
- Pipeline analyzer.
- Correlation analyzer.
- Behavioral analyzer. Checks what the skill asks the agent to do against what its description claims it does.
- Trigger analyzer. Looks for instructions that fire on conditions the user did not ask for.
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/101-skills/superpowers
- Raw scan result: 101-skills-superpowers-guides-writing-technical-blog-writing-scan.json
- Badge for your README:
- Request a re-scan