Name: activate-project
Rating: 50.4 (1 reviews)
Author: duplocloud

Blog Docs Log in Get started

activate-project

Activate a DuploCloud project context.

Quality

55%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/activate_project/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted, highly actionable skill for a complex multi-step project activation workflow. Its greatest strengths are the precise tool call specifications, exhaustive branching logic, and clear step sequencing with proper error handling. The main weakness is its length — while most content is necessary, some sections (particularly TOON parsing details and repeated emoji formatting reminders) could be tightened or extracted to supporting files.

Suggestions

Consider extracting the TOON parsing instructions into a shared reference file (e.g., TOON_PARSING.md) since this format likely appears in other skills too, reducing duplication and body length.

The color coding rule section at the top could be reduced to a single line since the examples throughout the document already demonstrate the pattern consistently.

Dimension	Reasoning	Score
Conciseness	The skill is quite long and detailed, but most content is necessary for the complex multi-step workflow. However, some sections are verbose — e.g., the color coding rule is repeated through examples, and the TOON parsing explanation could be tighter. The routing table in Step 7 is well-structured but the overall document could be trimmed by ~20%.	2 / 3
Actionability	The skill provides highly specific, concrete guidance: exact MCP tool calls with parameter names, precise file paths, specific TOON field mappings (i=id, n=name), exact user-facing message templates, and clear conditional logic for every branch. This is copy-paste ready for Claude to execute.	3 / 3
Workflow Clarity	The multi-step workflow is clearly sequenced (Steps 1-8) with explicit branching logic, validation checkpoints (auth/connection error handling, empty list handling), and feedback loops (e.g., workspace change clears project state, re-prompting on invalid selections). Each case is enumerated with clear conditions and outcomes.	3 / 3
Progressive Disclosure	The skill references external files appropriately (skills/ai_planner/SKILL.md, skills/stage_tasks/SKILL.md, CLAUDE.md) and delegates to them, but the main SKILL.md itself is a monolithic ~200-line document. The TOON parsing section and the state-writing details in Step 4 could potentially be extracted to reference files. No bundle files are provided to verify referenced paths.	2 / 3
	Total	10 / 12 Passed

Description

32%

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 extremely terse—a single sentence that names the tool (DuploCloud) and a single vague action. It lacks a 'Use when...' clause, multiple concrete actions, and natural trigger terms a user might employ. While the DuploCloud brand name provides some distinctiveness, the description is insufficient for reliable skill selection among many candidates.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'switch DuploCloud project', 'set duplo tenant', 'change duplo environment', 'duplo context'.

Expand the 'what' portion to list specific concrete actions, e.g., 'Sets the active DuploCloud tenant/project, configures environment variables, and validates connectivity to the selected project.'

Include common user-facing synonyms and variations such as 'duplo', 'tenant', 'infrastructure project', 'cloud environment' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names a specific domain (DuploCloud) and a single action (activate project context), but does not list multiple concrete actions or elaborate on what 'activating a project context' entails.	2 / 3
Completeness	Provides a brief 'what' (activate a DuploCloud project context) but completely lacks any 'when' clause or explicit trigger guidance, which per the rubric caps completeness at a maximum of 2, and the 'what' itself is also quite thin.	1 / 3
Trigger Term Quality	Includes 'DuploCloud' and 'project context' which are relevant keywords, but misses common variations or natural phrases a user might say such as 'switch project', 'set tenant', 'duplo project', or 'change environment'.	2 / 3
Distinctiveness Conflict Risk	'DuploCloud' is a specific product name which helps distinguish it, but 'activate a project context' is vague enough that it could overlap with other cloud platform or project-switching skills.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: duplocloud/duplo-claude-plugin
Commit: 6a46510

Reviewed: 4 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.