encapsulation

Solid

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 125 stars 11 forks Updated today MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
70
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
7 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

self-audit

Self-audit this skills repo against CLAUDE.md invariants, the v3 artifact contract, and README/CLAUDE.md/docs sync via three parallel read-only subagents. Local meta-skill — independent of the /task:* pipeline.

7 Updated 4 days ago
SpaiR
AI & Automation Listed

skill-security-audit

Security-audit Agent Skills and plugins — vet a new skill before installing it, scan everything already installed on this machine, or harden your own skill before publishing. Use when asked to vet, review, or check a skill/SKILL.md/plugin for safety, prompt injection, malware, or suspicious behavior — or to make a skill safe to publish.

0 Updated 6 days ago
joshphoenix1
Data & Documents Listed

skill-safety-audit

Statically audits a downloaded/third-party Claude skill (or any small code bundle: scripts folder, plugin, gist, repo) for safety BEFORE it is ever run — detecting malware, data exfiltration, credential/secret theft, destructive or persistence behavior, and prompt-injection hidden in SKILL.md or docs — then produces a plain-language HTML report with a traffic-light verdict. Use this whenever the user has downloaded, cloned, or received a skill/plugin/script from GitHub, a gist, Discord, a blog, or any untrusted source and asks whether it is safe, whether it might contain a virus, whether it steals their data or info, whether it is trustworthy, or asks you to "check / review / vet / audit / scan / 검사 / 안전한지 확인" a skill or code folder before installing or running it. Trigger even if they just say "이 스킬 안전해?" or "믿고 써도 돼?" about downloaded code. Do NOT use this for auditing the user's OWN code they are actively writing, for general code review of trusted first-party code, or for reviewing pull requests (use code

0 Updated 5 days ago
huiaunt