Name: progress-sitefinity
Rating: 56.8 (1 reviews)
Author: membranedev

progress-sitefinity

Progress Sitefinity integration. Manage data, records, and automate workflows. Use when the user wants to interact with Progress Sitefinity data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/progress-sitefinity/SKILL.md

Quality

Content

68%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 content is highly actionable with copy-paste commands and a solid connection workflow, but it is padded with an unnecessary CMS intro and lacks validation checkpoints for destructive data operations.

Suggestions

Trim the opening CMS explainer and promotional phrasing; Claude already knows what a CMS is, so lead directly with what the skill does.

Add a validation/verification step around destructive operations, e.g. list or GET a record before running a DELETE/proxy call, and confirm the result afterward, to lift workflow clarity above the destructive-operation cap.

Fix the dangling 'Step 2' reference (there is no labeled Step 1/Step 2) and remove the redundant 'Popular actions' section that repeats the earlier action-list command.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-driven prose, but the opening CMS explainer ('Progress Sitefinity is a content management system...') and promotional lines like 'so you can focus on the integration logic rather than auth plumbing' are padding Claude does not need.	3 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login, connection ensure, action list/run with --input, request) plus a comprehensive proxy flag table, matching 'fully executable; copy-paste ready; covers common cases'.	5 / 5
Workflow Clarity	The connection flow has a clear state-based sequence with polling checkpoints, but data-modifying operations (action run, proxy with DELETE) lack any validation/verification steps, and the destructive/batch cap holds workflow clarity at 3.	3 / 5
Progressive Disclosure	No bundle files exist, so disclosure is judged on section organization; the body is cleanly sectioned with clear headers and the proxy flag table is reasonably placed inline, fitting 'good structure; most content appropriately placed; minor gaps'.	4 / 5
	Total	15 / 20 Passed

Description

62%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 well-formed in third person with an explicit 'Use when' trigger and a named product niche, but its action list is generic rather than concrete and trigger terms are limited to the product name.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Sitefinity actions, e.g. 'Create and publish pages, news, and blog posts; manage content blocks, lists, and forms'.

Add natural trigger synonyms users might say, such as 'Sitefinity CMS', 'Sitefinity content', or specific entities like 'pages', 'news', 'forms'.

Tighten the 'when' clause to reference concrete Sitefinity tasks (e.g. 'Use when the user wants to publish or edit Sitefinity pages, news, blogs, or forms') to reach the explicit-concrete-trigger anchor.

Dimension	Reasoning	Score
Specificity	Names the domain ('Progress Sitefinity integration') and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, fitting the '1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	It answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Progress Sitefinity data'), but the 'what' is somewhat generic, keeping it just below the explicit-concrete-trigger anchor 5.	4 / 5
Trigger Term Quality	The only natural trigger keyword is the product name 'Progress Sitefinity' (and 'Sitefinity data'); common variations or synonyms are missing, matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Progress Sitefinity' gives it a clear niche with low conflict risk, but the generic 'manage data, records, and automate workflows' phrasing leaves minor overlap risk with other integration skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/progress-sitefinity/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.