CtrlK
BlogDocsLog inGet started
Tessl Logo

work-operating-model

Conversation-first workflow for turning tacit work patterns into a structured operating model. Use when the user wants to map how their work actually runs, generate USER.md / SOUL.md / HEARTBEAT.md artifacts, or build an agent-ready model of rhythms, recurring decisions, dependencies, institutional knowledge, and friction. Requires base Open Brain search/capture tools plus the paired Work Operating Model recipe MCP tools.

71

Quality

88%

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

88%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.

The body is a high-quality, actionable interview-orchestration skill with a clearly sequenced workflow, explicit validation checkpoints, and concrete tool/prompt/field guidance. Its main limitation is progressive disclosure: everything lives in one large file with no reference split, and a couple of preamble/example passages could be tightened.

Suggestions

Move the per-layer canonical entry shapes and Interview Guidance By Layer into a reference file (e.g. references/layers.md) linked from SKILL.md, so the main file is a lean overview with one-level-deep references.

Tighten the Purpose section by dropping the philosophical opener ("The first job is not to automate the user…") and lead with the concrete five-step job list.

Add one fully-populated canonical entry example (all 11 common fields plus a layer's details filled in) to make the entry contract copy-paste concrete.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — it never explains basic concepts (what a decision or knowledge is) and keeps guidance task-specific, but the philosophical Purpose preamble ("The first job is not to automate the user…") and the long worked summary-thought example could be trimmed, so it sits at 4 rather than a lean 5.

4 / 5

Actionability

Fully actionable for an instruction-only skill: it names exact tools (search_thoughts, capture_thought, start_operating_model_session, save_operating_model_layer, etc.), gives concrete interview prompts ("Walk me through a real Monday from the last two weeks."), specifies the full canonical entry field contract per layer, and provides worked checkpoint and summary-thought examples covering the common cases.

5 / 5

Workflow Clarity

A clear four-phase sequence (Session Start → Layer Interview → Final Review → Export) with explicit validation checkpoints — per-layer confirmation before each save, a contradiction pass via query_operating_model, and a revise-and-resave feedback loop — plus checklists in the Non-Negotiable Rules and Canonical Entry Contract, matching the 5 anchor; the destructive/batch cap does not apply because validation is present.

5 / 5

Progressive Disclosure

Well-organized with clear, purposeful section headers and easy in-file navigation, and self-containment is defensible for an interactive interview skill, but it is a ~280-line monolith with no external references and reference-like material (canonical contracts, per-layer guidance) kept inline, so it does not reach the split, one-level-deep-reference structure of the 5 anchor.

4 / 5

Total

18

/

20

Passed

Description

87%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 strong: it explicitly covers both what the skill does and when to use it, with concrete named artifacts and a distinctive five-layer niche that minimizes conflict risk. The only soft spot is trigger-term breadth, where a few casual user synonyms would push it from good to comprehensive.

DimensionReasoningScore

Specificity

Lists several specific actions — "map how their work actually runs", "generate USER.md / SOUL.md / HEARTBEAT.md artifacts", and "build an agent-ready model of rhythms, recurring decisions, dependencies, institutional knowledge, and friction" — but the lead framing ("turning tacit work patterns into a structured operating model") is slightly abstract, keeping it just below the comprehensive 5 anchor.

4 / 5

Completeness

Explicitly answers both halves: a clear "what" (conversation-first workflow producing structured artifacts and an agent-ready model) and an explicit "Use when the user wants to map how their work actually runs, generate … artifacts, or build …" clause with concrete trigger phrases, matching the 5 anchor.

5 / 5

Trigger Term Quality

Good natural-term coverage with "rhythms", "recurring decisions", "dependencies", "institutional knowledge", "friction", and the named USER.md / SOUL.md / HEARTBEAT.md artifacts as concrete triggers, but it lacks a few casual synonyms a user might actually say (e.g., "what blocks me", "bottlenecks").

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — the named USER.md / SOUL.md / HEARTBEAT.md artifacts, the fixed five-layer model, and the required Work Operating Model recipe MCP tools make it highly distinguishable with minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
NateBJones-Projects/OB1
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.