apollo-enterprise-rbac

Enterprise role-based access control for Apollo.io. Use when implementing team permissions, restricting data access, or setting up enterprise security controls. Trigger with phrases like "apollo rbac", "apollo permissions", "apollo roles", "apollo team access", "apollo enterprise security".

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/apollo-pack/skills/apollo-enterprise-rbac/SKILL.md

Quality

Content

57%Weight 40%Scale 1-3

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

The content is highly actionable with executable code and a clear step sequence, but it lacks validation checkpoints for destructive RBAC operations and fails to integrate the bundled reference file, which it never links to and which uses an inconsistent role model.

Suggestions

Add a verification step after key creation/revocation and role changes (e.g., re-resolve the key, assert the permission matrix, or run an integration check) to satisfy the destructive-operation validation requirement for workflow_clarity.

Link references/implementation-guide.md from the body (e.g., a '## Advanced implementation' section pointing to it) and reconcile the role systems — the body uses 5 tiers while the reference uses 7 — so the split is coherent and navigable.

Move the larger code modules (RBAC service, team access, API key scoping already in the reference) out of the inline body and point to the reference, tightening the overview while keeping the quick-start inline.

Dimension	Reasoning	Score
Conciseness	The body is code-heavy and mostly efficient without re-explaining concepts Claude knows, but five full inline TypeScript modules make it dense; some of this code could be deferred to the reference file to tighten the overview.	2 / 3
Actionability	Provides fully executable, copy-paste-ready TypeScript with concrete endpoint-to-permission mappings and real Apollo API paths, matching the anchor for executable code and specific examples.	3 / 3
Workflow Clarity	The five steps are clearly sequenced, but there are no validation or verification checkpoints for destructive operations (key revocation, permission/role changes), which the rubric caps at 2 for risky operations.	2 / 3
Progressive Disclosure	A substantial references/implementation-guide.md bundle exists but is never linked or signaled from the body, and its role hierarchy (7 tiers) contradicts the body's (5 tiers), leaving the reference orphaned and the split incoherent.	1 / 3
	Total	8 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, third-person, and complete with explicit 'Use when' and 'Trigger with phrases like' guidance, covering both what the skill does and when to invoke it. Trigger terms are natural and Apollo-scoped, minimizing conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'implementing team permissions, restricting data access, or setting up enterprise security controls' — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ('Enterprise role-based access control for Apollo.io') and when ('Use when... Trigger with phrases like...'), matching the anchor for clear what-and-when with explicit triggers.	3 / 3
Trigger Term Quality	Provides natural user phrasings — 'apollo rbac', 'apollo permissions', 'apollo roles', 'apollo team access', 'apollo enterprise security' — covering common variations a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to Apollo.io enterprise RBAC with Apollo-specific trigger phrases, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/apollo-pack/skills/apollo-enterprise-rbac/SKILL.md
Commit: 0540a62

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.