CtrlK
BlogDocsLog inGet started
Tessl Logo

icims

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

57

Quality

66%

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

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 body is action-oriented with executable CLI commands and a well-sequenced connection workflow including validation checkpoints. It loses points mainly to a padded intro and minor redundancy/labeling gaps rather than to any structural problem.

Suggestions

Trim the introductory 'iCIMS is a talent acquisition platform...' paragraph and remove filler like 'Use action names and parameters as needed.'

Define 'Step 2' explicitly or remove the dangling cross-references to it.

Merge the redundant 'Popular actions' discovery command into the 'Searching for actions' section.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands, but the opening paragraph explains what iCIMS is and lines like 'Use action names and parameters as needed.' add little; could be tightened.

3 / 5

Actionability

Provides concrete, copy-paste-ready commands (install, login, connection ensure, action list/run, request) plus a flags table, with only minor gaps like the unresolved CONNECTION_ID placeholder.

4 / 5

Workflow Clarity

Clear sequence from install through authenticate, connect, poll-to-ready, search, and run, with explicit state checkpoints and a poll-again feedback loop; minor gaps such as the undefined 'Step 2' label.

4 / 5

Progressive Disclosure

Well-organized into clear sections with no bundle files to reference; the inline flags table and clientAction detail are reasonable in SKILL.md, though the 'Popular actions' section slightly duplicates 'Searching for actions'.

4 / 5

Total

15

/

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 is concise and third-person, with an explicit 'Use when' trigger and a clearly distinct iCIMS niche. Its main weakness is generic action verbs and limited trigger-term variation rather than concrete recruiting-specific operations.

Suggestions

Replace generic verbs with concrete iCIMS operations, e.g. 'Search applicants, manage job postings, and pull recruiting reports'.

Broaden trigger terms to include natural user phrasing like 'recruiting', 'applicants', 'job postings', or 'hiring data'.

DimensionReasoningScore

Specificity

Names the domain ('iCIMS integration') and a few actions ('Manage data, records, and automate workflows'), but the actions are generic and not the concrete iCIMS-specific operations (applicant tracking, job search, reporting) hinted at in the body.

3 / 5

Completeness

Answers both 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with iCIMS data'), but the 'when' could be more specific about the recruiting/hiring scenarios.

4 / 5

Trigger Term Quality

Includes the natural term 'iCIMS' and the trigger phrase 'Use when the user wants to interact with iCIMS data', but lacks common variations/synonyms a user might say (recruiting, applicants, hiring, jobs).

3 / 5

Distinctiveness Conflict Risk

iCIMS is a specific named platform, giving it a clear niche with distinct triggers and minimal overlap risk with 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.