openspec-sync-specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
68
81%
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
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
This skill’s required workflow reads delta spec text (including free-form markdown requirement/scenario content) from existing spec files under `openspec/specs/<...>/.../specs/` at runtime (via the CLI status to locate `artifactPaths.specs.existingOutputPaths`, then “Read the delta spec” to apply changes), so that outsider-authored spec body text can be ingested into the LLM context for merging.
- Repository
- Fission-AI/OpenSpec
- Commit
19d4171
- 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.