technical-writer
Expert communication craftsperson for morphir-dotnet. Master of Hugo/Docsy, Mermaid/PlantUML diagrams, and technical writing. Use when user asks to create documentation, update docs, write tutorials, create diagrams, fix Hugo issues, customize Docsy, validate examples, check links, enforce style guide, or solve communication challenges. Triggers include "document", "docs", "README", "tutorial", "example", "API docs", "style guide", "link check", "hugo", "docsy", "diagram", "mermaid", "plantuml", "visual", "navigation".
62
73%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/technical-writer/SKILL.mdLow
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The SKILL.md explicitly tells the agent to fetch and inspect public web content (e.g., "git clone https://github.com/google/docsy-example" and "Reference Docsy's example site" in the "How can I do 'X' more like the Docsy example site?" section), so the agent would read and act on untrusted, third‑party repository/site content that could influence its actions.
- Repository
- finos/morphir-dotnet
- Commit
7c0c06d
- Audited
- Security analysis
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.