sharing

Framework-level sharing and privacy for user-authored resources (dashboards, documents, forms, decks, etc.). Use when making a resource table ownable, wiring list/read/update access checks, or dropping the standard share dialog into a template.

Quality

81%

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

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

A highly actionable, well-structured skill body with executable code throughout and a clear migration workflow backed by a debugging feedback loop. Its main weakness is progressive disclosure: everything lives in one long file with no split-out reference materials.

Suggestions

Move the verbose role-system explanation and/or the full actions table into a separate references file (e.g. ACTIONS.md) and link to it from the body to improve progressive disclosure.

Add an explicit validation/verify checkpoint to the migration pattern's backfill step (e.g. confirm row counts or spot-check owner_email values) since it is a batch data operation.

Relocate the dated incident reference ('2026-04-29 leak') into a dedicated 'old patterns' or changelog note so time-sensitive content does not sit inside a code comment.

Dimension	Reasoning	Score
Conciseness	Mostly lean and assumes competence; explanations target domain-specific concepts (visibility levels, role systems) rather than general knowledge, though the inline dated incident reference ('see the 2026-04-29 leak') is time-sensitive content not placed in a deprecated section.	4 / 5
Actionability	Provides copy-paste-ready, executable code for every common case — schema definition, resource registration, accessFilter, assertAccess, owner-setting inserts, and ShareButton — plus a full actions table with args and purpose.	5 / 5
Workflow Clarity	The migration pattern is a clearly sequenced 8-step list and the Debugging section supplies a verify/fix feedback loop, but the batch backfill step lacks an inline validation checkpoint, a minor gap.	4 / 5
Progressive Disclosure	Well-organized into clear section headers, but the ~280-line skill is monolithic with no bundle files and no one-level-deep references; content such as the actions table and role-system details that could live in separate files is inlined.	3 / 5
	Total	16 / 20 Passed

Description

83%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 with an explicit 'Use when' trigger and concrete, domain-specific actions. It clearly answers both what and when, with only minor gaps in trigger synonym coverage and slight overlap risk from the generic term 'sharing'.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete actions — 'making a resource table ownable', 'wiring list/read/update access checks', 'dropping the standard share dialog into a template' — but the actions are framework-internal rather than a fully comprehensive enumeration.	4 / 5
Completeness	Explicitly answers both what ('Framework-level sharing and privacy for user-authored resources…') and when ('Use when making a resource table ownable, wiring list/read/update access checks, or dropping the standard share dialog…') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural trigger phrases ('sharing and privacy', 'share dialog', 'access checks') and an explicit 'Use when' clause, though the vocabulary skews developer-internal and misses some common-user synonyms.	4 / 5
Distinctiveness Conflict Risk	The 'framework-level sharing and privacy for user-authored resources' framing carves a clear niche, but the broad word 'sharing' carries minor overlap risk with adjacent access/permission skills.	4 / 5
	Total	17 / 20 Passed

Validation

75%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	12 / 16 Passed

Repository: BuilderIO/agent-native
Path: .agents/skills/sharing/SKILL.md
Commit: bb282b1

Reviewed: ~21 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.