domino-projects

Work with Domino Projects including Git integration, DFS vs Git-based projects, collaboration, and version control. Covers project creation, Git provider setup (GitHub, GitLab, Bitbucket), branch management, collaborator permissions, and project settings. Use when creating projects, setting up Git repos, or managing team collaboration.

Quality

73%

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/projects/SKILL.md

Quality

Content

57%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 comprehensive, well-structured reference with concrete code and clear sections, but it leans long and monolithic: it re-teaches basic Git concepts Claude already knows, omits validation checkpoints in state-changing workflows, and keeps all content inline rather than progressively disclosing to bundle files.

Suggestions

Trim content Claude already knows — the 'Manual Git Commands' basics (git status/add/commit/push) and generic 'Best Practices' bullets — and keep only Domino-specific guidance to improve conciseness.

Add explicit validation/verification steps to state-changing workflows (e.g., after Sync or push, confirm the commit landed and the project state updated; verify branch before pushing) to lift workflow clarity above the destructive-operation cap.

Split the bulk into one-level-deep reference files (e.g., references/git-workflows.md, references/collaboration-roles.md, references/troubleshooting.md) and point to them from SKILL.md so the body acts as an overview rather than a monolith.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete code and lists, but includes content Claude already knows (basic 'git status / git add / git commit' commands, generic best-practice bullets like 'Use Git for Code: Change tracking, Code reviews') that could be trimmed.	3 / 5
Actionability	Provides mostly executable guidance — Python SDK snippets, copy-paste bash commands, and numbered UI steps — with only minor gaps (e.g., thin SDK examples like project_update with a placeholder environment_id).	4 / 5
Workflow Clarity	Multi-step flows (Create Project, Add Collaborator, Sync Files) are sequenced, but workflows involving state-changing operations (sync, push, branch management) lack explicit validation/verification checkpoints; the cap for missing validation on destructive/batch operations applies.	3 / 5
Progressive Disclosure	Well-organized with clear section headers, but the ~330-line body is monolithic with no bundle files or in-skill references — content like the full roles table, troubleshooting, and detailed Git workflows is inlined rather than split into one-level-deep reference files.	3 / 5
	Total	13 / 20 Passed

Description

88%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: third-person, concrete, with explicit 'what' and 'when' clauses covering the full Domino Projects surface area. Trigger terms are natural and the niche is mostly distinct, with only minor overlap risk from generic Git/collaboration phrasing.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across the domain — 'project creation, Git provider setup (GitHub, GitLab, Bitbucket), branch management, collaborator permissions, and project settings' — giving comprehensive coverage rather than a single generic action.	5 / 5
Completeness	Explicitly answers both 'what' (Work with Domino Projects including Git integration, DFS vs Git-based projects, collaboration, version control) and 'when' ('Use when creating projects, setting up Git repos, or managing team collaboration') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('creating projects', 'setting up Git repos', 'managing team collaboration') with good coverage, but lacks synonyms/variants and is anchored to one platform name.	4 / 5
Distinctiveness Conflict Risk	The 'Domino Projects' framing carves a clear niche, but trigger phrases like 'setting up Git repos' and 'managing team collaboration' carry minor overlap risk with generic Git/collaboration skills.	4 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: dominodatalab/domino-claude-plugin
Path: skills/projects/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.