Name: understand-cloudzero-organization
Rating: 58.4 (1 reviews)
Author: Cloudzero

understand-cloudzero-organization

Use at the start of any CloudZero cost analysis session to load organization-specific context — custom dimensions, team structures, cost allocation policies, and workflows

Quality

68%

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 ./plugins/cost-analyst/skills/understand-cloudzero-organization/SKILL.md

Quality

Content

62%Weight 40%Scale 1-3

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

The skill has a clear sequenced workflow with an explicit caching checkpoint and a concrete MCP call, but is verbose with redundant caching reminders and abstract mid-steps, and keeps all detail inline rather than splitting into reference files.

Suggestions

Consolidate the caching/avoid-redundant-calls guidance into one place; it currently appears in 'When to Use', 'Efficiency Note', and Best Practice #1.

Make Steps 3-4 actionable by specifying what to extract and where to store it (e.g. a concrete context schema) instead of 'Review...' and 'Store key insights...'.

Move the detailed 'What Organization Context Provides' enumeration and output template into a separate reference file linked from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The ~165-line body is mostly efficient but repeats the caching rule across 'When to Use', 'Efficiency Note', and Best Practice #1, and the 'Integration with Other Skills' section instructs other skills rather than this one, so it could be tightened.	2 / 3
Actionability	It gives one concrete executable call ('get_org_context()') and a structured output template, but Steps 3-4 ('Analyze and Internalize Context', 'Make Context Available to Other Skills') are abstract direction rather than specific actionable guidance.	2 / 3
Workflow Clarity	Steps 1-4 are clearly sequenced with an explicit gating checkpoint in Step 1 ('If YES... If NO...'), plus re-validation guidance in 'When Context Changes' and Best Practice #3, satisfying the score-3 anchor for a non-destructive single-tool workflow.	3 / 3
Progressive Disclosure	No local bundle files exist (references/scripts/assets absent), and all content is inline in one ~165-line file; the only 'See Also' links point to external ${CLAUDE_PLUGIN_ROOT} plugin docs rather than split detail files, matching the score-2 anchor where inline content could be separated.	2 / 3
	Total	9 / 12 Passed

Description

75%Weight 40%Scale 1-3

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 cleanly states both what it does and when to use it, with a distinct CloudZero-specific trigger that minimizes conflict risk. It is slightly held back by a single action verb and limited trigger-term variation.

Suggestions

Add a second concrete action verb (e.g. 'retrieve and cache') to lift specificity toward the score-3 anchor.

Broaden trigger terms to include natural user phrasings like 'cloud costs', 'spend analysis', or 'FinOps'.

Dimension	Reasoning	Score
Specificity	Quotes 'load organization-specific context — custom dimensions, team structures, cost allocation policies, and workflows' name the CloudZero domain and enumerate loaded content, but rely on a single action verb ('load') rather than multiple distinct concrete actions like the score-3 anchor (extract/fill/merge).	2 / 3
Completeness	Explicitly answers both what ('load organization-specific context — custom dimensions, team structures, cost allocation policies, and workflows') and when ('Use at the start of any CloudZero cost analysis session'), matching the score-3 anchor with an explicit trigger clause.	3 / 3
Trigger Term Quality	Uses 'CloudZero cost analysis session' as the trigger, which is relevant but narrow; it misses common variations a user might say (e.g. 'cloud costs', 'spend analysis', 'FinOps') that would warrant a 3.	2 / 3
Distinctiveness Conflict Risk	The CloudZero-specific niche and 'cost analysis session' trigger make it clearly distinguishable and unlikely to fire for unrelated skills, matching the score-3 'clear niche with distinct triggers' anchor.	3 / 3
	Total	10 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 2 missing, 2 deeper-than-1-level, 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: Cloudzero/cloudzero-claude-marketplace
Path: plugins/cost-analyst/skills/understand-cloudzero-organization/SKILL.md
Commit: b9c7c16

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