CtrlK
BlogDocsLog inGet started
Tessl Logo

repuso

Repuso integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Repuso 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/repuso/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 content is a well-structured, actionable guide with concrete commands and a clear validated connection workflow, held back by a padded marketing intro and a monolithic single-file structure.

Suggestions

Cut the marketing intro ('helps businesses build trust and increase sales…') and the 'so you can focus on the integration logic' editorializing to respect token budget.

Resolve the dangling 'skip to Step 2' reference by adding an explicit numbered Step 2 heading for the action-search/run phase.

Flesh out the 'Popular actions' section with a few concrete example actions or remove the heading to avoid the thin placeholder.

DimensionReasoningScore

Conciseness

The body is mostly efficient and command-driven, but the marketing-flavored intro ('social proof platform that helps businesses build trust and increase sales…') and editorializing like 'so you can focus on the integration logic rather than auth plumbing' could be trimmed.

3 / 5

Actionability

Concrete copy-paste commands cover install, auth, connection, action discovery/execution, and proxying, with a thorough proxy flag table; the thin 'Popular actions' section leaves a minor gap.

4 / 5

Workflow Clarity

The install→auth→connect→poll→search→run→proxy sequence is clear with an explicit connection state machine and feedback loops (poll until READY, handle clientAction), though the dangling 'skip to Step 2' reference is a minor gap.

4 / 5

Progressive Disclosure

The single file is well-organized into clearly headed sections with no nested references, but it is a monolithic ~150-line document with no content split into separate reference files.

4 / 5

Total

15

/

20

Passed

Description

70%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 the domain and provides an explicit 'Use when' trigger with a concrete entity list, but the single generic verb 'Manage' limits action specificity and the trigger phrasing is broad.

Suggestions

Replace the generic verb 'Manage' with more specific concrete actions (e.g., 'create, update, and query Persons, Organizations, Deals…').

Tighten the 'when' clause to reference concrete Repuso-specific triggers such as 'reviews', 'testimonials', or 'social proof' that users would naturally say.

Drop the vague 'and more' tail or enumerate the remaining capabilities so coverage reads as comprehensive.

DimensionReasoningScore

Specificity

The description lists many concrete entities (Persons, Organizations, Deals, Leads, Projects, Activities) but relies on a single generic verb 'Manage', so the action vocabulary is limited rather than comprehensive.

3 / 5

Completeness

Both a 'what' (manage the listed Repuso entities) and an explicit 'Use when the user wants to interact with Repuso data' trigger are present, though the 'when' is somewhat generic.

4 / 5

Trigger Term Quality

The brand name 'Repuso' plus concrete entity nouns (Deals, Leads, Persons) give good keyword coverage, though natural product terms like 'reviews' or 'testimonials' are missing.

4 / 5

Distinctiveness Conflict Risk

The named Repuso SaaS niche is mostly distinct with low conflict risk, but generic CRM-style entity nouns (Deals, Leads, Organizations) create minor overlap with related skills.

4 / 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.