CtrlK
BlogDocsLog inGet started
Tessl Logo

database-cloud-optimization-cost-optimize

You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, and GCP.

52

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/database-cloud-optimization-cost-optimize/SKILL.md

The canonical home for this skill is database-cloud-optimization-cost-optimize in rmyndharis/antigravity-skills

SKILL.md
Quality
Evals
Security

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.

The skill body is concise and well-structured but stops at high-level guidance without executable commands or a validated workflow, and its only external reference points to a file that does not exist in the bundle. Concreteness and a real reference file would substantially raise the scores.

Suggestions

Add concrete, executable commands or tool calls (e.g. AWS Cost Explorer / CUR queries, `aws ce get-cost-and-usage`, Azure Cost Management API) to the Instructions instead of abstract verbs.

Insert an explicit validation checkpoint in the workflow (e.g. 'Validate savings estimate and rollback plan in staging before applying resizing/deletion') and reference the Safety section from the sequence.

Either add the referenced 'resources/implementation-playbook.md' to the bundle under the correct directory (references/) or correct the path so the reference resolves.

DimensionReasoningScore

Conciseness

The body is lean with well-organized sections and no padded explanations of concepts Claude already knows; only minor tightening is possible.

4 / 5

Actionability

Instructions ('Collect cost data by service', 'Identify waste and quick wins') are high-level descriptors rather than concrete commands or runnable examples, leaving key execution details unspecified.

3 / 5

Workflow Clarity

A rough four-step sequence exists, but operations involving resizing/deletion (destructive, batch) lack an explicit validation checkpoint inside the workflow; Safety mentions staging validation but the workflow itself does not enforce it.

3 / 5

Progressive Disclosure

Structure is clean with a one-level reference to 'resources/implementation-playbook.md', but that referenced file is absent from the bundle and the path ('resources/') does not match standard bundle directories, so navigation is not actually resolvable.

3 / 5

Total

13

/

20

Passed

Description

58%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.

The description conveys a clear, multi-action capability in a distinct niche but omits any explicit 'when to use' trigger guidance, which caps completeness. Adding concrete trigger phrases would lift completeness and trigger-term quality.

Suggestions

Append an explicit 'Use when...' clause naming concrete triggers such as 'Use when reducing cloud spend, rightsizing instances, or auditing idle resources.'

Add natural user phrases and synonyms (e.g. 'cloud bill', 'wasted spend', 'RI/Savings Plan coverage') to broaden trigger-term coverage.

Consider adding file- or service-level triggers (e.g. EC2/RDS/bigquery) to further reduce overlap with general FinOps or infrastructure skills.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures') across AWS, Azure, and GCP, with only minor coverage gaps.

4 / 5

Completeness

The 'what' is clearly stated but there is no 'Use when...' trigger clause, so per the rubric a missing explicit 'when' caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant terms ('cloud spending', 'cost optimization', 'infrastructure expenses') are present but common natural user phrases ('reduce my cloud bill', 'rightsizing', extensionless resource names) and synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

The cloud-cost-optimization niche across AWS/Azure/GCP is clearly distinct with minimal overlap risk against other skills, though no trigger phrase sharpens the boundary further.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.