How do I install the Encapsulation Reviewer skill?

Run npx skillmds@latest add 45ck/encapsulation-reviewer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Encapsulation Reviewer skill do?

encapsulation-reviewer It is listed under Coding & Dev Tools on SkillMD.

Is Encapsulation Reviewer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Encapsulation Reviewer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Encapsulation Reviewer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Encapsulation Reviewer?

45ck (@45ck) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Encapsulation Reviewer by 45ck — Agent Skill

Name: Encapsulation Reviewer
Author: 45ck

File contents

encapsulation-reviewer

Purpose

Review fields, methods, and object interactions for information hiding, invariant protection, and leakage of internal state.

Trigger this skill when

Objects expose too much mutable state.
Invariants can be broken from outside the class.
APIs feel leaky or too permissive.

Expected inputs

class definitions
fields and methods
mutation paths
public API surface
invariants if known

Deliverables

exposure findings
invariant risks
API surface recommendations
state-protection suggestions
follow-up actions

Operating procedure

Identify the object-oriented concern this skill is meant to assess.
Separate facts from inferred design intent.
Review the current structure against OOP fundamentals: responsibility, invariants, ownership, exposure, abstraction, and lifecycle where relevant.
Surface concrete risks, tradeoffs, and improvement options.
Prefer minimal structural change that materially improves clarity or safety.
Hand off to the next most relevant skill if the issue is broader than this skill alone can resolve.

Quality gates

Findings are tied to concrete code structure or stated design intent.
Recommendations explain why, not just what.
Tradeoffs are stated when multiple designs could work.
Output avoids style nitpicks unless they affect abstraction or maintainability.

Handoff targets

visibility-modifier-reviewer
immutability-opportunity-finder
constructor-sanity-checker

Output style

Be explicit about uncertainty.
Prefer short, evidence-based findings over long vague critique.
Distinguish design defects from mere preference.
End with recommended next actions.

Failure modes to avoid

Do not invent framework constraints without evidence.
Do not recommend sweeping refactors without naming the benefit.
Do not confuse naming/style issues with true design problems unless they affect abstraction.
Do not force inheritance, immutability, or statics as ideology.

Minimum output skeleton

## Summary
## Findings
## Risks
## Recommendations
## Tradeoffs
## Recommended next skill

---name: encapsulation-reviewerdescription: encapsulation-reviewer---# encapsulation-reviewer## PurposeReview fields, methods, and object interactions for information hiding, invariant protection, and leakage of internal state.## Trigger this skill when- Objects expose too much mutable state.- Invariants can be broken from outside the class.- APIs feel leaky or too permissive.## Expected inputs- class definitions- fields and methods- mutation paths- public API surface- invariants if known## Deliverables- exposure findings- invariant risks- API surface recommendations- state-protection suggestions- follow-up actions## Operating procedure1. Identify the object-oriented concern this skill is meant to assess.2. Separate facts from inferred design intent.3. Review the current structure against OOP fundamentals: responsibility, invariants, ownership, exposure, abstraction, and lifecycle where relevant.4. Surface concrete risks, tradeoffs, and improvement options.5. Prefer minimal structural change that materially improves clarity or safety.6. Hand off to the next most relevant skill if the issue is broader than this skill alone can resolve.## Quality gates- Findings are tied to concrete code structure or stated design intent.- Recommendations explain *why*, not just *what*.- Tradeoffs are stated when multiple designs could work.- Output avoids style nitpicks unless they affect abstraction or maintainability.## Handoff targets- visibility-modifier-reviewer- immutability-opportunity-finder- constructor-sanity-checker## Output style- Be explicit about uncertainty.- Prefer short, evidence-based findings over long vague critique.- Distinguish design defects from mere preference.- End with recommended next actions.## Failure modes to avoid- Do not invent framework constraints without evidence.- Do not recommend sweeping refactors without naming the benefit.- Do not confuse naming/style issues with true design problems unless they affect abstraction.- Do not force inheritance, immutability, or statics as ideology.## Minimum output skeleton```md## Summary## Findings## Risks## Recommendations## Tradeoffs## Recommended next skill```

Frequently asked questions

Encapsulation Reviewer