misuse

Featured

Retrospective protocol contract violation detector. Scan past sessions for /ground (Sₐ confabulation) and /induce (stereotype misconflation) contract violations and surface structured violation records for user-constituted review. Use this skill whenever the user asks to 'audit my misuse', 'check protocol misuse', 'scan past invocations', 'misuse history', wants retrospective audit of past /ground or /induce calls, or suspects silent contract violations in prior sessions.

AI & Automation 161 stars 15 forks Updated today MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
74
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Misuse Skill Retrospective Contract Violation Detector — when the user wants to audit past `/ground` and `/induce` invocations for silent contract violations, scan session history against contract integrity criteria and surface candidate violations for user-constituted review. Type: `(ContractIntegrityOpaque, AI, AUDIT, SessionHistory) → ViolationReview`. Invoke directly with `/misuse` when the user wants a retrospective audit of past protocol invocations against their declared Phase 0 contracts. ## Definition **Misuse** (ἔλεγχος, *élenchos*: examination by drawing out, Socratic refutation): A dialogical act of resolving the opacity of past protocol contract integrity into a recognized violation history, where AI scans session JSONL for `/ground` and `/induce` invocations, classifies each against the contract criteria in `references/violation-taxonomy.md` (LEGITIMATE / VIOLATION / AMBIGUOUS), and the user constitutes the verdict via per-invocation recognition — never AI-resolved verdict assertion. This skill stands in time-axis dual relationship to `/probe`. Probe is prospective: when a deficit is unrecognized at the present moment, surface candidate hypotheses with reverse-evidence so the user routes forward. Misuse is retrospective: when contract integrity in past invocations is opaque, surface candidate violations with operational evidence so the user audits backward. Both refuse AI-side resolution; both treat user recognition as the constitutive act. Phase 4 recog...

Details

Author
jongwony
Repository
jongwony/epistemic-protocols
Created
8 months ago
Last Updated
today
Language
JavaScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

skill-usage-audit

Scan all artefacts (epics, stories, PRDs) for Base Rule

160 Updated today
Fr-e-d
AI & Automation Solid

retro

Scientific session-closing retrospective: scan the current conversation, turn each signal into a falsifiable hypothesis, cite session evidence for AND against it, assign a verdict (supported / refuted / inconclusive) and a confidence level, then promote only supported, sufficiently-confident hypotheses into the harness memory tiers (.oh/memory/MEMORY.md, .oh/context/IDENTITY.md) behind a propose-then-confirm gate. Reflects on six learning/knowledge subsystems through the lens of this session — continual learning, context compression, reinforcement learning, wiki, docs, and memory scaffolding — and points at the deep-dive lint/audit skills rather than running them. Operationalizes the Memory Improvement Protocol (.oh/skills/retro/references/memory-protocol.md) as an explicit, evidence-driven, session-closing skill rather than a per-run afterthought. Always appends a log entry. TRIGGER when: /retro invoked, or session closing with decisions, surprises, or failures worth preserving.

38 Updated today
mifunedev
AI & Automation Listed

audit

Use this skill to audit a software team's engineering practices — CI/CD, testing, code review, monitoring, Developer Experience, and ownership culture — and produce a scored, evidence-based audit report. Trigger when the user asks to "audit our team", "review our CI/CD setup", "assess our testing practices", or describes their team/project and wants an honest read on where they stand. This skill produces the audit report only — it does not build an improvement plan. For that, hand the audit output to the strategy skill, or use the minottobot skill for the two combined.

4 Updated 1 weeks ago
EmanueleMinotto