libresource

libresource - Typed resource management with access control. ResourceIndex stores and retrieves resources with policy-based authorization. toInstance converts objects to typed instances. toResourceId parses URI strings. createResourceIndex factory. Use for persisting structured data, managing entities, and enforcing access control.

Quality

66%

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 ./packages/libresource/SKILL.md

Quality

Content

64%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 skill is concise and well-structured but incomplete in actionability. It covers basic retrieval and parsing but omits critical operations like creating/storing resources and using toInstance (which is mentioned but never demonstrated). The access control integration is mentioned but not shown in practice.

Suggestions

Add executable example for toInstance showing conversion from plain object to typed resource instance

Include example for creating/storing a resource, not just retrieving

Show error handling pattern for access control failures (what happens when policy denies access)

Add links to libpolicy skill or documentation for access control configuration

Dimension	Reasoning	Score
Conciseness	Content is lean and efficient, avoiding unnecessary explanations of concepts Claude already knows. Every section serves a purpose with no padding or verbose descriptions.	3 / 3
Actionability	Provides executable code examples for get and parse operations, but missing examples for creating resources, updating, deleting, or using toInstance. The patterns shown are incomplete for full usage.	2 / 3
Workflow Clarity	Shows individual operations but lacks a complete workflow showing how to create, store, retrieve, and manage resources end-to-end. No validation or error handling patterns shown for access control failures.	2 / 3
Progressive Disclosure	Mentions integration with libpolicy and other services but provides no links to related documentation. For a library skill, references to policy configuration or storage setup would improve navigation.	2 / 3
	Total	9 / 12 Passed

Description

67%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 provides a reasonable overview of the library's capabilities and includes an explicit 'Use for' clause, which is good for completeness. However, it relies heavily on technical API names (ResourceIndex, toInstance, toResourceId) that users wouldn't naturally use as trigger terms, and the use cases remain somewhat abstract rather than concrete task-oriented scenarios.

Suggestions

Replace API-specific names with natural language descriptions of what users would ask for, e.g., 'storing typed objects', 'permission checking', 'URI-based resource lookup'

Add more concrete trigger scenarios in the 'Use for' clause, such as 'when building CRUD operations with permissions' or 'when needing to control who can access specific data'

Dimension	Reasoning	Score
Specificity	Names the domain (resource management) and lists some actions (stores, retrieves, converts, parses, creates), but the actions are somewhat abstract and don't clearly convey what concrete tasks a user would accomplish.	2 / 3
Completeness	Clearly answers both what (typed resource management with access control, storing/retrieving resources, policy-based authorization) and when ('Use for persisting structured data, managing entities, and enforcing access control').	3 / 3
Trigger Term Quality	Includes some relevant terms like 'resource management', 'access control', 'authorization', 'persisting structured data', but uses technical jargon (ResourceIndex, toInstance, toResourceId, createResourceIndex) that users wouldn't naturally say when requesting help.	2 / 3
Distinctiveness Conflict Risk	The focus on 'resource management' and 'access control' provides some distinction, but terms like 'persisting structured data' and 'managing entities' are generic enough to potentially overlap with database or ORM-related skills.	2 / 3
	Total	9 / 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: copilot-ld/copilot-ld
Path: packages/libresource/SKILL.md
Commit: da36296

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.