Name: raisely
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

raisely

Raisely integration. Manage Organizations. Use when the user wants to interact with Raisely data.

Quality

70%

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

Quality

Content

78%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 delivers highly actionable, executable CLI guidance with a clear connection-state workflow and a clean section structure. Its main weakness is moderate verbosity from a domain overview and restated best-practice bullets, plus an undefined 'Step 2' reference.

Suggestions

Trim the Raisely platform overview paragraph and softening phrases that do not add executable guidance.

Define or relabel 'Step 2' (the reference appears but no Step 2 heading exists) and merge the redundant 'Popular actions' section into 'Searching for actions'.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands and a useful flag table, but includes removable padding such as the Raisely domain overview and softening sentences like 'so you can focus on the integration logic rather than auth plumbing'. Not 4 because several sentences are unnecessary explanation.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands for install, login, connection, action discovery/execution, and proxying, with a complete flag table covering common cases. Matches the anchor for fully executable guidance.	5 / 5
Workflow Clarity	Clear sequenced flow (install, login, connection ensure, wait/branch on state, search, run) with explicit state checkpoints and a poll-after-action feedback loop. Not 5 because 'Step 2' is referenced but never defined and the 'Popular actions' section repeats the prior search guidance.	4 / 5
Progressive Disclosure	Single self-contained SKILL.md with no external references needed, organized into clear, navigable sections per the simple-skill exception. Well-structured and easy to navigate.	5 / 5
	Total	17 / 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 correctly states both what the skill does and when to use it, anchored to a clearly distinct named app. It is held back by thin action coverage and a generic trigger phrase lacking synonyms.

Suggestions

Expand the action list beyond 'Manage Organizations' to concrete capabilities (e.g., manage campaigns, donations, events, fundraisers, people).

Broaden the trigger phrase with natural synonyms users would say, e.g. 'Use when the user wants to manage Raisely campaigns, donations, events, or supporter data.'

Dimension	Reasoning	Score
Specificity	Names the Raisely domain and one concrete action ('Manage Organizations'), but coverage is not comprehensive. Not 4 because only a single action is enumerated rather than several.	3 / 5
Completeness	Has both a 'what' ('Raisely integration. Manage Organizations.') and an explicit 'when' ('Use when the user wants to interact with Raisely data'). Not 5 because the trigger phrase is generic without concrete synonym-rich triggers.	4 / 5
Trigger Term Quality	Includes domain keywords ('Raisely', 'Organizations') and a 'Use when' trigger, but lacks common variations or synonyms like fundraising, donations, events, or campaigns. Not 4 because keyword coverage remains thin.	3 / 5
Distinctiveness Conflict Risk	Raisely is a named, distinct app giving a clear niche with minimal conflict risk. Not 5 because 'Manage Organizations' and the generic trigger slightly overlap with general org-management 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/raisely/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.