file-magic-mismatch-counterexample
From the author
Generated counterexample containing a static asset whose extension does not match its content
Install
npx skills add bruc3van/agent-skills-guard --skill file-magic-mismatch-counterexample -a claude-code
Installs to .claude/skills/file-magic-mismatch-counterexample/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 86
Security100
Provenance71
Maintenance100
Licence100
Adoption43
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- homoglyph-obfuscation-counterexamplebruc3van/agent-skills-guardGenerated counterexample containing mixed-script lookalike account namesOther★ 391
- allowed-tools-mismatch-counterexamplebruc3van/agent-skills-guardGenerated counterexample declaring narrow tool access while scripts perform network activityOther★ 391
- counterexample-generatorArabelaTso/Skills-4-SEGenerate concrete counterexamples when formal verification, assertions, or specifications fail. Use this skill when debugging failed proofs, understanding why verification fails, creating minimal reproducing examples, analyzing assertion violations, investigating invariant breaks, or diagnosing specification mismatches. Produces concrete input values, execution traces, and state information that demonstrate the failure.Finance★ 258
- pipeline-exfil-counterexamplebruc3van/agent-skills-guardGenerated counterexample containing a multi-stage sensitive data exfiltration pipelineOther★ 391
- counterexample-explainerArabelaTso/Skills-4-SEExplain why counterexamples violate specifications by analyzing formal specifications (temporal logic, invariants, pre/postconditions, code contracts), informal requirements (user stories, acceptance criteria), test specifications (assertions, property-based tests), and providing step-by-step traces showing state changes, comparing expected vs actual behavior, identifying root causes, and assessing violation impact. Use when debugging test failures, understanding model checker output, explaining runtime assertion violations, analyzing static analysis warnings, or teaching specification concepts. Produces structured markdown explanations with traces, comparisons, state diagrams, and cause chains. Triggers when users ask why something failed, explain a violation, understand a counterexample, debug a specification, or analyze why a test fails.Testing★ 258
- gsd:docs-updatedavepoon/buildwithclaudeGenerate or update project documentation verified against the codebaseOther★ 3.7K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in