evernote-enterprise-rbac
Implement enterprise RBAC for Evernote integrations. Use when building multi-tenant systems, implementing role-based access, or handling business accounts. Trigger with phrases like "evernote enterprise", "evernote rbac", "evernote business", "evernote permissions".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill evernote-enterprise-rbac79
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%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 well-structured skill description with explicit trigger terms and clear 'when to use' guidance. The main weakness is that the capabilities could be more specific about what concrete actions the skill enables (e.g., creating roles, managing permissions hierarchies, auditing access). The description effectively carves out a distinct niche.
Suggestions
Add more specific concrete actions like 'create permission roles', 'manage user hierarchies', 'audit access logs', or 'configure tenant isolation' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (enterprise RBAC for Evernote) and mentions some actions (building multi-tenant systems, implementing role-based access, handling business accounts), but lacks specific concrete actions like 'create roles', 'assign permissions', or 'manage user groups'. | 2 / 3 |
Completeness | Clearly answers both what (implement enterprise RBAC for Evernote integrations) and when (building multi-tenant systems, implementing role-based access, handling business accounts) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'evernote enterprise', 'evernote rbac', 'evernote business', 'evernote permissions'. These are specific and cover common variations a user might naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with the specific combination of 'Evernote' + 'enterprise RBAC'. The trigger terms are unique enough that this would not conflict with generic RBAC skills or other Evernote skills. | 3 / 3 |
Total | 11 / 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.
This skill provides comprehensive, executable code for implementing Evernote enterprise RBAC, with strong actionability through complete JavaScript implementations and SQL schema. However, it suffers from being overly verbose with all code inline rather than progressively disclosed, and critically lacks validation checkpoints for testing the security-sensitive RBAC implementation.
Suggestions
Add explicit validation steps after each major implementation phase (e.g., 'Test role assignment by querying user_roles table and verifying the expected role is returned')
Split the extensive code into separate reference files (models.md, services.md, schema.md) and keep only essential examples in the main skill
Remove the Prerequisites section - Claude already understands these concepts
Add a verification checklist at the end to confirm RBAC is working correctly before deployment
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite lengthy with extensive code examples. While the code is useful, some sections could be tightened - the prerequisites section explains concepts Claude knows, and some code comments are redundant. The permission levels table is efficient, but overall the document is verbose for what it teaches. | 2 / 3 |
Actionability | The skill provides fully executable JavaScript code with complete implementations for permission models, RBAC service, middleware, and database schema. Code is copy-paste ready with proper imports, class definitions, and SQL statements. | 3 / 3 |
Workflow Clarity | Steps are numbered and sequenced logically (1-7), but there are no validation checkpoints or feedback loops for verifying the RBAC implementation works correctly. For a security-critical system like RBAC, missing validation steps (e.g., 'test permission grants before deploying') is a significant gap. | 2 / 3 |
Progressive Disclosure | The skill is largely monolithic with all code inline. While it references external resources at the end and mentions 'evernote-migration-deep-dive' for next steps, the 400+ lines of code could benefit from being split into separate reference files (e.g., models.md, services.md, schema.md). | 2 / 3 |
Total | 9 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (727 lines); consider splitting into references/ and linking | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- 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.