CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

governance-assessor

Orchestrates AAP governance readiness assessments -- full platform audit or scoped to specific domains. Assesses 7 governance domains + 1 bonus: 1. Workflow Governance (approval gates, workflow coverage) 2. Notification Coverage (failure alerting, notification bindings) 3. Access Control / RBAC (teams, roles, least privilege) 4. Credential Security (separation of duties, credential hygiene) 5. Execution Environments (custom EEs, image provenance) 6. Workload Isolation (instance groups, capacity separation) 7. Audit Trail (activity stream, change tracking) Bonus: External Authentication (LDAP, SAML, SSO) Use when: - Full: "Is my AAP ready for production?", "Audit my platform governance" - Scoped: "Assess my credentials setup", "Check my RBAC", "How are my notifications?" - "What should I fix before executing jobs?" - Any question about specific AAP governance domains above NOT for job execution (use governance-executor) or troubleshooting (use forensic-troubleshooter).

Quality

81%

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

67%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 body presents a clear, gated workflow with concrete skill invocations, literal confirmation prompts, and illustrative worked examples, and it delegates the assessment framework to a properly linked reference. Its main flaws are systematic repetition of the same information across sections and a bundle with orphaned files plus a cross-bundle symlink that leaves the core framework reference fragile.

Suggestions

Consolidate the three listings of required skills (Prerequisites, Step 2 sub-bullets, Dependencies 'Required Skills') into a single Dependencies section and remove the duplicate mention of governance-readiness.md from Step 2's 'Document Consultation' paragraph.

Merge the closing 'Critical: Human-in-the-Loop Requirements' section into Step 3's 'Human Confirmation (REQUIRED)' block (or keep only one) so the confirmation gate is stated once at the point of use.

Either reference or remove the orphaned bundle files (error-classification.md, aap/execution-governance.md, aap/job-troubleshooting.md), and replace the cross-bundle symlink references/aap/governance-readiness.md with a direct in-bundle copy or a stable path so the framework document resolves within this skill's bundle.

DimensionReasoningScore

Conciseness

The body avoids concept-padding and stays directive, but information is systematically duplicated: the required-skills list appears three times (Prerequisites, Step 2 bullets, Dependencies), the human-confirmation requirement is stated twice (Step 3's 'Human Confirmation (REQUIRED)' and the closing 'Critical: Human-in-the-Loop Requirements' section), and governance-readiness.md is referenced three separate times. This is 'mostly efficient but could be tightened' (anchor 3) rather than minor trimmable instances (anchor 4).

3 / 5

Actionability

Guidance is concrete for an orchestrator skill: named skill invocations in sequence ('Invoke the aap-mcp-validator skill'), a literal user-facing prompt ('Should I create/modify this resource to address the gap?'), and two fully worked example dialogues covering the full and scoped cases. Anchor 4 rather than 5 because the MCP-server-to-domain mapping for scoped validation is only shown by example (Example 2), never specified, leaving a gap for unlisted domain combinations.

4 / 5

Workflow Clarity

A clear 4-step sequence (validate connectivity, run assessment, present report with gated remediation, generate summary) with an explicit validation stop ('If any required server fails: report and stop') and mandatory human-confirmation checkpoints before any write action. It meets anchor 4 but not anchor 5: there is no feedback loop or recovery path if the assessment skill itself fails or returns partial results mid-run.

4 / 5

Progressive Disclosure

References are well signaled with markdown links and one-line descriptions ([governance-readiness.md](references/aap/governance-readiness.md), two sample reports), and the heavy framework content is appropriately split out of SKILL.md. Not anchor 5 because three of seven bundle files (error-classification.md, aap/execution-governance.md, aap/job-troubleshooting.md) are never referenced from the body (orphaned content), and the key framework reference is a symlink into another skill's bundle (../../governance-readiness-assessor/...), an external indirection that does not resolve within this bundle.

4 / 5

Total

15

/

20

Passed

Description

91%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: explicit what and when, quoted natural trigger phrases with good synonym coverage, and clear negative boundaries against sibling skills. The only weaknesses are limited verb diversity with no mention of concrete outputs, and potential overlap with the governance-readiness-assessor sub-skill whose domain list it mirrors.

DimensionReasoningScore

Specificity

The description names concrete capabilities ('Orchestrates AAP governance readiness assessments -- full platform audit or scoped to specific domains') and enumerates 7 domains with specific sub-topics ('approval gates, workflow coverage', 'separation of duties, credential hygiene'). It matches anchor 4 rather than 5 because the verbs are limited to orchestrate/assess and no concrete outputs (report, fix order, remediation) are stated.

4 / 5

Completeness

It explicitly answers what (orchestrates full or scoped assessments across 7+1 enumerated governance domains) and when (a dedicated 'Use when:' section with concrete quoted trigger phrases for full, scoped, and pre-execution cases). A negative boundary ('NOT for job execution...') further sharpens the when; clear anchor 5.

5 / 5

Trigger Term Quality

Natural user phrases are quoted verbatim ('Is my AAP ready for production?', 'Audit my platform governance', 'Check my RBAC', 'How are my notifications?') with synonym coverage (audit/assess/check) and domain keywords users would naturally say (RBAC, credentials, notifications, LDAP, SAML, SSO). This matches the comprehensive-coverage anchor; no common natural terms are missing.

5 / 5

Distinctiveness Conflict Risk

A clear AAP-governance niche with explicit redirects to sibling skills ('use governance-executor', 'use forensic-troubleshooter') minimizes wrong-skill triggering for execution/troubleshooting. However, it claims 'Assesses 7 governance domains' while the sibling governance-readiness-assessor skill performs that assessment, so a near-duplicate description in the same library creates minor overlap risk with a closely related skill.

4 / 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: 2 deeper-than-1-level

Warning

referenced_paths_exist

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

Warning

Total

13

/

16

Passed

Repository

RHEcosystemAppEng/agentic-plugins

Path

rh-automation/skills/governance-assessor/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.