CtrlK
BlogDocsLog inGet started
Tessl Logo

backend-dev

Coding practices for backend development in Atomic CRM. Use when deciding whether backend logic is needed, or when creating/modifying database migrations, views, triggers, RLS policies, edge functions, or custom dataProvider methods that call Supabase APIs.

75

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, well-structured reference with strong workflow clarity and a verification checklist, scoring well on progressive disclosure for a simple single-file skill. The main gap is actionability: guidance is convention-level with fragments rather than complete executable examples.

Suggestions

Add at least one complete, copy-paste-ready edge function example (CORS preflight → authenticate() → handler) so the middleware chain pattern is executable rather than only described.

Include a minimal concrete SQL snippet for the SECURITY DEFINER count function (with fixed search_path) to make the RLS pitfall directly actionable.

Show a full custom dataProvider method example (httpClient call + react-query wiring) for a representative mutation like salesCreate() to lift actionability to copy-paste ready.

DimensionReasoningScore

Conciseness

Lean body that assumes Claude's competence — e.g. "verify_jwt = false in config.toml, so JWT validation is manual via authenticate()" — with no padding or restating of basic concepts, fitting the level-3 anchor.

3 / 3

Actionability

Gives concrete conventions and flag-level specifics (e.g. "SECURITY DEFINER with a fixed search_path", "httpClient(`${supabaseUrl}/functions/v1/<name>`)") but lacks complete, copy-paste executable code blocks; it is mostly guidance rather than fully runnable examples, matching level 2 rather than the copy-paste-ready level 3.

2 / 3

Workflow Clarity

Clear sequencing via "Deciding where logic belongs", "Edge function conventions" (CORS → authenticate() → handler), plus a Red Flags list and a Verification checklist with explicit validation checkpoints for these database/edge operations — meeting the level-3 anchor.

3 / 3

Progressive Disclosure

No bundle files exist in references/scripts/assets; the single-file body is a well-organized overview with clearly signaled one-level cross-skill pointers (writing-migrations, frontend-dev), appropriate for a simple skill per the scoring notes.

3 / 3

Total

11

/

12

Passed

Description

100%

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, well-scoped description that states concrete capabilities and an explicit Use-when trigger, with clear Atomic CRM/Supabase niche differentiation. No first/second-person voice issues; no vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "creating/modifying database migrations, views, triggers, RLS policies, edge functions, or custom dataProvider methods that call Supabase APIs" — matching the level-3 anchor of several specific actions.

3 / 3

Completeness

Explicitly answers both what ("Coding practices for backend development in Atomic CRM") and when via an explicit "Use when deciding whether..." clause, satisfying the level-3 anchor.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — "database migrations", "views", "triggers", "RLS policies", "edge functions" — giving good coverage rather than jargon-only phrasing.

3 / 3

Distinctiveness Conflict Risk

Scoped to Atomic CRM / Supabase backend with distinct triggers unlikely to collide with generic skills; clearly not below level 2 since it names a precise niche.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
marmelab/atomic-crm
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.