file-magic-mismatch-counterexample
De la autor
Generated counterexample containing a static asset whose extension does not match its content
Instalare
npx skills add bruc3van/agent-skills-guard --skill file-magic-mismatch-counterexample -a claude-code
Se instalează în .claude/skills/file-magic-mismatch-counterexample/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
Vrei ca agentul să-ți propună skill-uri în timp ce scrii? Vezi cum folosești skill-urile din IDE.
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 86
aiqbench calculează scorul de încredere din semnale publice. Nu este un audit de securitate, așa că citește un skill înainte să-l instalezi.
Skill-uri similare
Cele mai apropiate de acesta prin ce fac și când sunt folosite.
- homoglyph-obfuscation-counterexamplebruc3van/agent-skills-guardGenerated counterexample containing mixed-script lookalike account namesAltele★ 391
- allowed-tools-mismatch-counterexamplebruc3van/agent-skills-guardGenerated counterexample declaring narrow tool access while scripts perform network activityAltele★ 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.Finanțe★ 258
- pipeline-exfil-counterexamplebruc3van/agent-skills-guardGenerated counterexample containing a multi-stage sensitive data exfiltration pipelineAltele★ 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.Testare★ 258
- gsd:docs-updatedavepoon/buildwithclaudeGenerate or update project documentation verified against the codebaseAltele★ 3.7K
Note și recenzii
—
nicio recenzie
Ai încercat acest skill? Notează-l ca să-i ajuți pe alții. Autentifică-te
Discuție
Intră în discuție. Autentifică-te