CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

effect-ledger

Check that the effect ledger, the internal judge of native sync, never calls a merge held when it lost work, over every merge the real rebase writes for short command lists on small documents and the intake's queue cases. Eleven planted mutations must read lost, an intent oracle written apart from the ledger must agree, held verdicts must compose, and every merge must reopen as a valid document through createEditor. Use before and after changing packages/plitejs/src/core/change/effect-ledger.ts, the rebase or another file in its coverage record, when the effect-ledger step of pnpm check fails, or when fixing a broken merge the native sync plan's M0.6 names.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

No security issues found

Scanned

Repository

udecode/plate

Path

.agents/skills/effect-ledger/SKILL.md

Audited
Security analysis
Snyk

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.