CtrlK
BlogDocsLog inGet started
Tessl Logo

ramco-systems

Ramco Systems integration. Manage data, records, and automate workflows. Use when the user wants to interact with Ramco Systems 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/ramco-systems/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 highly actionable, well-structured integration guide with concrete CLI commands and a validated connection workflow. Minor conciseness and organization improvements are possible but it is strong overall.

DimensionReasoningScore

Conciseness

The body is mostly lean with executable commands, but includes minor padding such as the opening 'Ramco Systems is a cloud enterprise software provider...' sentence and a duplicated action-list command under 'Popular actions', fitting the score-4 anchor of efficient content with minor trims possible.

4 / 5

Actionability

Commands are copy-paste ready with flags and a JSON input example covering connection setup, action discovery, action execution, and proxying, matching the score-5 anchor of fully executable guidance covering common cases.

5 / 5

Workflow Clarity

The connection workflow is clearly sequenced with state-checking checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/error states) and a poll loop, but 'Step 2' is referenced without a matching labeled section and destructive data operations lack explicit validation, so it sits below the score-5 anchor.

4 / 5

Progressive Disclosure

A single self-contained file with well-organized headers and no nested references; the 26-item entity list and API details are borderline content that could be split into a reference file, placing it just below the score-5 anchor.

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 clearly names a distinct product and provides an explicit 'Use when' trigger, but its action list ('Manage data, records, and automate workflows') is generic rather than concrete. It is solid and trigger-complete but could be more specific about capabilities.

Suggestions

Replace generic verbs with concrete operations, e.g. 'Create, update, and query employee, leave, timesheet, and expense records; automate approval workflows.'

Add natural trigger synonyms users might say, such as 'Ramco', 'Ramco ERP', or specific entity names like 'leave' or 'timesheet'.

Tie the 'Use when' clause to more concrete intents, e.g. 'Use when the user wants to manage Ramco ERP records, leave, timesheets, or approvals.'

DimensionReasoningScore

Specificity

Names the domain (Ramco Systems) plus a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic verbs rather than concrete operations, matching the score-3 anchor of domain + 1-2 actions that are not comprehensive.

3 / 5

Completeness

Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Ramco Systems data') are present and explicit; the 'what' is somewhat generic so it does not reach the fully concrete score-5 anchor.

4 / 5

Trigger Term Quality

'Ramco Systems' and 'interact with Ramco Systems data' are relevant natural terms, but common variations or synonyms are missing, fitting the score-3 anchor of some relevant keywords without full coverage.

3 / 5

Distinctiveness Conflict Risk

Ramco Systems is a specific named product giving a clear niche with a distinct trigger phrase and minimal conflict risk with other skills, matching the score-5 anchor.

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.