claims

Claims-based authorization for agents and operations. Grant, revoke, and verify permissions for secure multi-agent coordination. Use when: permission management, access control, secure operations, authorization checks. Skip when: open access, no security requirements, single-agent local work.

1.79x

Quality

88%

Does it follow best practices?

Impact

97%

1.79x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Quality

Content

87%Scale 1-3

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

This is a well-structured, concise reference skill for claims-based authorization. Its strengths are token efficiency, concrete CLI commands, and clean tabular organization. Its main weakness is the lack of a sequenced workflow showing how to properly set up and verify authorization for an agent, which is important for security-sensitive operations.

Suggestions

Add a brief workflow section showing the typical sequence: check existing claims → grant with scope → verify the grant was applied correctly (e.g., re-run check command)

Include a verification/validation step after grant and revoke operations to confirm the authorization state is correct before proceeding

Dimension	Reasoning	Score
Conciseness	The content is lean and well-structured with tables for quick reference. No unnecessary explanations of what authorization or claims are—it assumes Claude understands these concepts and jumps straight to the specifics.	3 / 3
Actionability	Provides fully executable, copy-paste ready CLI commands for all operations (check, grant, revoke, list). Scope patterns and security levels are concrete and specific with clear examples.	3 / 3
Workflow Clarity	While individual commands are clear, there's no sequenced workflow showing how to set up authorization for a new agent (e.g., check existing claims → grant needed claims → verify). There's also no validation/verification step after granting or revoking claims, which matters for security-sensitive operations.	2 / 3
Progressive Disclosure	For a skill of this size and scope (under 50 lines of substantive content, single-purpose), the content is well-organized with clear sections and tables. No bundle files are needed, and the structure supports quick scanning and discovery.	3 / 3
	Total	11 / 12 Passed

Description

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

This is a well-structured description with clear 'Use when' and 'Skip when' clauses that aid in skill selection. The trigger terms are natural and relevant, and the domain is distinctive. The main weakness is that the capability listing could be more specific about concrete operations beyond the high-level 'grant, revoke, verify' triad.

Suggestions

Expand the specific actions beyond 'grant, revoke, and verify' to include more concrete operations like 'define permission policies', 'manage agent roles', or 'audit authorization decisions' to improve specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (claims-based authorization) and lists some actions (grant, revoke, verify permissions), but doesn't go deeper into concrete operations like 'create permission policies', 'assign roles to agents', or 'audit access logs'.	2 / 3
Completeness	Clearly answers both 'what' (claims-based authorization, grant/revoke/verify permissions for multi-agent coordination) and 'when' (explicit 'Use when' and 'Skip when' clauses with specific trigger scenarios).	3 / 3
Trigger Term Quality	Includes strong natural trigger terms: 'permission management', 'access control', 'authorization checks', 'secure operations', 'multi-agent coordination'. These are terms users would naturally use when needing this capability.	3 / 3
Distinctiveness Conflict Risk	The combination of 'claims-based authorization', 'multi-agent coordination', and specific permission operations creates a clear niche that is unlikely to conflict with other skills. The 'Skip when' clause further helps disambiguate.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/claude-flow
Path: .agents/skills/claims/SKILL.md
Commit: 913f9ea

Reviewed: 3 days 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.