CtrlK
BlogDocsLog inGet started
Tessl Logo

add-enrichment

Add a code-defined table enrichment (registry entry) under `apps/sim/enrichments/` backed by an ordered provider cascade, ensuring every provider tool it calls has hosted-key support. Use when adding a per-row table enrichment that fills cells via existing Sim tools.

68

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

A well-structured, actionable skill body with strong workflow sequencing and validation checkpoints appropriate to a batch per-row operation. Conciseness and progressive disclosure are solid but not maximal due to inline code bulk and a few explanatory passages.

Suggestions

Tighten the 'Why it matters' paragraph in Step 2 to a one-line rationale so the hosted-key gate stays the focus.

Consider moving the full EnrichmentConfig example into a references/ template file and showing a trimmed version inline to improve progressive disclosure.

Add a short note clarifying which placeholder values ({name}, SomeIcon, toolId) the user must replace versus which are literal.

DimensionReasoningScore

Conciseness

Dense and technical, assuming Claude's competence (no basic concept explanations), with necessary Sim-specific architecture stated inline; a few explanatory passages like the 'Why it matters' rationale in Step 2 could be trimmed slightly.

4 / 5

Actionability

Provides copy-paste-ready EnrichmentConfig, registry, index.ts, and hosting-block examples plus concrete commands (bun run type-check, bunx biome check) and exact paths; minor gaps remain via template placeholders ({name}, SomeIcon, service_action) that the user must substitute.

4 / 5

Workflow Clarity

Five steps are clearly sequenced in an overview table with an explicit required gate in Step 2 (stop and run /add-hosted-key) and a verification step with feedback signals in Step 5 (cell fills, dev-server log, blank-vs-error rows), plus a checklist.

5 / 5

Progressive Disclosure

Well-organized into Overview, Architecture, Steps 1–5, and Checklist with no nested references; the long inline code example and architecture block are justified for a self-contained skill, though the body is heavier than a lean overview.

4 / 5

Total

17

/

20

Passed

Description

87%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.

A strong, specific description that covers what and when with concrete, third-person phrasing and a clear niche. Trigger-term synonyms could be richer, but distinctiveness and completeness are excellent.

DimensionReasoningScore

Specificity

Names the domain ('code-defined table enrichment', 'registry entry under apps/sim/enrichments/') and several concrete actions (ordered provider cascade, ensuring hosted-key support, filling cells via existing tools); minor gaps such as registration/verification are not surfaced.

4 / 5

Completeness

Explicitly answers both what ('Add a code-defined table enrichment... backed by an ordered provider cascade, ensuring every provider tool it calls has hosted-key support') and when ('Use when adding a per-row table enrichment that fills cells via existing Sim tools') with concrete trigger phrasing.

5 / 5

Trigger Term Quality

'Use when adding a per-row table enrichment that fills cells via existing Sim tools' covers natural trigger phrases ('table enrichment', 'per-row', 'fills cells') a user would say, though synonyms and alternative phrasings are thin.

4 / 5

Distinctiveness Conflict Risk

The niche is narrow and specific — code-defined per-row table enrichments under a fixed path with a provider cascade and hosted-key constraint — making conflict with unrelated skills unlikely.

5 / 5

Total

18

/

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
simstudioai/sim
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.