encapsulation

Featured

This skill should be used when the user asks to "audit plugin encapsulation", "check self-containment semantics", "find contributor-knowledge assumptions", or invokes /encapsulation. Reviews LLM-facing prose in this project's plugin SKILL.md files and plugin description metadata for Plugin Encapsulation compliance: prose that assumes contributor documentation knowledge or rephrases banned references to bypass deterministic checks. Project-local contributor tooling.

Data & Documents 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

# Encapsulation Audit The project-local instance of the **semantic-audit engine** (`docs/audit-engine.md`). The shared mechanism — read-only Claude-judge review, the scope shape, severity calibration, self-application stance, and on-demand slash invocation — is defined in that engine document; read it for the parts this skill holds in common with its published siblings. Below is this instance's principle parameter and the one place its output schema extends the engine's base. This instance audits LLM-facing prose for Plugin Encapsulation: the runtime contract surface (`SKILL.md` plus plugin description metadata) must be self-contained and intelligible without contributor documentation. Project-local — its principle is coupled to this repo's deterministic encapsulation check and contributor model, and so (unlike `white-bear` and `zero-shot`) it is not decouplable into a portable skill. Read-only: it emits structured findings and writes no fixes. ## Purpose Surface encapsulation drift that the deterministic verify check (`artifact-self-containment` BANNED patterns) cannot catch — prose that assumes contributor sidecar knowledge in plain language, or rephrases banned references to evade pattern matching. Findings are presented for review; the human author decides which to rewrite, mark as load-bearing, or dismiss. ## Inputs **Manual invocation only** (interactive `/encapsulation`): - The caller passes target file paths or a glob; with no argument, the skill enumerates the ...

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

Code & Development Listed

review-skill

Reviews and audits an existing skill, then tightens it — a fast, static, read-only audit of a `SKILL.md`'s triggering, scope, structure, prose, and domain accuracy, with severity-ranked findings applied on approval. Use whenever the user wants to review, critique, audit, lint, tighten, or improve a skill they already have, fine-tune a skill drafted with skill-creator, or asks why a skill is too verbose, won't trigger, or feels off — even when they just paste a SKILL.md and ask for feedback. Defers the empirical loop (running evals, benchmarking, the automated description optimizer, packaging) to skill-creator; this is the static counterpart that reads rather than measures.

0 Updated today
azborgonovo
AI & Automation Listed

skill-review

Security, safety, and quality review of Claude Code plugin marketplaces, plugins, and skills before install/approval. Use when the user asks to review, audit, vet, or approve a marketplace, plugin, or skill; check allowed-tools/permissions; scan for prompt injection, embedded secrets, or unsafe tool use; or produce a scored go/no-go report on Claude Code extensions.

0 Updated 4 days ago
johnoconnor0
AI & Automation Listed

code-audit-deep

Line-level code audit skill. Surfaces concrete, actionable findings — perf hotspots, error-handling correctness bugs, durability / ordering bugs, memory-shape problems, function-level complexity, semantic coupling, concurrency-primitive scope mistakes, and unenforced or unfalsifiable invariants (gates that cannot reach the violation, assertions that cannot fail, rules that live only in a comment) — that file-level architectural analysis cannot see. Language-agnostic. **This skill owns the word "hotspots" when the user wants line-level findings inside files** — phrasings like "what are the hotspots", "where are the hotspots in X", "find hotspots in this file", "show me the hotspots", "any hotspots in commit.rs?" all trigger this skill; prefer this over `architectural-hotspots` whenever the user is pointing at code and asking what's wrong with it, rather than asking which files in the repo are structurally suspect. Also trigger on "audit this", "review this code", "audit X", "review X", "find bugs in X", "what'

0 Updated 2 weeks ago
Stoica-Mihai