CtrlK
BlogDocsLog inGet started
Tessl Logo

resource-management

Server-side Luzmo resource operations - CRUD, automation, and bulk API scripts. Use for listing, searching, creating, or deleting dashboards, datasets, themes, users, groups. Triggers on: "list all dashboards", "delete dataset", "bulk update", "automate", "script", "find resources". Critical: all deletes are irreversible and require explicit user confirmation before execution. Not for embedding saved dashboards/charts (use core), auth setup (use core), or data ingestion (use data-integration).

74

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

Well-structured, actionable, and safety-conscious with strong workflow checkpoints and clean progressive disclosure. The main weakness is redundancy: core rules are restated across the Avoid and Common Mistakes sections.

Suggestions

Consolidate the POST-only, credential-security, and irreversible-delete rules into one authoritative section; have "Avoid" and "Common Mistakes" cross-reference it instead of restating each rule a third time.

Trim the "Common Mistakes" frequency markers and "You'll see" symptom prose, or fold the genuinely new pitfalls into the relevant sections, to recover tokens without losing the safety emphasis.

Consider moving the security checkpoint into the references (e.g. deletion-policy.md already covers delete safety) if the same content is duplicated, keeping the body to the actionable checklist only.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence and uses lean tables/lists, but the POST-only rule, the security rule, and the irreversible-delete rule each recur across "Core API Rules", "Avoid", and "Common Mistakes" (3x), and the "Common Mistakes" section restates earlier content with padded frequency/symptom prose — a clear tightening opportunity.

2 / 3

Actionability

Concrete and actionable throughout: exact base URLs by region, an Action Map of real action names, precise doc URL patterns, and a numbered deletion workflow — with copy-paste-ready executable clients split into the bundled references, which is appropriate for an instruction/routing skill.

3 / 3

Workflow Clarity

The destructive-delete workflow is a clearly sequenced search → show → explicit-"yes"-confirm → execute path with an explicit preview checkpoint, and the security checkpoint has a "If ANY checkbox is unchecked, STOP" validation gate, so destructive/batch validation is present rather than missing.

3 / 3

Progressive Disclosure

The body is an overview that signals one-level-deep references (script-examples.md, deletion-policy.md, delete-script-patterns.md — all present in ./references) plus external docs, with templates appropriately split out and a dedicated "Bundled References" navigation list.

3 / 3

Total

11

/

12

Passed

Description

100%

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 specific, trigger-rich, and complete with explicit when-guidance and clear non-goals. It uses third-person voice and avoids fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions on named resources — "CRUD, automation, and bulk API scripts" and "listing, searching, creating, or deleting dashboards, datasets, themes, users, groups" — matching the anchor for listing several specific concrete actions rather than naming only a domain.

3 / 3

Completeness

Clearly answers both what (server-side resource CRUD/automation/bulk scripts on listed resource types) and when (an explicit "Use for" clause plus a "Triggers on" list), satisfying the highest completeness anchor.

3 / 3

Trigger Term Quality

Explicit "Triggers on: \"list all dashboards\", \"delete dataset\", \"bulk update\", \"automate\", \"script\", \"find resources\"" are natural phrases a user would say, giving good coverage rather than technical jargon.

3 / 3

Distinctiveness Conflict Risk

Carves a clear server-side Luzmo niche and adds an explicit "Not for..." boundary with hand-offs to core and data-integration, making it unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

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

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository
luzmo-official/agent-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.