add-connector

Add or update a Sim knowledge base connector for syncing documents from an external source, including auth mode, config fields, pagination, document mapping, tags, and registry wiring. Use when working in `apps/sim/connectors/{service}/` or adding a new external document source.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

77%

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 and workflows are clearly sequenced with strong validation checkpoints tailored to a batch sync operation. Its weaknesses are token efficiency (length and some restated sections) and progressive disclosure, since a large monolithic file carries detail that could be externalized.

Suggestions

De-duplicate the repeated meta/runtime structural explanation and the two 'Reference Implementations' sections into a single authoritative location to reduce length.

Split the detailed selector/canonical-pair guidance and the available-selector-keys table into a references file (e.g. SELECTORS.md) and link to it from a concise overview, so SKILL.md stays a lean entry point.

Tighten the explanatory prose around the OAuth and API-key meta.ts examples, which overlap, into one parameterized example with a short diff for the auth block.

Dimension	Reasoning	Score
Conciseness	The body is dense with codebase-specific knowledge Claude would not already know and avoids explaining basic concepts, but it is ~620 lines with notable redundancy — the structural meta/runtime split and the 'Reference Implementations' section are each restated — so it could be tightened; not a 3 because not every token earns its place.	2 / 3
Actionability	Provides fully executable TypeScript templates and a complete fileToStub/listDocuments/getDocument implementation pattern with exact imports, function signatures, and named helpers (htmlToPlainText, parseTagDate, fetchWithRetry), making it copy-paste ready; it is not a 2 because the code is concrete rather than pseudocode.	3 / 3
Workflow Clarity	The task is clearly sequenced, with a 'Hard Rule' stop-condition for unknown schemas, the listingCapped invariant as a correctness checkpoint against destructive deletion reconciliation, a contentHash identity invariant, and a final checklist — feedback loops appropriate to a batch sync operation.	3 / 3
Progressive Disclosure	No bundle files exist and the skill is a single ~620-line SKILL.md; sections are well-organized with clear headers and one-level-deep pointers to real reference implementations, but substantial detail (selector canonical pairs, the available-selector-keys table, content-hash strategies) lives inline that could be split into separate reference files.	2 / 3
	Total	10 / 12 Passed

Description

85%

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 specific, complete, and well-scoped, clearly stating what the skill does and when to use it. Its main weakness is trigger-term quality, since the triggers lean on internal file paths rather than natural user language.

Suggestions

Add natural-language trigger terms users would actually say (e.g. 'add a Confluence/Google Drive/Notion connector', 'sync external docs into the knowledge base') alongside the code-path trigger.

Consider mentioning common source services by name in the description so the skill matches when a user names a specific integration.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete actions — 'auth mode, config fields, pagination, document mapping, tags, and registry wiring' — matching the anchor that lists several specific concrete actions rather than naming only a domain.	3 / 3
Completeness	It states what ('Add or update a Sim knowledge base connector for syncing documents...') and gives an explicit 'Use when...' clause for when, satisfying the anchor requiring both with explicit triggers; it is not a 2 because the when-guidance is explicit, not merely implied.	3 / 3
Trigger Term Quality	Relevant terms exist ('syncing documents from an external source', 'adding a new external document source') but the primary triggers are internal code paths like 'apps/sim/connectors/{service}/' rather than natural user phrasings, and common variations a user would actually say are not covered.	2 / 3
Distinctiveness Conflict Risk	Scoped to 'Sim knowledge base connector' with a distinct codebase path trigger, giving it a clear niche unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (627 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: simstudioai/sim
Path: .agents/skills/add-connector/SKILL.md
Commit: 6f514c1

Reviewed: about 16 hours 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.