CtrlK
BlogDocsLog inGet started
Tessl Logo

cornerstone-talentlink

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

60

Quality

70%

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

Quality

Content

75%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 highly actionable with concrete CLI commands and a well-validated connection workflow, but it carries some explanatory padding and inlines reference-grade detail that could be split out.

Suggestions

Trim the introductory paragraph and editorializing phrases ('so you can focus on the integration logic') to respect the token budget.

Add a brief validation/check step after running or proxying mutating actions (e.g. re-fetch the record to confirm the change) so destructive operations have a feedback loop.

Consider moving the clientAction schema detail and proxy flags table into a references/ file, keeping SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

Mostly efficient with executable commands throughout, but padded with unnecessary prose such as the introductory paragraph defining what TalentLink is and phrases like 'so you can focus on the integration logic rather than auth plumbing'.

3 / 5

Actionability

Fully executable, copy-paste-ready commands cover the common cases (install, interactive and headless auth, connection ensure with --wait polling, action list/run with JSON input, proxy requests with a flags table).

5 / 5

Workflow Clarity

The connection setup is a clearly sequenced flow with explicit state-based checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED) and a poll-again feedback loop, though the action-running and proxy sections lack validation guidance for destructive operations.

4 / 5

Progressive Disclosure

Well-organized into clear section headers with no nested references, but all detail (the full clientAction schema, proxy flags table) is inlined in a single ~140-line file rather than split into reference files.

4 / 5

Total

16

/

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 well-formed with a third-person voice, an explicit trigger clause, and a distinctive product name, but its action list is generic and its trigger terms lack the recruiting-domain synonyms a user would naturally say.

Suggestions

Replace generic verbs ('Manage data, records') with concrete capabilities such as 'search candidates, manage requisitions, and update applications'.

Expand the trigger clause to include natural recruiting phrases, e.g. 'Use when the user wants to work with candidates, applications, requisitions, or hiring workflows in Cornerstone TalentLink.'

DimensionReasoningScore

Specificity

Names the domain ('Cornerstone TalentLink') and a few actions ('Manage data, records, and automate workflows'), but the actions are high-level and generic rather than comprehensive concrete capabilities.

3 / 5

Completeness

Provides both a clear 'what' (integration that manages data, records, workflows) and an explicit 'when' ('Use when the user wants to interact with Cornerstone TalentLink data'), though the when clause could name concrete recruiting scenarios.

4 / 5

Trigger Term Quality

Includes the core product keyword and a 'Use when... interact with Cornerstone TalentLink data' trigger, but misses natural synonyms users would say like recruiting, hiring, candidates, or requisitions.

3 / 5

Distinctiveness Conflict Risk

Naming the specific product 'Cornerstone TalentLink' creates a clear niche with distinct triggers and minimal risk of conflicting 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.