Configuring Horizon
coollabsio/coolify
A skill your agent uses whenever the user mentions Horizon by name in a Laravel context.
Configure enterprise role-based access control for Lindy AI workspaces.
Install Lindy Enterprise Rbac
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-enterprise-rbac -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-enterprise-rbac --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/lindy-enterprise-rbac .claude/skills/lindy-enterprise-rbac && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "lindy-enterprise-rbac" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-enterprise-rbac into .claude/skills/lindy-enterprise-rbac/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-enterprise-rbac", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-enterprise-rbacType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-enterprise-rbac -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-enterprise-rbac --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/lindy-enterprise-rbac .agents/skills/lindy-enterprise-rbac && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lindy-enterprise-rbac" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-enterprise-rbac into .agents/skills/lindy-enterprise-rbac/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-enterprise-rbac", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-enterprise-rbac -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-enterprise-rbac --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/lindy-enterprise-rbac .cursor/skills/lindy-enterprise-rbac && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "lindy-enterprise-rbac" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-enterprise-rbac into .cursor/skills/lindy-enterprise-rbac/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-enterprise-rbac", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/lindy-enterprise-rbac--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-enterprise-rbac -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-enterprise-rbac --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/lindy-enterprise-rbac .gemini/skills/lindy-enterprise-rbac && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "lindy-enterprise-rbac" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-enterprise-rbac into .gemini/skills/lindy-enterprise-rbac/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-enterprise-rbac", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-enterprise-rbacInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-enterprise-rbac -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/lindy-enterprise-rbac .github/skills/lindy-enterprise-rbac && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "lindy-enterprise-rbac" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-enterprise-rbac into .github/skills/lindy-enterprise-rbac/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-enterprise-rbac", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-enterprise-rbac -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-enterprise-rbac --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/lindy-enterprise-rbac .opencode/skills/lindy-enterprise-rbac && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "lindy-enterprise-rbac" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-enterprise-rbac into .opencode/skills/lindy-enterprise-rbac/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-enterprise-rbac", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
lindy-enterprise-rbac- GitHub stars
- 2.8k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 748 words
- Files
- 3 (incl. references)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Configure enterprise role-based access control for Lindy AI workspaces.
- Works in 8 steps: Map Organizational Roles to Lindy Roles → Invite Team Members → Organize Agents with Folders → …
- Setting up team permissions
- SKILL.md covers Overview, Prerequisites, Lindy Role Model and Instructions, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Lindy Enterprise Rbac is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure enterprise role-based access control for Lindy AI workspaces. Use when setting up team permissions, managing workspace access, or implementing enterprise security policies with SSO/SCIM. Trigger with phrases like "lindy permissions", "lindy RBAC", "lindy access control", "lindy enterprise security", "lindy SSO".
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/implementation-guide.md` and `references/implementation.md`). Compatibility notes: Designed for Claude Code
It sits in Backend & APIs, covering Authorization and RBAC. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
When your agent uses it
- Setting up team permissions
- Managing workspace access
- Implementing enterprise security policies with SSO/SCIM
- With phrases like lindy permissions
Example prompts
- “lindy permissions”
- “lindy RBAC”
- “lindy access control”
- “/lindy-enterprise-rbac”
Requirements
- Compatibility (from SKILL.md): Designed for Claude Code
- Pre-approved tools (allowed-tools): Read, Write, Edit
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEdit
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
lindy.aidocs.lindy.ai
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Context cost
Lindy Enterprise Rbac loads about 1.7k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 86 tokens; SKILL.md has 748 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 748 words, ~1,729 tokens.
Download SKILL.mdSave it as
.claude/skills/lindy-enterprise-rbac/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- lindy-enterprise-rbac
- description
- Configure enterprise role-based access control for Lindy AI workspaces. Use when setting up team permissions, managing workspace access, or implementing enterprise security policies with SSO/SCIM. Trigger with phrases like "lindy permissions", "lindy RBAC", "lindy access control", "lindy enterprise security", "lindy SSO".
- allowed-tools
- Read, Write, Edit
- compatibility
- Designed for Claude Code
- version
- 1.20.0
- license
- MIT
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- tags
- saas, lindy, security, rbac
Lindy Enterprise RBAC
Overview
Lindy organizes access around workspaces where agents live. Team members are assigned roles that control who can create, modify, run, or observe agents and their execution history. Enterprise features add SSO, SCIM, audit logs, and granular permission controls.
Prerequisites
- Lindy Team ($49.99/mo + $19.99/seat) or Enterprise plan
- Workspace owner privileges
- Team members invited to the workspace
Lindy Role Model
| Role | Create Agents | Edit Agents | Run Agents | View Tasks | Manage Team |
|---|---|---|---|---|---|
| Owner | Yes | Yes | Yes | Yes | Yes |
| Editor | Yes | Yes | Yes | Yes | No |
| Viewer | No | No | No | Yes | No |
Instructions
Step 1: Map Organizational Roles to Lindy Roles
| Org Role | Lindy Role | Rationale |
|---|---|---|
| Engineering Lead | Owner | Full workspace control |
| Developer | Editor | Build and modify agents |
| Ops/Support | Editor | Run agents and configure workflows |
| Manager | Viewer | Monitor task execution and metrics |
| Stakeholder | Viewer | Read-only access to results |
Step 2: Invite Team Members
- Go to Settings > Team in the Lindy dashboard
- Click Invite Member
- Enter email address
- Select role: Owner, Editor, or Viewer
- Confirm invitation
Pro plan: Each additional seat costs $19.99/month Enterprise plan: Custom pricing with bulk seat discounts
Step 3: Organize Agents with Folders
Use folders to organize agents by team, function, or environment:
Workspace: Acme Corp Production
├── Support/
│ ├── Email Triage Agent
│ ├── FAQ Chatbot
│ └── Escalation Agent
├── Sales/
│ ├── Lead Router
│ ├── Follow-up Agent
│ └── Meeting Scheduler
├── Operations/
│ ├── Daily Report Agent
│ ├── Monitoring Agent
│ └── Data Pipeline Agent
└── Shared/
├── Knowledge Base Agent
└── Notification AgentFolder permissions: Share folders with specific team members to control visibility. Agents in private folders are only visible to the folder owner.
Step 4: Agent Sharing Controls
Each agent can be shared independently:
| Sharing Level | Who Gets It | What They Can Do |
|---|---|---|
| Edit access | Team collaborators | Edit agent, see all tasks |
| User access | Agent consumers | Run agent, trigger workflows |
| Template | Anyone with link | Make a copy (no access to original) |
Step 5: Connection Sharing
Control which team members can use shared integration connections:
- Private connections: Only the connection creator can use them
- Shared connections: Any team member can use them in their agents
- Recommendation: Keep sensitive connections (payment gateways, databases) private
Step 6: API Key Isolation
Create separate API keys per integration purpose:
| API Key | Purpose | Scope | Rotation |
|---|---|---|---|
lnd_prod_app_xxxx | Application webhook triggers | Production only | 90 days |
lnd_prod_ci_xxxx | CI/CD smoke tests | Test agents only | 90 days |
lnd_prod_monitor_xxxx | Monitoring/observability | Read-only | 90 days |
Revoke keys immediately when a team member with access leaves the organization.
Step 7: Enterprise Security Features
SSO (Single Sign-On):
- SAML-based authentication
- Configure in Enterprise settings
- Users authenticate through your identity provider
- Automatic session management
SCIM (User Provisioning):
- Automated user creation and deactivation
- Sync with your identity provider (Okta, Azure AD, etc.)
- When an employee leaves, SCIM automatically revokes Lindy access
- Group mappings to Lindy roles
Audit Logs:
- Complete activity trail for compliance
- Track who created, modified, or deleted agents
- Track who accessed task data
- Export for security review
Encryption:
- AES-256 encryption at rest
- TLS encryption in transit
- No data sharing between workspaces
Show full SKILL.md (295 more words)Show less
Step 8: Offboarding Procedure
When a team member leaves:
- SCIM auto-deactivates their account (Enterprise) or manually remove
- Revoke any API keys they had access to
- Transfer ownership of agents they created
- Review and re-authorize any integrations they set up
- Audit recent task history for their agents
Output
Create an access-control register that maps each workspace member and service account to a Lindy role, permitted connections, agent ownership, and the next review date. The register must include the offboarding owner and evidence that departing users’ sessions, API keys, and shared connections were revoked.
Examples
An operations analyst who only needs to inspect task history is assigned Viewer, receives no shared database connection, and is listed for quarterly review. A departing editor is removed from the workspace, their API key is revoked, and ownership of their production agents is transferred before the offboarding ticket is closed.
Access Control Checklist
- Team roles mapped to Lindy roles
- All team members invited with appropriate role
- Agents organized in folders by team/function
- Sensitive agents in private folders
- Connections shared only as needed
- Separate API keys per integration purpose
- Key rotation schedule (90-day max)
- Enterprise: SSO enabled
- Enterprise: SCIM configured
- Enterprise: Audit log review scheduled (monthly)
- Offboarding procedure documented
Error Handling
| Issue | Cause | Solution |
|---|---|---|
403 Forbidden on agent create | User has Viewer role | Promote to Editor |
| Agent not visible to teammate | Agent in private folder | Move to shared folder |
API key returns 401 | Key revoked or expired | Generate new key |
| Cannot delete workspace | Not the Owner | Transfer ownership first |
| SSO login fails | SAML misconfigured | Verify IdP metadata and assertions |
| SCIM not syncing | Endpoint URL wrong | Check SCIM endpoint in IdP config |
Resources
Next Steps
Proceed to lindy-migration-deep-dive for platform migration strategies.
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in skills/.curated/lindy-enterprise-rbac of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- references/implementation-guide.md
- references/implementation.md
Open the folder on GitHubat commit cfae287
Compare with similar skills
Lindy Enterprise Rbac next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Lindy Enterprise Rbac this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Configuring Horizoncoollabsio/coolify | 63k | 4 repos | ~898 | Automated safety check: Pass | MIT | |
| K8s Security PoliciesCybereason-Public/owLSM | 280 | 12 repos | ~2k | Automated safety check: Pass | GPL-2.0 | |
| Payloadpayloadcms/payload | 45k | 5 repos | ~6.2k | Automated safety check: Pass | MIT | |
| Convex Setup Authspokvulcan/poker-planning | 115 | 8 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Cognitoitsmostafa/aws-agent-skills | 1.2k | 1 repos | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
K8s Security Policies
Cybereason-Public/owLSM
Comprehensive guide for implementing NetworkPolicy, PodSecurityPolicy, RBAC, and Pod Security Standards in Kubernetes.
Payload
payloadcms/payload
A skill your agent uses when working with Payload projects (payload.config.ts, collections, fields, hooks, access control, Payload API).
Convex Setup Auth
spokvulcan/poker-planning
Sets up Convex auth, identity mapping, and access control. An agent skill from spokvulcan/poker-planning.
Cognito
itsmostafa/aws-agent-skills
AWS Cognito user authentication and authorization service. An agent skill from itsmostafa/aws-agent-skills.
Abp Authorization
abpframework/abp
ABP permission system - PermissionDefinitionProvider, [Authorize] attribute, CheckPolicyAsync, IsGrantedAsync, ICurrentUser, IPermissionManager, multi-tenancy side.
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming Security Code Review
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
Adapting Transfer Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
Analyzing Database Indexes
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Related
Categories
Questions about Lindy Enterprise Rbac
What does Lindy Enterprise Rbac do?
Configure enterprise role-based access control for Lindy AI workspaces. Lindy Enterprise Rbac is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure enterprise role-based access control for Lindy AI workspaces.
When should I use Lindy Enterprise Rbac?
Lindy Enterprise Rbac fits situations like: setting up team permissions; managing workspace access; implementing enterprise security policies with SSO/SCIM; with phrases like lindy permissions.
How do I install Lindy Enterprise Rbac in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-enterprise-rbac -a claude-code`. Or copy the skill folder (skills/.curated/lindy-enterprise-rbac in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/lindy-enterprise-rbac in your project. Claude Code loads it when a task matches its description.
How do I install Lindy Enterprise Rbac in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-enterprise-rbac -a codex`. Or copy the skill folder (skills/.curated/lindy-enterprise-rbac in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/lindy-enterprise-rbac in your project. Codex loads it when a task matches its description.
Can I use Lindy Enterprise Rbac in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-enterprise-rbac -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lindy-enterprise-rbac, .gemini/skills/lindy-enterprise-rbac, .github/skills/lindy-enterprise-rbac and .opencode/skills/lindy-enterprise-rbac in your project.
What does Lindy Enterprise Rbac need to run?
SKILL.md names no scripts, command-line tools or credentials: Lindy Enterprise Rbac is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code.
Does Lindy Enterprise Rbac access the network?
SKILL.md names 2 domains. As links in the text: lindy.ai and docs.lindy.ai. This is read from the text; nothing was executed.
Is Lindy Enterprise Rbac safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Lindy Enterprise Rbac use?
Lindy Enterprise Rbac is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Lindy Enterprise Rbac use?
About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.7k tokens, read only when the agent opens those files.
What are the alternatives to Lindy Enterprise Rbac?
Skills that share tags, products or a category with Lindy Enterprise Rbac: Configuring Horizon (coollabsio/coolify, 63k stars), K8s Security Policies (Cybereason-Public/owLSM, 280 stars), Payload (payloadcms/payload, 45k stars) and Convex Setup Auth (spokvulcan/poker-planning, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Lindy Enterprise Rbac?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.