CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

execution-risk-analyzer

Analyze execution risk by classifying inventory, scanning extra_vars for secrets, and assessing scope. Use when: - "Execute on production", "Deploy to production" (as first step before launch) - "Is this execution safe?" - "Check execution risk" - "Validate the execution target" NOT for: launching jobs (use governed-job-launcher) or troubleshooting failures (use job-failure-analyzer).

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary operational skill body: every step is executable with named tools and parameters, the multi-step workflow has explicit checkpoints and hard gates, and detail is appropriately pushed to a real, well-signaled reference file. The only trimmable fat is duplicated dependency listings and the workflow-replaying example section.

DimensionReasoningScore

Conciseness

The body is dense operational guidance with no concept-teaching padding, but contains minor trimmable duplication: MCP servers are listed in both Prerequisites and Dependencies, Example Usage replays the workflow, and Step 1 mandates a scripted user-facing announcement — matching 'minor instances of over-explanation that could be trimmed' rather than anchor 5's 'every token earns its place'.

4 / 5

Actionability

Every step names the exact MCP tool, its source server, and concrete parameters (e.g., order_by: "-finished", page_size: 5), backed by decision tables and a copy-paste report template — fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

A clear 7-step sequence with explicit conditional sub-steps (5a–5f keyed to risk level and job history), prerequisite verification via aap-mcp-validator, error-recovery signals (WARN/ELEVATED, 'Investigate before re-executing'), and hard gates (secrets found → BLOCK), matching the anchor-5 pattern of explicit validation with feedback loops.

5 / 5

Progressive Disclosure

The body serves as an overview that repeatedly and clearly signals the one-level-deep reference references/aap/execution-governance.md (which exists, at 569 lines, with sections matching the body's claims), while inlining only the quick-reference tables needed to execute — appropriate split and easy navigation.

5 / 5

Total

19

/

20

Passed

Description

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

A strong description: concrete actions, explicit quoted triggers for both what and when, and clear boundary routing to sibling skills. The only weaknesses are the slightly vague 'assessing scope' phrase and missing a few natural trigger synonyms.

DimensionReasoningScore

Specificity

Names three concrete actions ('classifying inventory, scanning extra_vars for secrets, and assessing scope'), two of which are highly specific, but 'assessing scope' is generic and the operational-context analysis (job history, notifications, workflow coverage) is not captured — minor gaps in coverage per the anchor-4 example.

4 / 5

Completeness

The opening sentence explicitly states what the skill does, and the 'Use when:' block provides concrete quoted trigger phrases for when to use it, directly matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

Quoted triggers ('Execute on production', 'Deploy to production', 'Is this execution safe?', 'Check execution risk', 'Validate the execution target') are natural user phrasings, but common variants like 'run this playbook', 'is it safe to deploy', or 'pre-launch check' are missing, keeping it short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche (pre-launch execution risk analysis) with distinct trigger phrases, plus an explicit 'NOT for' clause routing to governed-job-launcher and job-failure-analyzer, minimizes conflict with neighboring skills.

5 / 5

Total

18

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 3 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 3 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

RHEcosystemAppEng/agentic-plugins

Path

rh-automation/skills/execution-risk-analyzer/SKILL.md

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.