CtrlK
BlogDocsLog inGet started
Tessl Logo

oss-standards

Pre-PR discipline for a public-by-default repo. What a reviewer enforces beyond CI: secrets and internal data in diffs or screenshots, docs that name their reader, and the cleaning pass where incomplete or confusing artifacts get dropped. Use before opening any PR against `gridaco/grida` or when finalizing work for review.

67

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, actionable guidance skill that assumes Claude's intelligence and gives concrete decision rules and checklists. It is efficient rather than fully lean, and its workflow has validation checkpoints but no explicit error-recovery loop.

Suggestions

Tighten the editorial framing lines (e.g. 'Push = publish. A secret in a branch push is a published secret, even if you delete the commit five minutes later. "I'll redact before merge" is not a plan; rotation is.') to reduce token cost while preserving the rule.

Add an explicit validation/feedback loop to the cleaning pass (e.g. 'after dropping or fixing, re-run the stranger-reads-this check on the changed files until no unrecoverable questions remain') to lift workflow clarity.

Consider splitting the per-area rules (Code, Security, Docs) into a short reference file so SKILL.md stays a tighter overview pointing to detail, improving progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly lean and declarative, assuming Claude's competence with git, CI, and semver; a few editorial framing statements ('Push = publish', 'Incomplete is worse than absent') could be trimmed but largely carry the substantive rules rather than padding known concepts.

4 / 5

Actionability

Provides concrete, executable guidance for an instruction skill — 'Use draft: true', 'Use .env.local (gitignored) and fixture placeholders', 'rewrite as a neutral TODO with a tracking issue link' — plus a decision procedure (Helps→keep / Recoverable→fix / Unrecoverable→drop) and a concrete removals checklist.

4 / 5

Workflow Clarity

Sequences the flow (code/docs → security review when a GRIDA-SEC tag appears → cleaning pass → PR description/commit message) and the cleaning pass is a per-file validation checkpoint with a decision tree and checklist; it lacks an explicit error-recovery feedback loop, keeping it just below a 5.

4 / 5

Progressive Disclosure

Well-organized sections with a 'short version' overview and clearly-signaled, one-level-deep cross-references to sibling skills (links, etiology, security) and docs/AGENTS.md; the skill carries its own content inline appropriately with no detail files to split, so structure is good but not exemplary.

4 / 5

Total

16

/

20

Passed

Description

87%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, specific description that clearly states both the capability and the trigger conditions, scoped tightly to its niche. Slight room to add more natural synonyms, but it answers what and when concretely.

DimensionReasoningScore

Specificity

Names the domain (pre-PR discipline for a public-by-default repo) and several concrete enforcement areas — 'secrets and internal data in diffs or screenshots', 'docs that name their reader', 'the cleaning pass where incomplete or confusing artifacts get dropped' — with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ('What a reviewer enforces beyond CI: …') and when ('Use before opening any PR against gridaco/grida or when finalizing work for review') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Uses natural terms a user would say — 'PR', 'secrets', 'screenshots', 'review', 'finalizing work' — giving good keyword coverage, though a few natural synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (public-by-default OSS pre-PR discipline, naming the specific repo gridaco/grida) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 12 suspicious

Warning

Total

15

/

16

Passed

Repository
gridaco/grida
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.