domino-data-connectivity

Connect Domino workloads to external data sources including AWS S3 (via Mountpoint CSI driver), credential propagation with AWS IRSA and Azure Entra ID, and External Data Volumes. Use when configuring S3 access, setting up credential propagation, or connecting to cloud data sources from Domino.

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/data-connectivity/SKILL.md

Quality

Content

51%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 reads efficiently and makes good structural use of tables and quick-start code, but it delegates its substance to three referenced files that are missing from the bundle, and it contains no sequenced setup workflow or validation steps for the configuration tasks the skill is named for. As shipped, a consumer would get an index with no reachable detail.

Suggestions

Add ordered setup sequences with validation checkpoints for each option (e.g., Mountpoint CSI driver install + a verify step such as listing an S3 object; IRSA trust-policy setup verified with `aws sts get-caller-identity`) so the core configuration tasks are actionable without the missing detail files.

Create the referenced files (S3-MOUNTPOINT.md, AWS-IRSA.md, AZURE-CREDENTIALS.md) or fix the paths — currently none of them exist in the bundle, breaking progressive disclosure.

Make quick-start examples self-contained (e.g., add `import json` in the EDV snippet) and trim the "When to Use" bullet lists to the non-obvious criteria.

Dimension	Reasoning	Score
Conciseness	The body is lean: terse comparison tables, short code snippets, and no re-explanation of concepts Claude already knows. It falls short of anchor 5 because the "When to Use Each Option" bullet lists are somewhat padded with obvious criteria ("Want to avoid EFS costs for large data") and the opening sentence duplicates the frontmatter description.	4 / 5
Actionability	The quick-start snippets are concrete (boto3 client, pd.read_parquet on a mount path), but the skill's core advertised tasks — configuring S3 access, setting up credential propagation — have no executable steps in the body; they are deferred to detail files that are not present in the bundle. The EDV example also omits `import json`, leaving minor incompleteness in the code itself.	3 / 5
Workflow Clarity	No ordered sequence exists for any setup workflow: the quick start assumes configuration is already done ("With IRSA configured...") and provides no steps to get there, and no validation checkpoints appear anywhere. This matches anchor 2 — a rough usage picture with many gaps and validation absent — rather than anchor 3, where steps are at least listed.	2 / 5
Progressive Disclosure	The structure is good in intent — an overview with well-signaled one-level-deep references to S3-MOUNTPOINT.md, AWS-IRSA.md, and AZURE-CREDENTIALS.md — but those referenced files do not exist anywhere in the bundle (verified via file listing), so navigation to the detailed content is broken. References present but non-functional fits anchor 3 rather than 4.	3 / 5
	Total	12 / 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 strong description: it states concrete capabilities, gives explicit 'Use when...' triggers, and carves out a clearly distinct niche. The only minor weakness is keyword coverage, which misses a few natural synonyms an Azure-storage or bucket-level user might say.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete capabilities — "AWS S3 (via Mountpoint CSI driver)", "credential propagation with AWS IRSA and Azure Entra ID", and "External Data Volumes" — giving comprehensive coverage of the skill's scope. It exceeds anchor 4 because the actions are named with their specific mechanisms rather than leaving minor gaps in coverage.	5 / 5
Completeness	It explicitly answers both questions: the "what" is "Connect Domino workloads to external data sources including AWS S3... and External Data Volumes", and the "when" is the concrete trigger clause "Use when configuring S3 access, setting up credential propagation, or connecting to cloud data sources from Domino". This matches the anchor-5 example pattern exactly.	5 / 5
Trigger Term Quality	Natural trigger phrases like "configuring S3 access", "setting up credential propagation", and "connecting to cloud data sources" are well chosen, alongside technical keywords (Domino, IRSA, Mountpoint, Entra ID). It falls short of anchor 5 because common variations users might say — e.g. "S3 bucket", "Azure storage", "mount a volume" — are not covered.	4 / 5
Distinctiveness Conflict Risk	The Domino-specific niche with named technologies (Mountpoint CSI, IRSA, Azure Entra ID, External Data Volumes) is highly distinct and unlikely to trigger for unrelated skills. Trigger conditions are anchored to the Domino platform, minimizing conflict risk.	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
relative_links	Relative link issues: 3 missing	Warning

	Total	15 / 16 Passed

Repository: dominodatalab/domino-claude-plugin
Path: skills/data-connectivity/SKILL.md
Commit: 92a240b

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.