CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lowdefy-config

Use when writing or editing Lowdefy YAML config — pages, blocks, operators, actions, connections, or requests. Looks up exact type names, schemas, and examples from the running dev server instead of guessing.

Quality

92%

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

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

An exemplarily lean, actionable skill body: exact tool names, sequencing, and operational guardrails with zero padding. The only gap is the absence of an explicit validation/feedback step after config is written.

DimensionReasoningScore

Conciseness

Roughly 23 lean lines with no explanation of concepts Claude already knows; every sentence carries project-specific facts (setup command, "never run lowdefy dev yourself", the directory parameter rule).

5 / 5

Actionability

Names exact executable MCP tool calls — `lowdefy_list_types`, `lowdefy_get_schema`, `lowdefy_get_examples`, `lowdefy_get_doc`, `lowdefy_search_docs` — each tied to a purpose, plus the `npx lowdefy agent-setup` setup command, covering the common cases for an instruction-only skill.

5 / 5

Workflow Clarity

A clear 4-step pre-write sequence with an explicit "Never guess type names or properties" checkpoint, but there is no post-write validation or error-recovery feedback loop, which the 5 anchor requires.

4 / 5

Progressive Disclosure

Under 50 lines, no external references needed, and the single section with a numbered procedure is well organized — the simple-skill case where clean organization alone earns full marks.

5 / 5

Total

19

/

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.

A strong description: third-person voice, explicit trigger clause with an enumerated scope, and a concrete anti-guessing capability statement. Only minor gaps in synonym coverage and action breadth keep it from perfect marks.

DimensionReasoningScore

Specificity

"Looks up exact type names, schemas, and examples from the running dev server" plus the enumerated "pages, blocks, operators, actions, connections, or requests" gives several concrete specifics, but the action repertoire is a single lookup capability rather than multiple distinct actions, so it falls short of the comprehensive 5 anchor.

4 / 5

Completeness

It explicitly answers "when" with concrete trigger scopes ("Use when writing or editing Lowdefy YAML config — pages, blocks, operators, actions, connections, or requests") and "what" ("Looks up exact type names, schemas, and examples from the running dev server"), matching the both-parts-explicit 5 anchor.

5 / 5

Trigger Term Quality

"Lowdefy YAML config", "pages", "blocks", "operators", "actions", "connections", "requests" are terms a Lowdefy user would naturally say, but common variations like "lowdefy.yml", "config file", or ".yml" are absent.

4 / 5

Distinctiveness Conflict Risk

"Lowdefy" names a clear niche with distinct, product-specific triggers; virtually no other skill would fire on these terms.

5 / 5

Total

18

/

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

lowdefy/lowdefy

Path

skills/lowdefy-config/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.