CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

process-doc

Turn an operational process into a clear SOP, role model, control map, and improvement backlog.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./resources/bundled-skills/process-doc/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-organized, token-efficient instruction skill with a concrete workflow, explicit completion gates, and clear boundaries. The main gaps are the absence of any deliverable template or example and of recovery guidance when a completion gate fails.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and explains nothing Claude already knows, but the "## Purpose" section repeats the frontmatter description verbatim ("Turn an operational process into a clear SOP, role model, control map, and improvement backlog."), a minor instance of trimmable redundancy that keeps it just below the top anchor.

4 / 5

Actionability

For an instruction-only skill, the guidance is concrete and specific: each workflow step enumerates exactly what to capture ("trigger, outcome, scope, owner, participants, systems, inputs, and exceptions"; "steps, decisions, controls, handoffs, evidence, and exception routes") and the tool-routing table assigns concrete tools. It stops short of fully executable guidance because no template or example of the deliverables (SOP skeleton, RACI table shape) is provided.

4 / 5

Workflow Clarity

The five steps are clearly sequenced with an explicit ordering constraint ("Map the current state before designing the target state") and a validation checklist in the completion gates ("Walk one normal case and one exception case end to end"). It lacks a feedback loop describing what to do when a gate fails, so it fits the anchor for clear sequence with most checkpoints rather than the top anchor.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into well-labeled sections (Purpose, Tool routing, Workflow, Completion gates, Boundaries, Delivery), which per the judging guidelines merits the top score for a compact single-file skill.

5 / 5

Total

17

/

20

Passed

Description

58%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 gives a clear, concrete picture of the deliverables but reads as a capability statement rather than a trigger: there is no "Use when..." guidance and few natural keywords a user would utter when they need this skill. Adding explicit trigger conditions and synonyms would substantially raise completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause such as "Use when the user asks to document, standardize, or improve an operational process, or mentions SOPs, runbooks, RACI, or process mapping."

Add natural synonyms and user-facing terms users would actually say (e.g., "write an SOP", "runbook", "process mapping", "RACI matrix") to broaden trigger-term coverage.

State the concrete actions involved (interview stakeholders, map current state, define RACI) rather than only naming the end artifacts, to close the specificity gap.

DimensionReasoningScore

Specificity

The description names the domain ("operational process") and four concrete deliverables ("SOP, role model, control map, and improvement backlog"), matching the anchor for several specific actions with minor coverage gaps. It falls short of the top anchor because the verb "Turn... into" is generic and how each artifact is produced is unstated.

4 / 5

Completeness

It clearly answers "what" (produce an SOP, role model, control map, and improvement backlog) but contains no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. The "when" is not even weakly implied, so it cannot score 4.

3 / 5

Trigger Term Quality

Relevant keywords like "operational process" and "SOP" appear, but common natural phrases users would say ("document this process", "write a runbook", "process mapping", "RACI") are missing. It has some relevant keywords without the common variations or synonyms, fitting the middle anchor rather than the good-coverage anchor above.

3 / 5

Distinctiveness Conflict Risk

The four-artifact combination (SOP, role model, control map, improvement backlog) carves out a mostly distinct niche with only minor overlap risk against closely related documentation and writing skills. It is not fully distinct because "operational process" documentation still brushes against generic documentation skills.

4 / 5

Total

14

/

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

KunAgent/Kun

Path

resources/bundled-skills/process-doc/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.