deploy-admin-permissions

Deploy an identity-verified role and permission system for a Runneth org sandbox.

3|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Motion-Creative/runneth-apps --skill deploy-admin-permissions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deploy-admin-permissions
Source: https://github.com/Motion-Creative/runneth-apps/tree/main/add-roles-permissions
Command: npx skills add https://github.com/Motion-Creative/runneth-apps --skill deploy-admin-permissions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill sets up an identity-verified permission system so admins can safely control org-level actions while members are restricted to their own home base.

Core Features & Use Cases

  • Automatic identity resolution: Resolves Slack IDs and motionapp.com emails to roles and home bases for every request.
  • Five-phase idempotent deployment: Pre-flight scans, explicit confirmation, deterministic installation, verification, and a post-deploy checklist.
  • Safety-first permission enforcement: Includes prompt-injection defenses, collision detection, locked-path restrictions, and strict scope rules (read from identity metadata only).
  • Admin/member operational model: Admins can manage workspace-map.json and locked org paths; members can write only under their own home base.

Quick Start

Tell Runneth to run the add-roles-permissions skill using the deployment flow for Phase 1–5 and follow the on-screen confirmations.

Frequently Asked Questions about deploy-admin-permissions

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

FAQPage Schema
How do I set up role-based access control using Slack IDs and email addresses?▼

Role-based access control is deployed by resolving Slack IDs and motionapp.com emails into verified roles and home bases. The system uses a workspace-map.json file as the identity source of truth to enforce strict admin and member scopes.

How do I provision admin permissions safely without exposing cross-org actions to members?▼

Admin permissions are provisioned through a five-phase idempotent deployment that includes pre-flight conflict detection and post-deployment verification. This process enforces locked-path restrictions, ensuring members can only write under their own home base.

What is the best way to prevent prompt injection during identity resolution and access provisioning?▼

Preventing prompt injection during identity resolution requires safety-first permission enforcement protocols. The deployment applies strict scope rules that read exclusively from identity metadata, preventing unauthorized cross-org actions.

Does the access control system require a specific permissions protocol before deployment?▼

The access control system requires a mandatory permissions protocol pointer located in the agent user.md file. It also requires executable dual resolver scripts and a workspace-map.json file to function as the identity source of truth.

How does the five-phase deployment process handle existing workspace configurations?▼

The five-phase deployment handles existing configurations through pre-flight scans and explicit confirmation before making any deterministic installation changes. This idempotent approach includes collision detection to prevent conflicts with existing workspace setups.

Can I manage locked org paths directly after completing the admin provisioning process?▼

Admin provisioning grants the ability to manage workspace-map.json and locked org paths directly. Admins receive full org-level action control, while members remain restricted to writing only within their designated home base.