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.
86
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that clearly defines its scope (backend development for Atomic CRM), lists specific concrete actions (migrations, views, triggers, RLS policies, edge functions, dataProvider methods), and includes an explicit 'Use when' clause with natural trigger terms. It uses proper third-person voice and is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: database migrations, views, triggers, RLS policies, edge functions, and custom dataProvider methods that call Supabase APIs. These are all concrete, identifiable backend development tasks. | 3 / 3 |
Completeness | Clearly answers both what ('Coding practices for backend development in Atomic CRM') and when ('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'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'backend', 'database migrations', 'views', 'triggers', 'RLS policies', 'edge functions', 'dataProvider', 'Supabase'. These are terms a developer working on this stack would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: backend development specifically for Atomic CRM using Supabase. The combination of project name, technology stack, and specific backend artifacts (RLS policies, edge functions, dataProvider methods) makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%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 skill that efficiently communicates project-specific backend conventions without over-explaining. Its main weaknesses are the lack of executable code examples (especially for edge functions and dataProvider methods) and missing validation/verification steps for database migrations and RLS policy changes.
Suggestions
Add a concrete, executable code example for an edge function following the middleware chain pattern (CORS → authenticate → handler) to improve actionability.
Add validation steps for migrations: e.g., 'Run `supabase db reset` to verify migration applies cleanly' or similar checkpoint after creating views/triggers.
Link directly to example files (e.g., the `20260108160722` migration, an existing edge function) so Claude can reference them without guessing paths.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every sentence conveys project-specific knowledge Claude wouldn't already know. No padding, no explanation of what Supabase or PostgREST is. Lean and efficient. | 3 / 3 |
Actionability | Provides concrete patterns (e.g., httpClient URL format, middleware chain order, specific migration reference) but lacks executable code examples. The edge function conventions and dataProvider method patterns would benefit from copy-paste-ready snippets. | 2 / 3 |
Workflow Clarity | The decision tree (frontend-only vs view vs edge function) is clear, but there are no validation checkpoints for migrations or edge function deployment. For database migrations and RLS policies (destructive/schema-changing operations), missing validation steps cap this at 2. | 2 / 3 |
Progressive Disclosure | References migration `20260108160722` and shared utils directory but doesn't provide navigable links. The content is well-organized with clear sections but could benefit from explicit links to example files or a reference document for the middleware chain pattern. | 2 / 3 |
Total | 9 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- marmelab/atomic-crm
- Commit
8126ceb
- 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.