CtrlK
BlogDocsLog inGet started
Tessl Logo

proxycurl

Proxycurl integration. Manage Persons, Organizations, Jobs, Profiles. Use when the user wants to interact with Proxycurl data.

59

Quality

68%

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

Quality

Content

76%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 actionable and well-structured with executable commands, but the workflow lacks validation/verification checkpoints after data operations, and some content (the full API list) could be moved to a reference file. Adding verify-steps and trimming editorial asides would raise the score.

Suggestions

Add validation checkpoints after running actions or proxy requests, e.g. inspect the JSON output for errors and confirm the expected fields before proceeding.

Move the full Proxycurl API endpoint listing into a reference file and keep SKILL.md as a concise overview pointing to it.

Trim editorializing ('so you can focus on the integration logic rather than auth plumbing', 'burn less tokens') to keep the body token-efficient.

DimensionReasoningScore

Conciseness

The body is mostly lean with short command blocks and a bullet API list, but includes minor editorializing ('so you can focus on the integration logic', 'burn less tokens') that could be trimmed.

4 / 5

Actionability

Concrete, copy-paste-ready commands are provided throughout (install, login, connect, action list/run, proxy flags table), covering the common cases of the CLI workflow.

5 / 5

Workflow Clarity

The install-to-run sequence is clearly ordered, but there are no validation or verification checkpoints after running actions or proxy requests, which the rubric caps at 3 for destructive or batch-capable operations.

3 / 5

Progressive Disclosure

A single well-organized SKILL.md with clear section headers and no bundle files; the inline 18-item API overview is reasonable but is bulk that could be split into a reference file, keeping it below a clean 5.

4 / 5

Total

16

/

20

Passed

Description

61%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 clear and distinct thanks to the named product, and covers both what and when, but its action verbs are generic and it lacks concrete trigger phrases and synonyms. Tightening the verbs and adding natural keywords would lift specificity and trigger quality.

Suggestions

Replace the generic verb 'Manage' with concrete operations, e.g. 'Retrieve person and company profiles, search jobs, look up emails and phone numbers'.

Add natural trigger synonyms users actually say, such as 'LinkedIn profiles, company data, professional enrichment'.

Make the 'Use when...' clause more concrete, e.g. 'Use when the user asks for LinkedIn profile data, company information, or person/job searches via Proxycurl'.

DimensionReasoningScore

Specificity

The description names the domain and objects ('Manage Persons, Organizations, Jobs, Profiles') but the only action verbs are generic ('Manage', 'interact'), with no concrete operation described.

2 / 5

Completeness

Both a clear 'what' (manage Persons/Organizations/Jobs/Profiles) and an explicit 'when' ('Use when the user wants to interact with Proxycurl data') are present, though the 'when' is generic rather than concrete.

4 / 5

Trigger Term Quality

'Proxycurl' plus the object nouns provide some relevant keywords, but natural user phrasings and synonyms (LinkedIn, company, enrichment) are missing.

3 / 5

Distinctiveness Conflict Risk

Naming a specific niche product (Proxycurl) gives it a clear distinct trigger with minimal risk of firing for an unrelated skill.

5 / 5

Total

14

/

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.