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.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%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 highly actionable, well-sequenced workflow skill: concrete code, exact commands, a required validation gate, and a checklist. The only weaknesses are mild redundancy in Step 2 and no use of bundle files to slim the main document.

Suggestions

Collapse Step 2's 'Why it matters' paragraph into the hosting-absent bullet — both explain the same no-hosting → no-billing → blank-cells chain, so one statement suffices.

Move the full EnrichmentConfig code template (Step 3) into a references/ file (e.g. references/enrichment-template.md) and keep a minimal skeleton inline, shortening SKILL.md to an overview plus the gate.

Dimension	Reasoning	Score
Conciseness	Lean and Claude-respecting throughout — it explains only Sim-specific internals (cascade runner, hosting blocks, client-safety rules) — but Step 2 states the no-hosting consequence twice ("silently produce blank cells" then the "Why it matters" paragraph re-deriving the same chain), which could be trimmed to one.	4 / 5
Actionability	Fully executable: a copy-paste-ready EnrichmentConfig template with exact import paths, the concrete `hosting` block shape to look for, a barrel-file snippet, registry edit snippet, and exact commands (`bun run type-check`, `bunx biome check`) plus UI steps to verify end-to-end.	5 / 5
Workflow Clarity	Five clearly sequenced steps with an overview table up front, a hard validation gate in Step 2 ("Stop and run /add-hosted-key"), explicit Step 5 verification including expected log output and miss/error cell behavior, and a final checklist covering error recovery.	5 / 5
Progressive Disclosure	Well-sectioned single file with no bundle references, and every codebase path mentioned is real within the workflow. At ~140 lines, the architecture map and the full Step-3 code template are candidates for a references/ file, so structure is good but not fully offloaded.	4 / 5
	Total	18 / 20 Passed

Description

92%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 tight, third-person description that states concrete capabilities and an explicit trigger clause for a well-defined niche. The only gap is minor: a couple of natural synonym phrasings that users might use instead of "table enrichment".

Dimension	Reasoning	Score
Specificity	Multiple concrete actions in third person: "Add a code-defined table enrichment (registry entry)", "backed by an ordered provider cascade", "ensuring every provider tool it calls has hosted-key support" — comprehensive for the skill's scope with no vague padding.	5 / 5
Completeness	Explicitly answers both: the "what" (add a registry entry backed by a provider cascade with hosted-key verification) and a concrete "Use when adding a per-row table enrichment that fills cells via existing Sim tools" trigger clause.	5 / 5
Trigger Term Quality	Natural phrases users would say are present ("table enrichment", "per-row", "fills cells", "Sim tools"), but a few natural variants like "enrichment column" or "data enrichment" are missing, so it falls just short of the comprehensive-synonyms anchor.	4 / 5
Distinctiveness Conflict Risk	A clear niche anchored in codebase-specific terms ("apps/sim/enrichments/", "hosted-key support", "Sim tools") makes overlap with other skills minimal and the triggers unambiguous.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: simstudioai/sim
Path: .agents/skills/add-enrichment/SKILL.md
Commit: 8725250

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.