Coordinate structured critique of software architecture, code, and writing.
npx skills add https://github.com/korentomas/kloydele --skill kloydele
Please help me install this Agent Skill. Skill: kloydele Source: https://github.com/korentomas/kloydele/tree/main Command: npx skills add https://github.com/korentomas/kloydele --skill kloydele
Cloydele, a Jewish way of thinking applied to coding and problem solving. Use when approaching problems that deserve more depth, when reviewing code or writing, when stuck, or when thinking feels shallow. Argue the other side before you commit. Fix what's there before you rewrite. Say what's actually wrong instead of being polite. Ask questions instead of giving answers.
It helps teams engage in structured, value-driven critique by forcing exploration of opposing viewpoints, surfacing biases, and ensuring deeper consideration before decisions.
Invoke Cloydele with the command /kloydele to start a study partner session and share your current work.
High-intent search queries and answers about installing and using this skill.
Structured code review requires exploring opposing viewpoints and surfacing biases to ensure deeper consideration. You can initiate a study partner session to read your work, push back on assumptions, and highlight where to dig deeper before committing.
The chavruta method for architecture review acts as a study partner that reads your work, questions it, and pushes back to reveal tensions. It forces exploration of opposing viewpoints to surface biases and ensure deeper consideration before decisions.
To force productive disagreement when analyzing technical writing, you apply structured critique principles that require arguing the other side before committing. This approach asks questions instead of giving answers and says what is actually wrong instead of being polite.
Yes, you can apply named principles like Machloket, PaRDeS, and Teshuvah to improve shallow codebase decisions. This principle invocation guides analysis by scanning documents and code to highlight exactly where deeper thinking is required.
You should avoid this adversarial approach for software problem solving when a problem is straightforward and lacks depth, as it is designed for problems that deserve more rigorous thinking. It is specifically built for situations where thinking feels shallow or when you are stuck.
samdenglerAnalyzes grammar, clarity, tone, and consistency of documents and code via command-line file review.
gewoonsebaEvaluate implementation plans from .claude/plans/ with a structured checklist and verdict.
VoDaiLoczAutomate linting and static analysis of code in CI pipelines.
robotijnDetect AI-specific code flaws like hallucinated imports and vacuous assertions.
