.claude/skills/<skill-name>1 structural issue
- error: SKILL.md does not contain a complete YAML frontmatter envelope.
skill.md
Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Use this skill to operate a hardened AI agent that analyzes vulnerabilities in authorized systems, challenges weak evidence, builds attack paths, prioritizes real risk, and recommends safe validation and remediation
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/<skill-name>skill.mdRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/<skill-name>skill.mdRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/<skill-name>skill.mdRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @3mper0rr/3mper0rr-ai-vulnerability-analyzerclawhub inspect @3mper0rr/3mper0rr-ai-vulnerability-analyzer --version 1.0.2This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
missing frontmatterThis is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:420237c32fca60836b16211ccdbf7bd1ff127a2a62232e8ee5d808359bfdea09skill-card.mdskill.mdVersion 1.0.2 Changelog - Updated SKILL.md with detailed agent mission, operating modes, authorization requirements, and analysis pipeline. - Clarified input context expectations and evidence types needed for analysis. - Provided explicit steps for vulnerability analysis, including triage, attack path construction, exploitability, and impact assessment. - Emphasized rigorous authorization checks and strict safety policies before proceeding. - Outlined modes for triage, red team analysis, remediation, and safe validation. - Improved guidance on risk prioritization and false positive handling.
Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.
These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.
sha256:caaff7bb720af824027c72fec9f47729005013ac37122e48cf21b20a16eb9d11sha256:6344c1970288772da6e46d5b529af7278ff29344acbc5684a74283344597a131