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
50
55%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/cost-analyst/skills/understand-cloudzero-organization/SKILL.mdQuality
Discovery
75%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 effectively communicates when to use the skill (start of CloudZero cost analysis sessions) and what it loads (custom dimensions, team structures, cost allocation policies, workflows), making it functionally complete. However, it could be more specific about the concrete actions performed beyond 'loading context' and could include more natural trigger terms that users might use when initiating cost analysis work.
Suggestions
Add more natural trigger term variations such as 'cloud costs', 'spending analysis', 'FinOps', or 'billing' to improve discoverability when users phrase requests differently.
Specify concrete actions beyond 'load context' — e.g., 'retrieves custom dimension mappings, identifies team cost ownership, applies allocation rules' to make capabilities more tangible.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (CloudZero cost analysis) and mentions some specific items it loads (custom dimensions, team structures, cost allocation policies, workflows), but it describes loading context rather than listing concrete actions the skill performs beyond that. | 2 / 3 |
Completeness | The description answers both 'what' (loads organization-specific context including custom dimensions, team structures, cost allocation policies, and workflows) and 'when' (at the start of any CloudZero cost analysis session), with an explicit trigger clause using 'Use at the start of...'. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'CloudZero', 'cost analysis', 'custom dimensions', 'cost allocation', but misses common user variations such as 'cloud costs', 'spending', 'billing', or 'FinOps'. The terms are somewhat specialized and may not match how users naturally phrase requests. | 2 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to CloudZero cost analysis context loading, which is a very specific niche. The combination of 'CloudZero', 'cost analysis session', and 'organization-specific context' makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill wraps a single API call (`get_org_context()`) in approximately 150 lines of content, most of which describes data that Claude will see in the API response anyway. The repeated emphasis on caching (stated 4+ times) and the extensive enumeration of what the context contains are wasteful. The core value — call this tool first, cache the result, use it in subsequent skills — could be conveyed in under 30 lines.
Suggestions
Reduce the 'What Organization Context Provides' section to a brief bullet list or remove it entirely — Claude will see the actual response data and doesn't need a preview of what it might contain.
Consolidate the repeated 'call once per conversation' guidance into a single, prominent note rather than restating it in multiple sections (When to Use, Efficiency Note, Best Practices, Integration).
Add error handling guidance: what to do if `get_org_context()` returns empty/incomplete data or fails, to improve workflow clarity.
Move the integration pattern template and the detailed 'What Organization Context Provides' content into a separate reference file to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose for what amounts to a single API call (`get_org_context()`). The skill over-explains what organization context provides (sections 1-5 are describing data Claude will see when it gets the response), repeats the 'call once per conversation' instruction at least 4 times, and includes extensive boilerplate about integration patterns, best practices, and when to re-invoke that could be condensed to a few lines. | 1 / 3 |
Actionability | The core action is clear — call `get_org_context()` — but there's no executable code beyond that single function call. The output format template is helpful but is a markdown template rather than something concrete. The example usage is illustrative but not truly executable. Most of the content describes rather than instructs. | 2 / 3 |
Workflow Clarity | Steps 1-4 provide a reasonable sequence (check cache → call tool → analyze → store), but for such a simple operation (one API call), the workflow is over-engineered. There are no validation checkpoints — no guidance on what to do if `get_org_context()` returns incomplete data, errors, or unexpected structure. | 2 / 3 |
Progressive Disclosure | References to external files exist (CloudZero Tools Reference, Dimensions Reference) with path variables, but no bundle files are provided to verify them. The SKILL.md itself is monolithic — the lengthy 'What Organization Context Provides' section (sections 1-5) could easily be in a separate reference file, and the integration pattern template could be elsewhere. The content that is inline should largely be split out. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%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
- Cloudzero/cloudzero-claude-marketplace
- Commit
760a9c7
- Reviewed
Table of Contents
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.