domino-taxonomy

Manage Domino taxonomies — namespaces, tags, and entity tagging — via the Taxonomy API. Covers creating, listing, updating, and deleting tags and namespaces; tagging entities (project, model, dataset, app, project_template, netapp_volume); querying entities by tag; tag autocomplete; merging tags; and importing/exporting taxonomy trees as CSV. Use when organizing projects with tags, building hierarchical namespaces, finding all entities with a given tag, bulk-tagging during onboarding, or migrating taxonomy across environments.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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 with executable curl throughout and clearly sequenced workflows, but it loses points for repeated auth boilerplate and a redundant Description section, and critically for referencing bundle files (BULK-OPS.md, IMPORT-EXPORT.md) that are not present. Adding the missing bundle files and tightening repetition would raise the score.

Suggestions

Provide the missing referenced bundle files (BULK-OPS.md and IMPORT-EXPORT.md) or inline their content so the progressive-disclosure links actually resolve.

Add explicit validation/verification checkpoints to destructive and batch workflows — e.g. a confirm-before-delete and a verify-after step for namespace cascading deletes, bulk-delete, and merge-tags.

Remove the redundant 'Description' section (it repeats the frontmatter) and consolidate the repeated TOKEN/BASE/H auth snippet to a single definition referenced by each workflow.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean API reference with little concept over-explaining, but the 'Description' section restates the frontmatter and the TOKEN/BASE/H auth boilerplate is repeated across Configuration, Workflow 1, and Documentation Reference. Not a 3 because that redundancy could be tightened; not a 1 because it does not pad with generic concepts Claude already knows.	2 / 3
Actionability	Curl examples are fully executable with real JSON request bodies, status codes (201/204/400), and response shapes (e.g. the tag-entity POST and the autocomplete JSON) — copy-paste ready. Not a 2 because the code is concrete and complete, not pseudocode.	3 / 3
Workflow Clarity	Workflows are numbered and Workflow 1 includes a 'Verify' step, but destructive and batch operations (cascading namespace delete, bulk-delete, merge-tags, CSV import) lack explicit validate→fix→retry feedback loops in the body, and their detailed workflows are deferred to missing bundle files. Per the rubric, missing validation in destructive/batch operations caps this at 2; not a 1 because sequences are present and one workflow does show a checkpoint.	2 / 3
Progressive Disclosure	References to BULK-OPS.md and IMPORT-EXPORT.md are well-signaled and one level deep, but neither file (nor references/scripts/assets directories) exists, so navigation is broken. Not a 3 because the referenced paths do not resolve; the structure intent is good but the bundle is absent.	2 / 3
	Total	9 / 12 Passed

Description

100%

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 strong across all dimensions: it states concrete capabilities in third person, lists natural trigger phrases, explicitly pairs what-it-does with when-to-use guidance, and occupies a distinct niche. No changes needed.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — 'creating, listing, updating, and deleting tags and namespaces; tagging entities (...); querying entities by tag; tag autocomplete; merging tags; and importing/exporting taxonomy trees as CSV' — matching the 'lists multiple specific concrete actions' anchor. Not a 2 because coverage is comprehensive rather than partial.	3 / 3
Completeness	Explicitly answers both 'what' ('Manage Domino taxonomies — namespaces, tags, and entity tagging — via the Taxonomy API') and 'when' with an explicit 'Use when...' clause. Not a 2 because the when is explicit, not merely implied.	3 / 3
Trigger Term Quality	'Use when organizing projects with tags, building hierarchical namespaces, finding all entities with a given tag, bulk-tagging during onboarding, or migrating taxonomy across environments' gives good coverage of phrases a Domino user would naturally say. Not a 2 because common variations (tagging, finding by tag, bulk-tagging, migrating) are all present.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Domino's Taxonomy API) with distinct tagging/taxonomy triggers unlikely to fire for unrelated skills. Not a 2 because it is not a generic 'manage data' description that would overlap broadly.	3 / 3
	Total	12 / 12 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: 10 missing, 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: dominodatalab/domino-claude-plugin
Commit: 64f4433

Reviewed: 1 day 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.