Skills doc-writer Audit History
📦

Audit History

doc-writer - 6 audits

Version comparison

Capability and finding changes across audited versions, newest first.

VersionDateResultReview itemsChange vs previous
v6 LatestJul 4, 2026, 01:29 PM No confirmed findings0No capability change
v5 Jul 4, 2026, 01:29 PM No confirmed findings0External commands Filesystem access
v4 Jun 27, 2026, 12:33 PM No confirmed findings1Filesystem access External commands
v3 Jan 16, 2026, 12:09 PM No confirmed findings0No capability change
v2 Jan 16, 2026, 12:09 PM No confirmed findings0External commands
v1 Jan 10, 2026, 08:50 AM No confirmed findings0Baseline

Jul 4, 2026, 01:29 PM

The static findings are false positives caused by Markdown inline code around file paths and naming examples in SKILL.md. I found no prompt injection, data exfiltration intent, or unsafe command construction in the reviewed skill instructions.

1
Files scanned
26
Lines analyzed
1
Review items
0
False positives ignored
Audited by: codex

Jul 4, 2026, 01:29 PM

The static findings are false positives caused by Markdown inline code around file paths and naming examples in SKILL.md. I found no prompt injection, data exfiltration intent, or unsafe command construction in the reviewed skill instructions.

1
Files scanned
26
Lines analyzed
1
Review items
0
False positives ignored
Audited by: codex

Jun 27, 2026, 12:33 PM

The static analyzer reported shell execution and weak cryptography patterns, but the reviewed lines are Markdown code spans and prose, not executable code. The skill has a low residual risk because it instructs the assistant to read and write repository documentation files and optionally run configured validators.

1
Files scanned
26
Lines analyzed
2
Review items
1
False positives ignored
Capability review items (1)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Low
Filesystem Documentation Changes
The skill asks the assistant to create or update Markdown files in repository documentation directories. This is expected behavior for a documentation skill, but users should review generated files before commit.
The instructions explicitly require generating or refreshing documentation files and saving them under documentation directories. This is a clear filesystem modification behavior, but it matches the declared purpose.
Static false positives ignored (1)

These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.

Low
Static Analyzer False Positives
The reported shell backtick and weak cryptography findings are not executable code. The flagged text consists of Markdown code spans, file names, directory names, and a plain description.
The reviewed file is a short Markdown instruction file with no Ruby, shell script, or cryptographic implementation. The flagged backticks are Markdown formatting, not command substitution.

Risk Factors

Audited by: codex

Jan 16, 2026, 12:09 PM

This is a pure documentation skill with no executable code. The static analyzer flagged 20 false positives due to pattern matching on file paths and URL strings in markdown and JSON. No network calls, file system operations, external commands, or cryptographic operations exist in these files. Only plain text documentation and metadata.

2
Files scanned
206
Lines analyzed
1
Review items
0
False positives ignored
Audited by: claude

Jan 16, 2026, 12:09 PM

This is a pure documentation skill with no executable code. The static analyzer flagged 20 false positives due to pattern matching on file paths and URL strings in markdown and JSON. No network calls, file system operations, external commands, or cryptographic operations exist in these files. Only plain text documentation and metadata.

2
Files scanned
206
Lines analyzed
1
Review items
0
False positives ignored
Audited by: claude

Jan 10, 2026, 08:50 AM

Pure prompt-based skill containing only documentation guidelines. No executable code, no network calls, no file system access, no external commands. This is a configuration file that instructs an AI how to write documentation using repository templates and context.

1
Files scanned
26
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were recorded for this completed audit.
Audited by: claude