AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Permission Model Validator

skill-aborroy-aiup-alfresco-permission-model-validator · by aborroy

Validates custom Alfresco permission model XML for well-formedness, no collision with built-in permission group names, correct permissionSet binding, and that any dynamic authority is registered and implements DynamicAuthority. Trigger automatically after generating or editing a *permissionDefinitions.xml or a *DynamicAuthority.java file.

No reviews yet
0 installs
23 views
0.0% view→install

Install

$ agentstack add skill-aborroy-aiup-alfresco-permission-model-validator

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-aborroy-aiup-alfresco-permission-model-validator)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Permission Model Validator? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Permission Model Validator

Validate the given custom Alfresco permission model and dynamic authorities against these rules.

XML Structure Validation

  • The file must be well-formed XML with root element ``.
  • Each ` must declare a type` attribute bound to a custom type or aspect

({prefix}:...), not a redefinition of a core type that removes built-in groups.

  • Each ` and must declare a name`.

Built-in Name Collision

  • FLAG as ERROR any ` or ` whose name

collides with a built-in Alfresco permission group/permission: Read, Write, Delete, AddChildren, ReadProperties, ReadChildren, WriteProperties, Consumer, Contributor, Editor, Collaborator, Coordinator, SiteManager, SiteCollaborator, SiteContributor, SiteConsumer, FullControl, All.

  • Why it breaks: redefining a core group name corrupts the global permission model and can

silently alter access across the whole repository.

  • Fix: use a project-scoped PascalCase name; compose on top of a core group with

``.

Registration Validation

  • The model must be registered as an extension model, not a replacement: look for a Spring

bean with parent="permissionModelBootstrap" and a model property pointing at the permissionDefinitions.xml under alfresco/extension/.

  • WARN if no such registration bean is found in a companion *-context.xml.
  • The registering context must be imported from module-context.xml.

Dynamic Authority Validation

  • If a *DynamicAuthority.java exists:
  • It must implements DynamicAuthority (from org.alfresco.repo.security.permissions).
  • It must implement hasAuthority, getAuthority, and requiredFor.
  • FLAG as ERROR runAsSystem inside hasAuthority (privilege escalation + per-node perf

hazard).

  • WARN if hasAuthority does not guard with nodeService.exists().
  • The bean must be registered (id {prefix}.{name}DynamicAuthority) and added to the global

dynamicAuthorities list.

  • WARN if a permission/group omits requiresType where it logically applies only to the

bound type.

Output

Report all violations with file path, line number, rule violated, and suggested fix. If no violations found, confirm the permission model is valid.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.