Name: celoxis
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

celoxis

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

Quality

64%

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

Quality

Content

67%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 a well-structured, largely executable guide with a clear connection workflow and feedback loop. Its main weaknesses are a slightly redundant introductory overview and the absence of explicit verification steps for create/update operations.

Suggestions

Trim or remove the opening 'Celoxis is a project management...' paragraph and the 'It's used by medium to large-sized businesses' background to improve token efficiency.

Add an explicit verification step after create/update actions (e.g., re-fetch the record or check the response status) to strengthen the workflow's feedback loop for destructive operations.

Include at least one complete 'action run' example with realistic parameter values (a real entity ID and input JSON) so the common case is fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but the opening overview ('Celoxis is a project management and resource management software. It's used by medium to large-sized businesses...') explains background Claude largely already knows and could be trimmed, fitting the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	Concrete, executable commands贯穿 install, auth, connection, search, run, and proxy flows with a flag table, but examples rely on placeholders (CONNECTION_ID, <actionId>, {"key": "value"}) with no complete real-parameter example, leaving minor gaps below the fully copy-paste-ready level 5.	4 / 5
Workflow Clarity	The connection setup is a clearly sequenced workflow with an explicit polling feedback loop and enumerated states (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR, SETUP_FAILED), but create/update operations lack an explicit verification checkpoint, capping it just below level 5.	4 / 5
Progressive Disclosure	No bundle files exist, and the body is well-organized into clear sections (overview, install, auth, connecting, actions, proxy, best practices); the inline actions table and proxy flags are reasonable inline content, matching the 'good structure, minor organization gaps' anchor.	4 / 5
	Total	15 / 20 Passed

Description

61%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 distinct and correctly pairs a 'what' with an explicit 'Use when' trigger, but its capability verbs are generic and its trigger vocabulary is limited to the product name. Tightening the action list to concrete operations and adding entity keywords would lift specificity and trigger quality.

Suggestions

Replace generic verbs with concrete operations, e.g. 'List, create, and update Celoxis projects, tasks, and time entries' to raise specificity.

Add the natural entity terms users say (projects, tasks, timesheets, resources, issues) to broaden trigger-term coverage beyond just 'Celoxis'.

Sharpen the 'when' clause to name the scenarios, e.g. 'Use when the user wants to query or update Celoxis projects, tasks, timesheets, or resources.'

Dimension	Reasoning	Score
Specificity	Names the domain (Celoxis) but the actions are generic verbs ('Manage data, records, and automate workflows') with no concrete operations, matching the 'actions are minimal or generic' anchor rather than the 1-2 concrete actions at level 3.	2 / 5
Completeness	Both a 'what' (Celoxis integration, manage data/records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Celoxis data') are present, though the 'what' could be more specific — matching the level-4 anchor.	4 / 5
Trigger Term Quality	The only natural keyword is the product name 'Celoxis' / 'Celoxis data'; it lacks common variations or the entity terms (projects, tasks, timesheets) users would actually say, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Tied to a named product (Celoxis) with a distinct trigger, giving a clear niche and minimal conflict risk with other skills.	5 / 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/celoxis/SKILL.md
Commit: f484c82

Reviewed: 4 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.