create-custom-permissions

Add named key-value boolean permissions to DaaS-backed applications.

1|Updated May 26, 2026
One-click install
npx skills add https://github.com/BaraArdiwinata/hackathon-sima-arome --skill create-custom-permissions-baraardiwinata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-custom-permissions
Source: https://github.com/BaraArdiwinata/hackathon-sima-arome/tree/main/.agents/skills/create-custom-permissions
Command: npx skills add https://github.com/BaraArdiwinata/hackathon-sima-arome --skill create-custom-permissions-baraardiwinata

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @directus/shared/utils/permissions/custom, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill allows you to add named key-value boolean permissions to a DaaS-backed application, providing application-level capability flags that are not tied to a collection or CRUD operation.

Core Features & Use Cases

  • Custom Permissions: Define application-level capabilities that can be checked from React components and Next.js API routes.
  • Integration with DaaS: Custom permissions coexist with DaaS data-access permissions and share the same Policy/Role assignment chain.
  • Use Case: Use this Skill to control access to specific features or actions within your application, such as viewing a widget or rejecting workflow requests.

Quick Start

Add the custom permission 'MyApp.Dashboard.TaskWidget' to the policy for the 'Tenant Admin' role.

Frequently Asked Questions about create-custom-permissions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add custom permissions to a DaaS-backed Next.js application?

To add custom permissions to a DaaS-backed Next.js application, you define named key-value boolean flags that integrate with the existing Policy → Role → User assignment chain for application-level access control.

What are application-level capabilities in policy-based access control?

Application-level capabilities are named boolean permission flags that control access to specific features like viewing widgets, independent of standard data-access CRUD operations tied to collections.

Can I check DaaS custom permissions from Next.js API routes and React components?

Yes, you can check DaaS custom permissions from Next.js API routes and React components using client-side hooks and server-side utilities for resolving the policy-based permission states.

Does this custom permissions approach work with the existing DaaS Policy and Role chain?

Yes, custom permissions coexist with DaaS data-access permissions and share the same Policy → Role → User assignment chain, ensuring feature flags remain consistent with existing roles.

How do I assign application capabilities to a specific tenant role?

You assign application capabilities by adding the named custom permission key to the policy configured for the target tenant role within your DaaS environment.

What is the difference between DaaS data-access permissions and application-level custom permissions?

DaaS data-access permissions restrict CRUD operations on collections, whereas application-level custom permissions are boolean flags controlling specific application features and actions independent of collections.