changelog-automation
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
86
71%
Does it follow best practices?
Impact
97%
1.16xAverage score across 6 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/documentation-generation/skills/changelog-automation/SKILL.mdSecurity
2 findings — 2 medium severity. This skill can be installed but you should review these findings before use.
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
Third-party content exposure detected (high risk: 0.80). The skill's workflows (e.g., Method 3: semantic-release, Method 4: the GitHub Actions release.yml, Method 5: git-cliff and other changelog generation steps) explicitly ingest and act on commits, PRs, and GitHub release/compare data (user-generated, public GitHub content), which the automation reads and uses to decide version bumps and release actions, so untrusted third‑party content can materially influence behavior.
W012: Unverifiable external dependency detected (runtime URL that controls agent)
What this means
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
Why it was flagged
Potentially malicious external URL detected (high risk: 0.80). The GitHub Actions workflow references and will fetch/execute external actions at runtime (e.g., uses: actions/checkout@v4, actions/setup-node@v4, softprops/action-gh-release@v1) and the workflow runs npx semantic-release / npm ci which fetch and execute code from external registries, so these external references are runtime dependencies that execute remote code.
- Repository
- wshobson/agents
- Commit
91fe43e
- 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.