Tencent SkillHub · AI

Self Discipline

Guarantee instruction compliance with root cause analysis, flow verification, and automated validators that make future failures impossible.

skill openclawclawhub Free

0 Downloads

0 Stars

0 Installs

0 Score

High Signal

Guarantee instruction compliance with root cause analysis, flow verification, and automated validators that make future failures impossible.

⬇ 0 downloads ★ 0 stars Unverified but indexed

Install for OpenClaw

Quick setup

Download the package from Yavira.
Extract the archive and review SKILL.md first.
Import or place the package into your OpenClaw setup.

Requirements

Target platform: OpenClaw
Install method: Manual import
Extraction: Extract archive
Prerequisites: OpenClaw
Primary doc: SKILL.md

Package facts

Download mode: Yavira redirect
Package format: ZIP package
Source platform: Tencent SkillHub
What's included: EXTRA_FILES.txt, SKILL.md, flow-verification.md, memory-template.md, root-cause.md, setup.md

Validation

Use the Yavira download entry.
Review SKILL.md after the package is downloaded.
Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

Download the package from Yavira.
Extract it into a folder your agent can access.
Paste one of the prompts below and point your agent at the extracted folder.

New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.

Open Send to Agent page Open JSON manifest Open Markdown brief

Trust & source

Release facts

Source: Tencent SkillHub
Verification: Indexed source record
Version: 1.0.1

Provenance

Publisher: ivangdavila
Source page: View original listing
Canonical URL: Open canonical page

Documentation

ClawHub primary doc Primary doc: SKILL.md 25 sections Open source page

When to Use

User is frustrated that the agent ignored instructions. Something critical happened that cannot repeat. User explicitly says "this can never happen again" or "I told you not to..." User explicitly invokes /discipline to ensure compliance on a rule.

How It Works

┌──────────────────────────────────────────────┐ │ DISCIPLINE TRIGGER │ └──────────────────────────────────────────────┘ │ ┌────────────────────┼────────────────────┐ ▼ ▼ ▼ ┌─────────┐ ┌──────────┐ ┌─────────┐ │ USER │ │ CRITICAL │ │ COMMAND │ │ UPSET │ │ FAILURE │ │ USED │ └────┬────┘ └────┬─────┘ └────┬────┘ │ │ │ │ "I told you..." │ Security breach, │ /discipline │ "Why did you..." │ data loss... │ │ │ │ └───────────────────┴────────────────────┘ │ ▼ ┌─────────────────┐ │ SEVERITY │ │ 🔴 🟡 🟢 │ └────────┬────────┘ │ ▼ ┌─────────────────┐ │ ROOT CAUSE │ │ 5 Whys: Why │ │ wasn't it │ │ followed? │ └────────┬────────┘ │ ▼ ┌─────────────────┐ │ FLOW VERIFY │ │ Will next agent │ │ see the fix? │ └────────┬────────┘ │ ▼ ┌─────────────────┐ │ VALIDATOR │ │ Script that │ │ blocks action │ └────────┬────────┘ │ ▼ ┌─────────────────┐ │ COMPLETE │ │ Logged+Enforced │ └─────────────────┘

Setup

On first use, read setup.md for integration guidelines. Creates ~/self-discipline/ for rules, validators, and enforcement logs.

Architecture

Memory lives in ~/self-discipline/. See memory-template.md for structure. ~/self-discipline/ ├── memory.md # Status + severity thresholds + stats ├── rules.md # Active discipline rules (ALWAYS loaded) ├── incidents.md # Incident log with root cause analysis ├── validators/ # Executable validators │ ├── pre-commit/ # Run before git commits │ ├── pre-send/ # Run before sending messages │ └── custom/ # Domain-specific validators ├── flow-analysis/ # Instruction flow traces └── archive/ # Resolved incidents

Quick Reference

TopicFileSetup processsetup.mdMemory templatememory-template.mdSeverity assessmentseverity.mdRoot cause protocolroot-cause.mdFlow verificationflow-verification.mdValidator patternsvalidators.md

1. Detect Severity Immediately

When triggered, assess severity FIRST: LevelIndicatorsResponse🔴 CRITICALUser angry, security risk, data loss, broken prod, financial impactFull analysis + MANDATORY validator🟡 MEDIUMUser frustrated, wasted time, incorrect outputFull analysis + instruction fix🟢 LOWUser annoyed, preference violatedLog + monitor Default to one level higher if uncertain.

2. Root Cause Before Solution

Never jump to "I'll remember that." Instead: What exactly failed? — Be specific What was the instruction? — Quote it verbatim Where was the instruction? — Path + line number Why wasn't it followed? — 5 Whys: Why? → Not loaded in context Why? → File not in session's read path Why? → No reference in AGENTS.md / system prompt Why? → Setup assumed it would be read Why? → No verification mechanism

3. Verify Flow Reachability (CRITICAL)

After identifying where the instruction SHOULD be, trace the actual agent flow: START: New session begins ↓ READ: System prompt loaded ↓ READ: AGENTS.md (if exists) ↓ READ: MEMORY.md (if referenced) ↓ READ: Other files (if referenced) ↓ QUESTION: Is the instruction in ANY of these? If instruction is NOT in the flow: The fix is NOT to "write it somewhere" The fix IS to add it to a file ALREADY in the flow OR add a reference to its location in a file ALREADY in the flow

