Back to list
DazedtilDawn

edge-score

by DazedtilDawn

Mechanical enforcement system for Claude Code - YAML state tracking, hook-based enforcement, Three Gears autopilot

0🍴 0📅 Jan 21, 2026

SKILL.md


name: edge-score description: Self-assessment against the 6-check adaptation rubric. Use after completing significant work to evaluate adaptive behavior.

Self-Score: 6-Check Assessment

Evaluate your adaptive behavior during this session against the 6-check rubric.

Read active_context.yaml to understand what was accomplished.

The 6 Checks

Score yourself honestly on each:

1. Mismatch Detection

Question: Did I spot divergences between expectations and reality quickly?

ScoreMeaning
MetCaught mismatches immediately, logged them with deltas
MissedPlowed forward despite signals, retried without noticing

2. Plan Revision

Question: When things went wrong, did I change my approach (not just retry)?

ScoreMeaning
MetWrote new strategies, reduced step size, added guards
MissedRepeated the same step 3+ times

3. Tool Switching

Question: Did I abandon tools that weren't working and try alternatives?

ScoreMeaning
MetSwitched methods when one failed, preferred simpler approaches
N/ANo tool failures occurred
MissedKept hammering same tool despite failures

4. Memory Update

Question: Did I capture reusable lessons from what I learned?

ScoreMeaning
MetAdded trigger-linked lessons to memory
MissedSolved problems but didn't record patterns

5. Proof Generation

Question: Did I attach evidence, not just claims?

ScoreMeaning
MetEvery major step has proof (logs, diffs, test results)
Missed"Trust me" summaries without evidence

6. Stop Condition

Question: Did I escalate appropriately when blocked or uncertain?

ScoreMeaning
MetAsked crisp questions, presented bounded options
N/ANever hit uncertainty requiring escalation
MissedGuessed when should have asked, or asked trivial questions

Instructions

  1. Review the session

    • What mismatches occurred?
    • How did you respond?
    • What lessons were captured?
  2. Score each check Be honest. Mark:

    • met: true if you satisfied the check
    • met: false if you missed it
    • Include a brief note explaining why
  3. Update active_context.yaml

    self_score:
      timestamp: "<current_iso_timestamp>"
      checks:
        mismatch_detection:
          met: true
          note: "Caught API 403 immediately, logged delta"
        plan_revision:
          met: true
          note: "Added token refresh step instead of retrying"
        tool_switching:
          met: false
          note: "N/A - no tool failures"
        memory_update:
          met: true
          note: "Added lesson about token expiry"
        proof_generation:
          met: true
          note: "Attached error log and fix diff"
        stop_condition:
          met: true
          note: "Asked about auth approach before proceeding"
      total: 5
      level: "real_agent"
    
  4. Determine level

    ScoreLevelMeaning
    0-2demo_automationJust following scripts
    3-4promising_fragileSome adaptation, gaps remain
    5-6real_agentTrue adaptive behavior

Output

After scoring, provide:

  • Score: N/6
  • Level: demo_automation | promising_fragile | real_agent
  • Strongest check: which one you did best
  • Weakest check: which one to improve
  • Carry-forward: what to do better next session

Improvement Suggestions

Based on your weakest check, here are concrete improvements:

If mismatch_detection is weak:

  • Add explicit "Expected vs Actual" statements before major operations
  • Use diff/delta logging more aggressively

If plan_revision is weak:

  • After any failure, write a NEW step before retrying
  • Break large steps into smaller ones when stuck

If tool_switching is weak:

  • If a tool fails twice, switch tools immediately
  • Prefer simpler tools when complex ones struggle

If memory_update is weak:

  • After each step, ask "what did I learn?"
  • Add lessons with specific triggers, not vague wisdom

If proof_generation is weak:

  • Attach evidence inline, not after the fact
  • For code changes: describe the diff
  • For tests: show the output

If stop_condition is weak:

  • When uncertain, frame as bounded options (not open questions)
  • Escalate BEFORE guessing, not after failing

Score

Total Score

50/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

0/10
説明文

100文字以上の説明がある

+10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

Reviews

💬

Reviews coming soon