CtrlK
BlogDocsLog inGet started
Tessl Logo

siyuan

Query and edit a SiYuan knowledge base via its API.

60

Quality

71%

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 ./optional-skills/productivity/siyuan/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

90%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 lean, highly actionable API reference with executable curl examples for every common operation and solid validation guidance in the Pitfalls section, with only minor gaps in inline workflow checkpoints and no external reference splitting.

DimensionReasoningScore

Conciseness

The body is almost entirely copy-paste curl commands, a quick-reference table, and tightly written notes; it avoids explaining concepts Claude already knows and every line serves a purpose, matching the lean/efficient anchor.

5 / 5

Actionability

Every operation ships as a complete, executable curl command with headers, JSON body, and a jq pipeline, covering search, read, create, update, delete, and export across the common cases.

5 / 5

Workflow Clarity

Operations are clearly catalogued and a Pitfalls section supplies validation guidance (check code != 0, ID pattern validation, SQL safety), but explicit inline checkpoints or validate-then-retry feedback loops are not woven into each destructive example, leaving a minor gap.

4 / 5

Progressive Disclosure

Content is well-organized into clear sections with a Quick Reference navigation table and an optional MCP alternative, but everything lives in a single ~275-line file with no external references, so it sits just below the top anchor for one-level-deep reference splitting.

4 / 5

Total

18

/

20

Passed

Description

53%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 concise, third-person, and names a distinct niche with two concrete actions, but it lacks a "Use when..." trigger clause and broader natural synonyms, which limits completeness and trigger-term quality to mid-range scores.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to search, read, or edit notes in a SiYuan knowledge base."

Broaden trigger terms with natural synonyms like "notes", "PKM", or "SiYuan blocks/documents".

Expand the action list slightly (e.g. "search, read, create, update, and delete blocks and documents") to lift specificity.

DimensionReasoningScore

Specificity

Names the domain ("SiYuan knowledge base") and two concrete actions ("Query and edit") but stops at a high-level pairing without enumerating specific operations, matching the anchor for 1-2 concrete actions that are not comprehensive.

3 / 5

Completeness

Clearly states what the skill does but provides no "Use when..." trigger clause, so per the judging guidelines completeness is capped at 3 for a clear what with missing or only weakly implied when.

3 / 5

Trigger Term Quality

Includes relevant keywords ("SiYuan", "knowledge base", "API") but omits natural synonyms a user would say such as "notes", "PKM", or file-type terms, fitting the anchor for some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

"SiYuan knowledge base via its API" carves a clear, narrow niche unlikely to fire for unrelated skills, though the absence of an explicit trigger phrase keeps it just below the top anchor.

4 / 5

Total

13

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
NousResearch/hermes-agent
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.