06-security-rollback-required
Every production feature must consider security, rollback, replay, and failure paths before being called complete. - Auth checks must be real, not `return Ok(())` pass-throughs.
Install / Use
npx skills add Cyptopimpinainteazy/xxxstarInstalls into whichever agent you are using.
Our assessment of 06-security-rollback-required
06-security-rollback-required scores 51/100 on our quality scale, 1085th of 1,103 Security skills we index.
Its .clinerules is 1.2 KB long, split into 5 sections and no code examples: moderately detailed.
It has no GitHub stars yet, so there is no community track record; judge it on its content.
Maintenance, license and trust
- We could not determine when the repository was last updated.
- Our last check on 2026-10-18 could not reach the source (HTTP 404); it may have been moved or deleted.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-24. Automated pattern scan on 2026-09-24. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
06-security-rollback-required compared with similar skills
All 4 of these similar skills score higher than 06-security-rollback-required; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| 06-security-rollback-required (this skill)by Cyptopimpinainteazy | 51 | 0 | — | .clinerules |
| diagram-designby cathrynlavery | 100 | 63.5k | 9d ago | SKILL.md |
| protocol-reverse-engineeringby wshobson | 100 | 39.9k | 46d ago | SKILL.md |
| anndataby K-Dense-AI | 100 | 46.4k | 46d ago | SKILL.md |
| codeqlby github | 100 | 39.3k | 43d ago | SKILL.md |
Frequently asked questions
- How do I install 06-security-rollback-required?
- Run
npx skills add Cyptopimpinainteazy/xxxstar. The install tabs above show the steps for each supported agent. - Which AI agents does 06-security-rollback-required work with?
- It is written for Cline, as a .clinerules file. Other agents that read the same format can often use it too.
- Is 06-security-rollback-required safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is 06-security-rollback-required still maintained?
- We could not determine when the repository was last updated.
Skill content
View source on GitHubRule: Security and Rollback Required
Purpose
Every production feature must consider security, rollback, replay, and failure paths before being called complete.
Required Behavior
- Auth checks must be real, not
return Ok(())pass-throughs. - Secret handling must use proper key management, not hardcoded strings.
- Bridge paths must validate signatures/merkle proofs, not trust incoming data.
- Rollback paths must exist and be tested — revert state, refund assets, cancel operations.
- Replay protection must be present on all cross-chain operations.
- Unsafe code must be documented, minimized, and reviewed.
Forbidden Behavior
- Do NOT ship
// TODO: add authin production paths. - Do NOT hardcode API keys, private keys, or seed phrases.
- Do NOT skip signature verification with
if trueor// skip for now. - Do NOT ship bridge code that doesn't verify source chain proofs.
- Do NOT ship rollback logic that is never tested.
- Do NOT claim mainnet-readiness without security review.
Proof Required
- Security review check must pass or be explicitly waived with reason.
- Rollback tests must exist and pass.
- Replay protection must be demonstrable.
- Unsafe code blocks must be audited.
Related Skills
diagram-design
63.5kCreate branded architecture, architecture delta, IT current-state, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar/spider, polar chart (polar/radial lollipop), loop/flywheel, nested, tree, org chart, layer stack, exploded axonometric, axonometric plan, Venn, py…
protocol-reverse-engineering
39.9kMaster network protocol reverse engineering including packet analysis, protocol dissection, and custom protocol documentation
anndata
46.4kHandles annotated matrices in single-cell analysis, .h5ad and Zarr files, and integration with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
codeql
39.3kComprehensive guide for setting up and configuring CodeQL code scanning via GitHub Actions workflows and the CodeQL CLI. This skill should be used when users need help with code scanning configuration, CodeQL workflow files, CodeQL CLI commands, SARIF output, security analysis setup, or troubleshoot…
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.