CtrlK
BlogDocsLog inGet started
Tessl Logo

sitecreatorio

Sitecreator.io integration. Manage Sites, Pages, Templates, Images, Domains, Users and more. Use when the user wants to interact with Sitecreator.io data.

64

Quality

76%

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 ./skills/sitecreatorio/SKILL.md
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.

The body is actionable and well-structured with a strong, validated connection workflow. It is slightly held back by minor redundancy and some inline reference material that could be externalized.

Suggestions

Deduplicate the action-list command between 'Searching for actions' and 'Popular actions' and remove the filler line 'Use action names and parameters as needed.'.

Add explicit validation/checkpoints for the action-run and proxy-request flows (e.g., check the output/error field before proceeding, confirm destructive action IDs before running).

Move the proxy flag table and clientAction field reference into a separate reference file and link to it from SKILL.md.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands and brief, non-generic explanations, though the 'Searching for actions' and 'Popular actions' sections repeat the action-list command and 'Use action names and parameters as needed.' is filler.

4 / 5

Actionability

It provides concrete, copy-paste-ready commands (install, login, connection ensure, action run, request with a complete flag table) covering common cases, with only minor placeholder gaps (CONNECTION_ID, <actionId>).

4 / 5

Workflow Clarity

The connection setup is clearly sequenced with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a feedback loop (poll again after user action), but running actions and proxy requests lack comparable validation guidance.

4 / 5

Progressive Disclosure

Content is well-organized into clear sections with no nested references and a single external-docs link, though some inline material (the proxy flag table, detailed clientAction schema) could be split into reference files given the ~140-line length.

4 / 5

Total

16

/

20

Passed

Description

78%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 clearly conveys the skill's niche and lists concrete managed entities with an explicit use-when clause. It is strong on distinctiveness but could improve the 'when' trigger phrases and use more varied action verbs.

Suggestions

Replace the single generic verb 'Manage' with a few distinct action verbs (e.g., create, edit, list, delete) to sharpen specificity.

Expand the 'Use when...' clause with concrete trigger phrases users would naturally say, such as 'when the user wants to create a page, list templates, or manage domains in Sitecreator.io'.

DimensionReasoningScore

Specificity

It enumerates multiple concrete capabilities (Sites, Pages, Templates, Images, Domains, Users) but relies on the single generic verb 'Manage', leaving minor coverage gaps in distinguishing actions, so just above the midpoint.

4 / 5

Completeness

It answers both 'what' (Sitecreator.io integration managing the listed entities) and 'when' ('Use when the user wants to interact with Sitecreator.io data'), but the 'when' clause is a single narrow trigger rather than multiple concrete trigger phrases.

4 / 5

Trigger Term Quality

Good keyword coverage including the product name and natural entity nouns (Sites, Pages, Templates, Images, Domains, Users) that users would say, though a few natural synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

It targets a clear niche (Sitecreator.io) with product-specific triggers, giving it minimal overlap risk with other skills.

5 / 5

Total

17

/

20

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
membranedev/application-skills
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.