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.

72

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

77%

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

A well-structured, actionable instruction skill with strong workflow sequencing and validation loops. It is slightly verbose due to redundant passes over the five layers and leaves room to move the detailed entry contract into a reference file.

Suggestions

Consolidate the three passes over the five layers: keep the canonical entry contract and interview guidance together per layer (or reference one from the other) to remove redundancy.

Extract the 'Canonical Entry Contract' and 'Interview Guidance By Layer' sections into a single references file (e.g. LAYERS.md) and point to it from SKILL.md to improve progressive disclosure.

Tighten the Non-Negotiable Rules and Workflow sections where they restate the same ordering and confirmation steps.

DimensionReasoningScore

Conciseness

Mostly efficient and free of concept-explanation fluff, but the five layers are covered three times (fixed layer order, canonical entry contract details, and per-layer interview guidance), which is more than a lean skill needs.

2 / 3

Actionability

Highly actionable for an instruction-only skill: exact tool calls, precise canonical entry field shapes, concrete interview prompt patterns ('Walk me through a real Monday from the last two weeks'), and a copyable approval-ask example.

3 / 3

Workflow Clarity

Four clearly sequenced phases with explicit validation checkpoints (confirm before save) and a feedback loop in Phase 3 (contradiction pass -> revise -> resave before export), matching the anchor for clear sequence with validation and error recovery.

3 / 3

Progressive Disclosure

Well-organized into clear sections with no nested references, but everything is inline in a ~280-line SKILL.md; the canonical entry contract and per-layer guidance could be split into a one-level-deep reference file.

2 / 3

Total

10

/

12

Passed

Description

100%

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

A strong, specific description with explicit trigger guidance and concrete named actions and artifacts. It is third person, concise, and clearly distinct from other skills.

DimensionReasoningScore

Specificity

Names multiple concrete actions: 'turning tacit work patterns into a structured operating model', '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'.

3 / 3

Completeness

Explicitly answers both what (the workflow/artifacts it produces) and when via the 'Use when the user wants to...' clause, matching the anchor for clearly answering both what AND when.

3 / 3

Trigger Term Quality

Natural user-language triggers are well covered: 'map how their work actually runs', 'operating model', the named artifacts, and the layer list (rhythms, recurring decisions, dependencies, institutional knowledge, friction) a user would plausibly say.

3 / 3

Distinctiveness Conflict Risk

A clearly defined niche — building a Work Operating Model from five fixed layers with named artifacts and specific MCP tooling — that is unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

12

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.