Name: webiny-admin-permissions
Rating: 72 (1 reviews)
Author: webiny

webiny-admin-permissions

Admin-side permission UI registration and DI-backed permission checking. Use this skill when adding permission controls to the admin UI — schema-based auto-generated forms, injectable permissions via createPermissionsAbstraction/ createPermissionsFeature, typed hooks (createUsePermissions), the HasPermission component (createHasPermission), and the Security.Permissions component props. Covers both simple apps and complex multi-entity permission schemas.

Quality

88%

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

Quality

Content

92%

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

A high-quality, highly actionable reference with executable code throughout and a clear layered build sequence. Its one weakness is progressive disclosure: the large inline API reference tables could be split into a separate reference file so SKILL.md stays an overview.

Suggestions

Move the Schema Reference, Entity Definition, and Security.Permissions Props tables into a separate REFERENCE.md (or similar) and keep SKILL.md as a concise overview with a one-level-deep link, so the inline body stays scannable.

Add a short 'Quick start' or numbered build-order checklist at the top (schema → abstraction → feature → register → hooks) to make the already-clear layer sequence immediately scannable before the detailed reference.

Dimension	Reasoning	Score
Conciseness	The body is lean reference material — code, tables, and file-structure maps with minimal prose — and assumes Claude's competence, explaining only Webiny-specific behavior Claude would not know (e.g., 'If the parent lacks the required action, the child is pruned from output'). Every token earns its place; it does not pad with generic concepts.	3 / 3
Actionability	Provides fully executable, copy-paste-ready TS/TSX for each layer (createPermissionSchema, createPermissionsAbstraction, createPermissionsFeature, RegisterFeature + Security.Permissions, usePermissions, HasPermission) plus complete field/prop reference tables. This matches the score-3 anchor of fully executable code with specific examples.	3 / 3
Workflow Clarity	The build order is an explicit, unambiguous three-layer sequence (Domain schema → Features/registration → Presentation hooks/components) reinforced by a File Structure map showing where each artifact lives. The rubric's validation-checkpoint requirement applies to destructive/batch/XML/db operations, none of which are present here.	3 / 3
Progressive Disclosure	The document is well-sectioned with clear header navigation, but it is a ~295-line monolith carrying three substantial inline API reference tables (Schema Reference, Entity Definition, Security.Permissions Props) and no bundle files at all. This fits 'some structure but content that should be separate is inline' rather than the one-level-deep split of score 3.	2 / 3
	Total	11 / 12 Passed

Description

85%

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, specific description with an explicit trigger clause and a clear admin-side niche. Its main weakness is trigger-term quality: the description leans heavily on implementation API symbols rather than the natural phrases a user would say.

Suggestions

Lead the trigger clause with more natural user phrasing and common variations (e.g., 'Use when adding permissions or a permission UI to a Webiny admin app, configuring role-based access, or building permission forms').

Move the long list of API symbol names (createPermissionsAbstraction, createUsePermissions, createHasPermission, etc.) out of the description or condense them, since they are implementation details rather than user-facing trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions with named APIs — 'permission UI registration', 'DI-backed permission checking', 'schema-based auto-generated forms', 'injectable permissions via createPermissionsAbstraction/createPermissionsFeature', 'typed hooks (createUsePermissions)', 'the HasPermission component (createHasPermission)'. This matches the score-3 anchor of multiple specific concrete actions rather than the partial score-2 anchor.	3 / 3
Completeness	Explicitly answers both what ('Admin-side permission UI registration and DI-backed permission checking...') and when ('Use this skill when adding permission controls to the admin UI'), with the explicit 'Use this skill when' trigger required for a 3.	3 / 3
Trigger Term Quality	The natural trigger phrase is only 'Use this skill when adding permission controls to the admin UI'; the rest of the description is dominated by API symbol names (createPermissionsAbstraction, createUsePermissions, etc.) that a user would not naturally say. This fits 'some relevant keywords but missing common variations' rather than the broad natural-term coverage of score 3, and is above the jargon-only score 1.	2 / 3
Distinctiveness Conflict Risk	Scoped clearly to the admin UI side ('Admin-side permission UI registration') and distinguishes itself from the API-side sibling via the Related Skills link, giving it a clear niche unlikely to trigger the wrong skill.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: webiny/webiny-js
Path: skills/user-skills/admin/admin-permissions/SKILL.md
Commit: 484553b

Reviewed: about 13 hours 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.