speckit-implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md
55
63%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Critical
Do not install without reviewing
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/speckit-implement/SKILL.mdSecurity
2 findings: 1 critical severity, 1 high severity. Installing this skill is not recommended: please review these findings carefully if you do intend to do so.
E006: Malicious code pattern detected in skill scripts.
What this means
Detected high-risk code patterns in the skill content — including its prompts, tool definitions, and resources — such as data exfiltration, backdoors, remote code execution, credential theft, system compromise, supply chain attacks, and obfuscation techniques.
Why it was flagged
The skill instructs executing repository-supplied scripts and "EXECUTE_COMMAND" hooks (pre/post) and reads many project files, which enables arbitrary remote code execution and makes data exfiltration/backdoor insertion trivial if a malicious hook or script is present.
W007: Insecure credential handling detected in skill instructions.
What this means
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
Why it was flagged
The prompt requires reading .specify/extensions.yml and emitting hook command strings (e.g., "EXECUTE_COMMAND: {command}" and raw `{command}` in outputs), which would force the LLM to reproduce any secrets embedded in those commands verbatim.
Low
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 workflow reads `.specify/extensions.yml` (step 1, lines 12-15 and step 10, lines 168-170); since that file is not authored by the operating user and its contents can include arbitrary free-text fields (e.g., description/prompt), it can be fed into the LLM context via the “Prompt”/hook output.
- Repository
- unoplatform/uno
- Commit
5927220
- 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.