engram-business-rules

Product and business-rule guardrails for Engram. Trigger: Any change that affects sync behavior, project controls, permissions, or memory semantics.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/business-rules/SKILL.md

Quality

Content

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

The body is a lean, well-structured set of guardrails with concrete rules and no fluff. Its weakest point is workflow clarity: it lists rules to apply but provides no sequenced procedure or validation checkpoints for the risky sync/admin changes it covers.

Suggestions

Add a short sequenced procedure (e.g., identify affected rule -> check server-side enforceability -> fail loudly if violated -> preserve audit trail) with an explicit validation checkpoint.

Include one concrete verification step for destructive/admin-policy changes, such as confirming auditability before merging, to lift workflow clarity above 3.

Dimension	Reasoning	Score
Conciseness	Every line is a discrete rule with no padding and no over-explanation of concepts Claude already knows; the body assumes competence and every token earns its place.	5 / 5
Actionability	Rules are concrete and specific ("fail loudly rather than dropping data silently", "must be deterministic and testable", "enforceable server-side"), giving actionable guardrails, though they are principles rather than executable commands.	4 / 5
Workflow Clarity	Content is organized into clear sections (When to Use, Product Rules, Sync Rules) but there is no sequenced workflow with validation checkpoints for the sync/permission/admin changes it governs.	3 / 5
Progressive Disclosure	Under 50 lines with no need for external references, and split into well-organized, clearly signaled sections, satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	17 / 20 Passed

Description

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

The description is concise, product-scoped, and supplies an explicit trigger clause that answers both what and when. Its main weakness is specificity: it states a single generic capability (guardrails) rather than enumerating concrete actions.

Suggestions

Add 1-2 concrete actions the skill performs (e.g., 'enforces', 'validates', 'reviews') to lift specificity beyond a single generic capability.

Include a few natural synonyms or variations of the trigger terms (e.g., 'admin policy', 'local-vs-remote data') to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("Product and business-rule guardrails for Engram") but the only action stated is providing guardrails, which is minimal/generic with no enumerated concrete actions.	2 / 5
Completeness	Clearly states what it is ("Product and business-rule guardrails for Engram") and gives an explicit, concrete "Trigger:" clause answering when to use it.	5 / 5
Trigger Term Quality	The explicit "Trigger: Any change that affects sync behavior, project controls, permissions, or memory semantics" provides good keyword coverage a developer would naturally mention, though a few common variations are absent.	4 / 5
Distinctiveness Conflict Risk	Tied to the specific Engram product with distinct trigger domains (sync, project controls, permissions, memory semantics), giving it a clear niche with minimal overlap risk.	5 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Gentleman-Programming/engram
Path: skills/business-rules/SKILL.md
Commit: 47f281c

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.