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.

72

Quality

89%

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

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 tight, security-aware reference skill: dense concrete guidance, a Red Flags anti-checklist plus a Verification checklist serving as validation checkpoints, and clean sectioning with one-level cross-skill links. Slightly short of fully copy-paste-ready workflows and an explicit fix-retry loop.

Suggestions

Tighten the opening orientation line and a few explanatory clauses (e.g. the parenthetical on RPC vs edge functions) to push conciseness toward a 5.

Add one minimal complete edge-function skeleton (CORS → authenticate → handler) so the main workflow is copy-paste ready rather than described.

Turn the Verification checklist into an explicit validate→fix→re-run loop for the security-critical RLS/migration steps to lift workflow_clarity to 5.

DimensionReasoningScore

Conciseness

Lean and information-dense, assuming Claude knows Supabase/PostgreSQL/RLS; only minor trimmable redundancy (the opening orientation sentence and a few explanatory clauses) keep it just below a 5.

4 / 5

Actionability

Gives concrete, executable specifics — `CREATE OR REPLACE VIEW`, `httpClient(`${supabaseUrl}/functions/v1/<name>`)`, migration id `20260108160722`, shared-utils paths — with minor gaps where guidance stays high-level (e.g. 'expose the edge function as a custom dataProvider method').

4 / 5

Workflow Clarity

Clear sequence (read section → write code → check Red Flags → run Verification checklist) with explicit validation checkpoints for security-critical RLS/migration work, though the checklist form lacks an inline validate→fix→retry loop.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with one-level-deep cross-skill navigation (`Skill({skill: "writing-migrations"})`, `Skill({skill: "frontend-dev"})`); no bundle files exist but none are needed for a skill this size.

5 / 5

Total

17

/

20

Passed

Description

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

An excellent description: third-person voice, dense with concrete backend actions, an explicit 'Use when' trigger clause, and tightly scoped to the Atomic CRM/Supabase niche. No fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'creating/modifying database migrations, views, triggers, RLS policies, edge functions, or custom dataProvider methods that call Supabase APIs' — giving comprehensive coverage of the backend surface.

5 / 5

Completeness

Explicitly answers both what ('Coding practices for backend development in Atomic CRM') and when via a concrete 'Use when deciding whether backend logic is needed, or when creating/modifying...' clause.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage: 'database migrations, views, triggers, RLS policies, edge functions, dataProvider methods, Supabase APIs' are exactly the phrases a developer would say when needing this skill.

5 / 5

Distinctiveness Conflict Risk

Scoped to Atomic CRM backend with Supabase-specific triggers (RLS, edge functions, dataProvider), giving a clear niche with minimal overlap risk against generic coding skills.

5 / 5

Total

20

/

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.

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.