4. User Consent Required

NEVER modify files outside ~/self-discipline/ without explicit user permission. When suggesting changes to AGENTS.md, HEARTBEAT.md, or other files: ActionRequirementCreate ~/self-discipline/Ask permission firstEdit AGENTS.mdShow exact changes, wait for approvalAdd to HEARTBEAT.mdShow exact changes, wait for approvalCreate validator scriptShow script content, wait for approvalEdit any existing fileBackup first + user confirmation Flow for external file changes: Explain WHY the change is needed Show EXACTLY what will be added/changed Wait for explicit "yes" / approval Only then make the change

5. Generate Validators for Critical Issues

For 🔴 CRITICAL issues, create automated validators: # Example: ~/self-discipline/validators/pre-send/no-secrets.sh #!/usr/bin/env bash set -euo pipefail # SECURITY MANIFEST: # Environment variables accessed: none # External endpoints called: none # Local files read: message content (stdin) # Local files written: none # Check for secrets before sending messages if echo "$1" | grep -qE '(password|token|key)='; then echo "❌ BLOCKED: Message contains potential secret" echo "Rule: no-secrets-in-messages (from incident 2024-02-15)" exit 1 fi Validators must: Exit 0 = pass, exit 1 = block Include the rule origin (incident reference) Never modify data, only check

6. Track Enforcement

In ~/self-discipline/memory.md, maintain: MetricPurposeActive rulesRules currently being enforcedIncidents by severityPattern detectionValidator triggersHow often rules catch violationsStreakDays since last repeat violation

7. Escalation Path

If the same rule is violated twice: First violation: Full analysis + fix Second violation: Promote to CRITICAL + mandatory validator Third violation: STOP and ask user for intervention

Severity Assessment Protocol

See severity.md for detailed criteria.

Quick Assessment

QuestionIf YES →Is the user visibly upset?+1 severityCould this cause data loss?Automatic CRITICALCould this cause security breach?Automatic CRITICALCould this affect production?Automatic CRITICALHas this happened before?+1 severityDid user use "never" or "always"?+1 severity

The Flow Verification Process

See flow-verification.md for complete protocol.

Why Instructions Get Ignored

CauseFrequencySolutionWritten in file not in load path60%Move or add referenceBuried in long file, not seen20%Move to top or separate fileContradicted by other instruction10%Resolve conflict explicitlyContext window overflow5%Shorten, prioritizeModel genuinely forgot5%Add validator

Verification Steps

Identify all files in agent's load path (system prompt, AGENTS.md, etc.) Check if instruction location is in that path If not in path: Find where to add reference If in path but buried: Move to more prominent location If contradicted: Resolve with explicit priority

Validator Patterns

See validators.md for complete reference.

Types

TypeWhen RunExamplespre-commitBefore git commitNo secrets, no WIPpre-sendBefore message sendNo secrets, format checkspre-actionBefore specific actionConfirm before deleteperiodicOn heartbeatState verification

Validator Template

#!/usr/bin/env bash set -euo pipefail # SECURITY MANIFEST: # Environment variables accessed: [list] # External endpoints called: [list or "none"] # Local files read: [list] # Local files written: [list or "none"] # Validator: [rule-name] # Created: YYYY-MM-DD # Incident: [reference] # Severity: CRITICAL # [description of what this validates] [validation logic] if [condition that should fail]; then echo "❌ BLOCKED: [reason]" echo "Rule: [rule-name] (from incident [date])" exit 1 fi exit 0

Common Traps

TrapConsequenceSolutionWriting rule in memory.md onlyFuture agent won't see itAdd to rules.md (always loaded)"I'll remember" without verificationSame mistake in 3 sessionsAlways verify flow reachabilityValidator that modifies dataUnexpected side effectsValidators ONLY check, never modifyNot backing up before editsCan't recover if wrongALWAYS backup before modifyingSkipping severity assessmentUnder-responding to critical issuesAssess severity FIRST, alwaysPutting rules in wrong fileRules not loadedOnly rules.md is guaranteed loaded

Commands

CommandAction/disciplineStart discipline process for last issue/discipline statusShow active rules and stats/discipline verify [rule]Run flow verification for rule/discipline test [validator]Dry-run a validator/discipline historyShow incident log

Security & Privacy

Data that stays local: All rules, incidents, and validators in ~/self-discipline/ No data sent to external services No telemetry or analytics This skill does NOT: Make network requests Access credentials or secrets Modify files without explicit user permission Run validators without user approval Access files outside ~/self-discipline/ without asking File modifications outside ~/self-discipline/: Only suggested when needed for rule visibility (e.g., AGENTS.md reference) Always shown to user first Require explicit approval before execution Include backup before any edit

Related Skills

Install with clawhub install <slug> if user confirms: reflection — structured self-evaluation memory — persistent memory patterns decide — decision-making patterns escalate — know when to ask vs act learning — adaptive learning system

Feedback

If useful: clawhub star self-discipline Stay updated: clawhub sync

Category context

Agent frameworks, memory systems, reasoning layers, and model-native orchestration.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package

5 Docs1 Files

SKILL.md Primary doc
flow-verification.md Docs
memory-template.md Docs
root-cause.md Docs
setup.md Docs
EXTRA_FILES.txt Files