CtrlK
BlogDocsLog inGet started
Tessl Logo

srxp

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

62

Quality

74%

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/srxp/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 a lean, highly actionable CLI integration guide with clear workflow sequencing and explicit state-handling checkpoints, weakened only slightly by light introductory padding and lack of progressive file splitting.

DimensionReasoningScore

Conciseness

Largely efficient with code blocks, a flag table, and minimal prose, though the opening context paragraph and filler like 'Use action names and parameters as needed' could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) plus a concrete proxy flag table covering common cases.

5 / 5

Workflow Clarity

Clear sequence from install → auth → connect → search → run, with an explicit polling/state-checkpoint loop (BUILDING → READY / CLIENT_ACTION_REQUIRED) and retry guidance; minor validation gaps only.

4 / 5

Progressive Disclosure

Single self-contained SKILL.md with well-organized sections and no nested references; content is appropriately placed inline, though the connection state-machine and proxy reference could optionally be split out.

4 / 5

Total

17

/

20

Passed

Description

66%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...' clause and names a distinct product, but the capability verbs ('manage data, records, automate workflows') are generic and lack concrete, spend-specific triggers.

Suggestions

Replace generic verbs with concrete SRXP actions, e.g. 'Create expense reports, submit and approve expenses, and manage budgets'.

Add natural trigger terms users actually say: 'expenses', 'spend management', 'expense reports', 'reimbursements'.

Tie the 'Use when' clause to those spend/expense triggers rather than the abstract 'interact with SRXP data'.

DimensionReasoningScore

Specificity

Names the domain (SRXP) and lists actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete, so it lands at 'names domain and 1-2 actions, not comprehensive'.

3 / 5

Completeness

Both 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with SRXP data') are present and explicit, though the 'what' is somewhat generic.

4 / 5

Trigger Term Quality

Provides 'SRXP' and the natural phrase 'interact with SRXP data', but omits common synonyms a user would actually say (expenses, spend management, expense reports) found in the body.

3 / 5

Distinctiveness Conflict Risk

Names the specific product SRXP with a dedicated trigger phrase, giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

15

/

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.