CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

platform-consumers

Work on Grida account and billing client adapters, credit display, Console handoffs and native execution receipts. Excludes financial policy and provider operations.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/platform-consumers/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 tight, guardrail-style instruction skill that is maximally token-efficient and full of specific project rules, but it under-specifies execution: verification steps name no concrete commands, and its one reference points outside the bundle via an unresolvable relative path. Workflow ordering is only implicit in document order with no explicit validation checkpoints.

Suggestions

Name the concrete verification commands (e.g. the exact test/check invocations for 'affected consumer checks and editor TypeScript') or point to a script in a scripts/ bundle file that runs them.

Fix the consumer README reference: copy it into a references/ file inside the skill bundle, or use a path that resolves from SKILL.md, so the 'read before editing' step is actionable.

Make the workflow explicit and ordered (1. read README/adapter, 2. edit under the listed constraints, 3. run checks, 4. fix and re-run if failing) with a validation checkpoint after the checks.

DimensionReasoningScore

Conciseness

The body is ~20 lean lines of pure directives with zero concept explanations or padding (e.g. 'Keep configuration server-only and lazy. Fail closed for affected paid actions'). Every token carries a project-specific rule and assumes Claude's competence.

5 / 5

Actionability

Directives are specific as constraints ('Never put workload credentials in navigation URLs', 'Retain original execution identities and completion receipts'), but key operational details are missing: 'Run affected consumer checks and editor TypeScript' names no actual command, and the referenced consumer README path (../../../editor/lib/platform/README.md) points outside the skill bundle and does not resolve. This fits anchor 3 (concrete guidance but incomplete, missing key details) better than anchor 4, where commands would be present with only minor gaps.

3 / 5

Workflow Clarity

A sequence is implied by document order — read the README and affected adapter before editing, apply the bulleted rules, then 'Run affected consumer checks and editor TypeScript' — but steps are never made explicit and validation has no commands or fix-and-retry checkpoints. Not destructive/batch work, so no hard cap applies; anchor 3 (sequence present but checkpoints missing or implicit) is the best fit.

3 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and the under-50-line body is well organized (heading, orientation paragraph, bulleted rules, closing verification paragraph). The single reference is clearly signaled ('Read [the consumer README](../../../editor/lib/platform/README.md) and affected adapter before editing') but escapes the skill directory via a fragile ../../../ relative path that does not resolve from the skill's location, keeping it at anchor 4 rather than 5.

4 / 5

Total

15

/

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.

A precise, lean, third-person description that clearly delimits a distinctive niche and explicitly fences off adjacent domains. Its main weakness is the missing 'when' — no trigger clause telling Claude when to reach for the skill — and slightly generic action phrasing ('Work on').

Suggestions

Add a 'Use when...' clause naming the concrete trigger moments, e.g. 'Use when editing Grida account or billing client adapters, credit display components, or Console handoff/native receipt handling.'

Replace the generic 'Work on' verb with 2-3 concrete actions (e.g. 'Edit, extend, and review ...') to raise specificity.

Add one or two common synonyms users might say (e.g. 'billing adapters', 'credit/usage display') to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

It names the domain precisely ('Grida account and billing client adapters') and lists several concrete work objects ('credit display, Console handoffs and native execution receipts'). It falls short of anchor 5 because the only verb is the generic 'Work on' — the objects are specific but no concrete actions (fix, preserve, implement) are enumerated.

4 / 5

Completeness

The 'what' is clear (work on Grida account/billing client adapters, credit display, Console handoffs, native execution receipts) but there is no 'when' — no 'Use when...' clause or equivalent trigger guidance, which the judging guidelines explicitly cap at 3. The exclusion statement ('Excludes financial policy and provider operations') bounds scope but does not tell Claude when to activate the skill.

3 / 5

Trigger Term Quality

Natural domain keywords a user in this codebase would say are present: 'account', 'billing', 'credit display', 'Console handoffs', 'native execution receipts'. Missing common variations and synonyms (e.g. usage, invoice, plan, any file paths or extensions), which keeps it at anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche with distinct domain terms (Grida, Console handoffs, native execution receipts) and an explicit exclusion ('Excludes financial policy and provider operations') that actively prevents collision with sibling financial-policy/provider-operations skills. Anchor 5 (clear niche with distinct triggers; minimal conflict risk) is the best fit.

5 / 5

Total

16

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

gridaco/grida

Path

.agents/skills/platform-consumers/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.