CtrlK
BlogDocsLog inGet started
Tessl Logo

neo4j-security-skill

Programmatic security management in Neo4j — RBAC/ABAC, user lifecycle (CREATE/ALTER/DROP USER), role lifecycle (CREATE/GRANT ROLE/DROP ROLE), privilege grants and denies (GRANT/DENY/REVOKE on graph, database, DBMS), property-level access control, sub-graph access control, SHOW PRIVILEGES inspection, and auth provider config reference (LDAP, OIDC/SSO). Use when an agent needs to manage users, roles, or privileges programmatically via Cypher on the system database. Does NOT handle Cypher query writing — use neo4j-cypher-skill. Does NOT handle cluster ops or backups — use neo4j-cli-tools-skill. Property-level security and ABAC require Enterprise Edition.

78

1.40x
Quality

90%

Does it follow best practices?

Impact

98%

1.40x

Average score across 1 eval scenario

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 well-structured, highly actionable security skill with executable Cypher, a mandatory write gate, and a verification-backed checklist. Tightening the small overlap between inline privilege patterns and the reference file would improve token efficiency further.

DimensionReasoningScore

Conciseness

Lean, comment-dense Cypher with no padding about what Neo4j or RBAC is, assuming Claude's competence; a few privilege patterns duplicate material also in the reference file and could be trimmed slightly.

4 / 5

Actionability

Copy-paste-ready Cypher throughout, plus a decision table mapping concrete goals ('Allow db connection', 'Read one property') directly to executable commands, covering the common cases comprehensively.

5 / 5

Workflow Clarity

Destructive/batch privilege operations are guarded by the mandatory MCP Write Gate, and the closing checklist sequences the work with explicit verification checkpoints ('SHOW ROLE ... PRIVILEGES AS COMMANDS', 'SHOW USER ... PRIVILEGES AS COMMANDS') forming a validate-then-proceed feedback loop.

5 / 5

Progressive Disclosure

A single one-level-deep reference (references/privilege-reference.md) is clearly signaled at the end and holds the bulk of full syntax, while the body keeps common patterns inline; the body itself is fairly long, keeping it just short of a 5.

4 / 5

Total

18

/

20

Passed

Description

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

A strong, specific description that clearly delineates both capabilities and trigger conditions while explicitly disambiguating from related skills. Minor room to add more natural-language synonyms alongside the technical terms.

DimensionReasoningScore

Specificity

Lists many concrete actions — 'CREATE/ALTER/DROP USER', 'GRANT/DENY/REVOKE on graph, database, DBMS', 'SHOW PRIVILEGES inspection', 'property-level access control', 'sub-graph access control' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (programmatic security management in Neo4j with enumerated capabilities) and 'when' ('Use when an agent needs to manage users, roles, or privileges programmatically via Cypher on the system database').

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ('manage users, roles, or privileges', 'RBAC/ABAC', 'LDAP, OIDC/SSO') but leans technical and lacks common synonyms or file-extension variants that would push it to a 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche reinforced by explicit disambiguation ('Does NOT handle Cypher query writing — use neo4j-cypher-skill', 'Does NOT handle cluster ops or backups — use neo4j-cli-tools-skill'), minimizing conflict with sibling skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
neo4j-contrib/neo4j-skills
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.