CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

macrocosm-oes

Reads, checks and explains MacroCOSM `.cosm` files — Holotypes, Canon catalogs, product trees, fabulas, holographs — and, only when the user asks, decompiles a text into its fabula, writes its atem (the tightest fair, full, plain reduction of a text), puts a volume's questions to the user and records their answers, builds a fabulac of a folder of Python, or runs a Thym program. Use for "what is this .cosm file", "read this Holotype", "lint this .cosm", "decompile this text", "make an atem of this", "say it in one line", "what is a fabula", "what does this stance mean", "ask me the questions", "build a fabulac", "run publish-story on this", "what is Thym". Not for an ordinary summary in the user's own terms (answer that directly), not for editing a Holotype's content (that is Comprise's work), and not for writing new .cosm volumes by hand.

Quality

93%

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

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, disciplined overview of a bespoke domain: no filler, hard limits and exact tool tags throughout, and an explicit tool order with embedded checks and error-refusal guidance. The residual gaps are deferred tool-call syntax, absent lint-failure recovery steps, and the unlinked references/README.md.

Suggestions

Include one complete worked tool call (e.g. a full fabula_derive or thym_run invocation with all its tags filled in) so guidance is copy-paste ready instead of deferring syntax to "the Tools section".

State what to do when cosm_lint reports failures — fix in place, report to the user, or re-run after edits — to close the validation loop for the reading workflow.

Link references/README.md from the "More" section so the bundle's source map is discoverable from the body rather than partially duplicated.

DimensionReasoningScore

Conciseness

The ~175-line body is dense with novel domain rules and contains no padding and no explanation of concepts Claude already knows ("People are never in files. Employees live only in Comprise's sealed database."); compatibility with old versions ("oes: emf/1… is still read", "a program that still says `tell`… runs the same, but write `entail`") is handled inline as explicit deprecated-spelling notes, so every token earns its place.

5 / 5

Actionability

Guidance is concrete — exact tags and values ("`thym_run`, only when asked: `<program>`, `<path>` the first input, others as `<inputs>` lines (`name=path`)", "`fabulac` `<do>build</do>`", "`<do>compile</do>` with `<what>` `code`… or a catem's depth: `line`, `overview`, `manual`") plus hard limits (6,000/24,000 characters, 60 files, 6,000 lines) — but exact tool-call syntax is deferred ("Their tags are in the Tools section") and no complete worked example is shown, so it is mostly executable with minor gaps rather than copy-paste ready.

4 / 5

Workflow Clarity

"The tools, in order" gives a numbered sequence with explicit checkpoints (`cosm_lint` at step 2, "`thym_check`… Use it first" before `thym_run`, fabulac job "`status` says what landed; `cancel` stops it; `build` again resumes it") and refusal handling ("say what was refused and what would make it run"); however, what to do when `cosm_lint` reports failures is never addressed, leaving a minor validation gap that keeps it below the 5 anchor.

4 / 5

Progressive Disclosure

The body is a genuine overview with clear sections pointing one level deep to the specs ("`docs/MACROCOSM_OES.md`… `docs/THYM.md`, `docs/ASCRIBE.md`, `docs/COMPRISE_OES.md`"), and the bundle's `references/README.md` is a well-organized source map; but the body never links `references/README.md` directly (the "More" section duplicates part of it), a minor organization gap versus the 5 anchor's fully well-signaled references.

4 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: third-person voice, comprehensive concrete actions, an explicit "Use for" clause containing the .cosm extension and natural phrasings, and "Not for" boundary exclusions that sharply limit conflict risk. Every dimension sits at the top anchor.

DimensionReasoningScore

Specificity

"Reads, checks and explains MacroCOSM `.cosm` files… decompiles a text into its fabula, writes its atem… puts a volume's questions to the user and records their answers, builds a fabulac of a folder of Python, or runs a Thym program" lists seven-plus concrete third-person actions covering the skill's full surface, matching the 5 anchor's comprehensive coverage; it is not 4 because no capability area from the body is missing.

5 / 5

Completeness

It explicitly answers both halves: a clear what ("Reads, checks and explains MacroCOSM `.cosm` files — Holotypes, Canon catalogs, product trees, fabulas, holographs…") and an explicit when ("Use for…" with concrete trigger phrases), plus "Not for…" exclusions — matching the 5 anchor exactly.

5 / 5

Trigger Term Quality

The "Use for" list — "what is this .cosm file", "lint this .cosm", "decompile this text", "make an atem of this", "say it in one line", "ask me the questions", "build a fabulac", "run publish-story on this", "what is Thym" — includes the file extension, natural user phrasings and synonyms for every capability; not 4 because both extensions and colloquial variants are comprehensively present.

5 / 5

Distinctiveness Conflict Risk

The ".cosm" niche is highly specific and the exclusions ("not for editing a Holotype's content (that is Comprise's work)", "not for an ordinary summary in the user's own terms") explicitly disambiguate neighboring skills, giving a clear niche with minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

0gsd/enough

Path

defaults/skills/macrocosm-oes/SKILL.md

Reviewed

Table of Contents

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.