CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

policy-check

This skill should be used when the user asks to "run policy check", "check policy", "policy-check", or needs to validate package compliance. Provides guidance on running policy checks for specific packages or the entire repository.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is policy-check in microsoft/FluidFramework

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a model of lean, actionable instruction: exact commands for both package-scoped and repository-wide checks, a clear anti-pattern to avoid, and a non-obvious scoping rationale, all in three sentences with no padding. Nothing is missing for the skill's single purpose and nothing should be moved to separate files.

DimensionReasoningScore

Conciseness

The body is three sentences with zero padding: no explanation of what pnpm or policy checks are, and the caveat sentence ("changes in one package can cause policy failures in others") conveys non-obvious information that earns its place, matching the lean-and-efficient anchor.

5 / 5

Actionability

Exact executable commands are given for both invocation modes (`pnpm policy-check --path <relative-path>` from the repo root and repo-wide `pnpm policy-check`), along with an explicit negative instruction ("Do NOT `cd` into the package directory"), covering the common cases copy-paste ready.

5 / 5

Workflow Clarity

This is a simple single-task skill whose single action is unambiguous (run one command from the repo root, never cd), and the note on when repo-wide checks are appropriate resolves the only decision point; a policy check is a read-only operation, so the destructive/batch validation cap does not apply.

5 / 5

Progressive Disclosure

The skill is well under 50 lines, needs no external references (no bundle files exist), and keeps its entire, appropriately scoped content in SKILL.md, satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

20

/

20

Passed

Description

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

The description clearly communicates when to invoke the skill via explicit quoted trigger phrases and identifies its scope (specific package vs. entire repository). Its main weakness is the meta-language "Provides guidance on running policy checks", which describes the skill indirectly instead of stating concrete actions, and slightly thin synonym coverage around compliance terminology.

Suggestions

Replace "Provides guidance on running policy checks" with direct concrete actions, e.g. "Runs `pnpm policy-check` for a specific package or repository-wide to validate package policy compliance", so the what is stated as actions rather than meta-description.

Add one or two natural trigger synonyms such as "policy compliance" or "check policy violations" to broaden the when-clause coverage.

Clarify what domain the policies belong to (e.g., licensing, dependencies, security) to sharpen distinctiveness against generic compliance/lint skills.

DimensionReasoningScore

Specificity

"Provides guidance on running policy checks for specific packages or the entire repository" names the domain and a single action at two scopes, but "provides guidance on" is meta-language and the description does not list several distinct concrete actions, matching the anchor for one-to-two concrete actions rather than comprehensive coverage.

3 / 5

Completeness

Both "what" ("running policy checks for specific packages or the entire repository") and an explicit "when" with concrete quoted trigger phrases are present, but the "what" is conveyed through the meta-phrase "Provides guidance on" rather than direct concrete actions, so it falls just short of the clearly-explicit both-what-and-when anchor.

4 / 5

Trigger Term Quality

Three quoted natural phrasings ("run policy check", "check policy", "policy-check") plus "validate package compliance" give good keyword coverage, but common variations such as "policy compliance" or "policy violations" are absent, keeping it below the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

"policy-check" is a distinct niche trigger unlikely to fire for unrelated skills, but the broader clause "needs to validate package compliance" carries minor overlap risk with general compliance or linting skills, fitting the mostly-distinct anchor.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

microsoft/FluidFramework

Path

.github/skills/policy-check/SKILL.md

Reviewed

Table of Contents

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.