CtrlK
BlogDocsLog inGet started
Tessl Logo

project-ops-skill

Triggered when the user wants to create, open, switch, move, delete, or rename OpenLoaf's "project" entity. Typical phrasings: "new project", "add ~/code/foo", "list all projects". **Not for**: reading/writing files inside a project (→ use Read/Edit/Write directly), discussing "project planning / requirement docs" (→ answer directly), routine Git operations (→ `Bash`).

69

Quality

83%

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

75%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 tight, actionable operational guide with concrete tool calls, decision flows, and guardrails for the risky remove/URI operations. It falls just short of top marks because URI conversion lacks a full executable example, there is no validate-retry loop, and all content is inline.

Suggestions

Add one complete executable `ProjectMutate { action: "create", rootUri: "file:///Users/user/code/repo", ... }` example so the file:// URI conversion is copy-paste ready rather than prose.

For destructive/batch paths, add an explicit validate→fix→retry checkpoint (e.g., re-run `ProjectQuery { mode: "get" }` after `remove` to confirm the record is gone).

Tighten the rootUri guardrail prose — keep the "three slashes = file:// + /" mnemonic and drop the explanatory sentence about cross-platform URI standards.

DimensionReasoningScore

Conciseness

The body is lean — tables, short examples, and a decision flow with no padding of concepts Claude already knows — though the rootUri prose ("The cross-platform URI standard requires the protocol prefix...") could be trimmed.

4 / 5

Actionability

Copy-paste-ready calls like `ProjectMutate { action: "create", title: "Q2 Marketing", ... }` cover every action, but the file:// URI conversion is shown as prose steps rather than a complete executable create-call example.

4 / 5

Workflow Clarity

A decision flow, end-to-end flows, and a "query first to confirm projectId" checkpoint sequence the work clearly; the destructive `remove` is safety-framed, but there is no explicit validate→fix→retry feedback loop to reach a 5.

4 / 5

Progressive Disclosure

No bundle files exist and the single SKILL.md is well-organized into clearly headed sections with no nested references, but at ~80 lines of inline content it sits above the simple-skill threshold that would let well-organized sections alone score 5.

4 / 5

Total

16

/

20

Passed

Description

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

A strong, third-person description that names concrete actions, gives natural trigger phrasings, and explicitly carves out exclusions to avoid misfires. Trigger-term coverage is the only mild weakness, missing a few obvious operation synonyms.

DimensionReasoningScore

Specificity

The description lists six concrete actions on the project entity — "create, open, switch, move, delete, or rename" — giving comprehensive coverage rather than vague language.

5 / 5

Completeness

It explicitly answers both what (operations on OpenLoaf's project entity) and when ("Triggered when the user wants to..." plus concrete Typical phrasings), with explicit Not-for exclusions.

5 / 5

Trigger Term Quality

It supplies natural phrasings users would actually say ("new project", "add ~/code/foo", "list all projects"), but a few common variations like "open/delete/rename project" are not enumerated.

4 / 5

Distinctiveness Conflict Risk

The "Not for" clause disambiguates file I/O, planning docs, and Git ops by routing them to Read/Edit/Write, direct answers, and Bash, giving a clear niche with minimal conflict risk.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
itsablabla/openloaf-web
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.