Name: paragon
Rating: 48.8 (1 reviews)
Author: membranedev

paragon

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

Quality

53%

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

Quality

Content

48%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 CLI guidance is concrete, executable, and reasonably well-sequenced with state-check feedback loops. The skill is undermined by a massively padded, partly duplicated overview list that bloats token cost and obscures structure.

Suggestions

Remove or relocate the 'Paragon Overview' list, especially the 120+ duplicated 'X Training' entries; keep only the entity types users actually query and move the full catalog to a references/ file.

Add a verification step after running actions or proxy requests (e.g. check the response `output`/status and confirm the record changed) to satisfy feedback-loop expectations for data operations.

Consolidate the overlapping 'Searching for actions' and 'Popular actions' sections into one discovery section to tighten the workflow.

Dimension	Reasoning	Score
Conciseness	The 'Paragon Overview' section is a ~200-line inlined list including 120+ duplicated 'X Training' entries (e.g. 'Ethics Training', 'Compliance Training', 'Sales Training' each appear twice), which is severe, heavily padded content Claude does not need.	1 / 5
Actionability	It provides copy-paste ready CLI commands for install, login, connection ensure/wait, action list/run, and proxy with a flag table, covering common cases with only minor gaps such as unresolved CONNECTION_ID placeholders.	4 / 5
Workflow Clarity	The connect workflow is a clear sequence with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop, though action-running and proxy paths lack verification steps.	4 / 5
Progressive Disclosure	Section headers provide structure, but the giant inlined entity/training list is content that belongs in a separate reference file or should be trimmed, and no external references are signaled; the skill is well over 50 lines so the simple-skill exception does not apply.	3 / 5
	Total	12 / 20 Passed

Description

57%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 has an explicit 'Use when...' trigger and a clearly named niche (Paragon), giving solid completeness and distinctiveness. It is held back by generic, non-concrete action phrasing and limited trigger-term variety.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Search and retrieve candidate, job, and application records; run Paragon workflows; sync data across integrations.'

Add natural trigger synonyms and entity terms users would say, such as 'candidates', 'requisitions', 'job posts', or 'ATS data'.

Make the 'when' clause more specific, e.g. 'Use when the user wants to query or update Paragon/ATS records or trigger Paragon workflows.'

Dimension	Reasoning	Score
Specificity	The description names the domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, matching the 'names the domain but actions are minimal or generic' anchor rather than the concrete-actions anchor at 3.	2 / 5
Completeness	It answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Paragon data'), but the 'what' is not concrete enough to reach the fully explicit anchor at 5.	4 / 5
Trigger Term Quality	It includes the distinctive keyword 'Paragon' plus 'data', 'records', and 'workflows', but the supporting terms are generic and it lacks common synonyms or variations a user might naturally say.	3 / 5
Distinctiveness Conflict Risk	'Paragon' is a clearly named niche with a distinct trigger, but the generic 'manage data, records, automate workflows' phrasing creates minor overlap risk with other data-management skills.	4 / 5
	Total	13 / 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/paragon/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.