Skip to content
Back to skills

Do

ASecurity

Enforce CLAUDE.md framework compliance. Re-reads rules, displays applicable rules, processes request with full compliance.

  • 4 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 12, 2026
business

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 12, 2026

npx -y skills add aibot88/sec_skill_store --skill do --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Do?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Do
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aibot88-sec-skill-store/badge)](https://www.skillsdirectory.com/skills/aibot88-sec-skill-store)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: do
description: Enforce CLAUDE.md framework compliance. Re-reads rules, displays applicable rules, processes request with full compliance.
argument-hint: "[user request]"
disable-model-invocation: true
---

# Enforce Framework Compliance

## CRITICAL ENFORCEMENT PROTOCOL

**BEFORE PROCESSING ANY REQUEST:**
1. Re-read ~/.claude/CLAUDE.md completely
2. Display ALL applicable rules for the operation
3. Process the user's request with FULL compliance
4. Verify rule adherence after completion

## Boy Scout Principle
- Compliance checks must always leave the workspace cleaner: fix misfiled rules, stale configs, or missing evidence as soon as you notice them
- If you uncover sloppy prior responses or unchecked boxes, correct them before moving forward so future runs inherit a healthy baseline
- Document each cleanup in the final verification block so the improvement is provable, not implied

## MANDATORY COMPLIANCE CHECKLIST

### PRE-EXECUTION
- [ ] Display relevant rules
- [ ] Classify operation type
- [ ] Display ALL relevant rule sets
- [ ] Re-read CLAUDE.md if needed
- [ ] Assess whether the planned workflow preserves separation of concerns, keeps each actor's responsibility singular, and avoids introducing tight coupling

### DURING EXECUTION
- [ ] Before EVERY tool use: verify rule compliance
- [ ] After EVERY tool use: confirm rules followed
- [ ] Maintain rule display in responses
- [ ] Follow workflows exactly

### POST-EXECUTION
- [ ] Verify all rules were followed
- [ ] Confirm deliverables match requirements
- [ ] Check for any rule violations

## REINFORCEMENT MANTRA

**REPEAT INTERNALLY BEFORE EVERY ACTION:**
- I MUST display rules at the start of EVERY response
- I MUST classify operations and show appropriate rules
- I MUST verify technical claims with evidence
- I MUST respect agent boundaries
- I MUST NOT create random markdown files
- These rules apply to ALL interactions, ALL tool uses

## USER REQUEST PROCESSING

After enforcing compliance above, process the user's actual request:

---

$ARGUMENTS

---

## FINAL VERIFICATION

Before completing response:
1. Did I display relevant rules?
2. Did I classify the operation type?
3. Did I display all relevant rule sets?
4. Did I follow the rules throughout?

Files in this skill

  • SKILL.md2.2 KB
  • source.json595 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.