asset-access-control — Claude Code skill for ImageKit access
The asset-access-control Claude Code skill manages access to ImageKit files, folders, and media collections through DAM MCP. It responds to requests to inspect visibility, grant permissions, or change an ACL.
MIT 114 installs ★ 2 updated 2026-10-09
npx skills add imagekit-developer/skills --skill asset-access-control -a claude-codeWhat asset-access-control does
The skill reads and updates access lists for ImageKit files, folders, and media collections. For files and folders it uses get_asset_access_list and update_asset_acl; for collections it uses get_collection_access_list and update_media_collection with the acl field. DAM MCP tools are required.
When only an asset name or path is available, the skill locates it with search_media_library, reads the current ACL, then uses the user and group IDs returned by that lookup. It can read the list again after a change. File and folder ACL updates must include both addOrModify and remove; the asset owner's entry must stay unchanged. A restricted user can edit access only on assets they are allowed to manage.
What it helps with
- find out who can access a file or folder
- grant a user READ, CONTRIBUTE, or MANAGE permissions
- add a user or group to an ACL
- remove access to a media collection
Example prompts for the agent
- Show who can view this ImageKit file.
- Give this group CONTRIBUTE access to the folder.
- Remove this user from the media collection's ACL.
How to install asset-access-control
1Skills CLI (Vercel)
npx skills add imagekit-developer/skills --skill asset-access-control -a claude-code2Manually: put the files in place
~/.claude/skills/asset-access-control/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/asset-access-control/
1Skills CLI (Vercel)
npx skills add imagekit-developer/skills --skill asset-access-control -a codex2Manually: put the files in place
.agents/skills/asset-access-control/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add imagekit-developer/skills --skill asset-access-control -a cursor2Manually: put the files in place
.cursor/skills/asset-access-control/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install imagekit-developer/skills skills/asset-access-control2Manually: put the files in place
.github/skills/asset-access-control/SKILL.md1Skills CLI (Vercel)
npx skills add imagekit-developer/skills --skill asset-access-control -a gemini-cli2Platform CLI
gemini skills install https://github.com/imagekit-developer/skills --path skills/asset-access-controlManually: put the files in place
.devin/skills/asset-access-control/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add imagekit-developer/skills --skill asset-access-control -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about asset-access-control
How do I install asset-access-control in Claude Code?
Run npx skills add imagekit-developer/skills --skill asset-access-control -a claude-code. The skill file is installed at ~/.claude/skills/asset-access-control/SKILL.md.
What does asset-access-control do?
It reads and edits ACLs for ImageKit files, folders, and media collections through DAM MCP tools. It can grant or revoke access for a user or group.
What does asset-access-control need to work?
It requires DAM MCP tools. To change an ACL, the user must be allowed to manage the relevant asset.
Source text
SKILL.md · MIT
---
name: asset-access-control
description: "Share or revoke access on ImageKit files, folders, and media collections via DAM MCP. Use when the user asks who can see an asset, to grant READ/CONTRIBUTE/MANAGE, or to add/remove a user or group from an ACL."
---
# Asset access control
Use the **DAM MCP** tools. Two surfaces — do not mix their tools.
| Target | Read ACL | Write ACL |
|--------|----------|-----------|
| File or folder | `get_asset_access_list` | `update_asset_acl` |
| Media collection | `get_collection_access_list` | `update_media_collection` (`acl`) |
`list_associated_media_collections` only answers "which collections contain this file/folder?". It does not change membership; use `add_assets_to_media_collection` / `remove_assets_from_media_collection`.
Restricted users can only change access on assets they can manage.
## Workflow
1. Resolve the asset with `search_media_library` if you only have a name or path.
2. Read the current ACL. Use `userId` / `groupId` from that response — never invent ids.
3. Write the change. Then re-read if you need to confirm.
`get_asset_access_list` also returns `users` and `userGroups` for the account. Match the person the user named against `userName` / `userEmail` / `label`.
## `update_asset_acl`
- Always send **both** `acl.addOrModify` and `acl.remove`. Use `[]` on the unused side.
- `entity.type` is only `USER` or `USER_GROUP`. `MEDIA_COLLECTION` may appear on read (inherited membership); do not send it on write.
- Do not change the asset owner's entry.
- Do not grant less than a parent folder already grants that same entity.
```json
{
"assetId": "<file-or-folder-id>",
"acl": {
"addOrModify": [{ "entity": { "id": "<userId>", "type": "USER" }, "permission": "READ" }],
"remove": []
}
}
```
## `list_associated_media_collections`
`permission` is a **string**, not an array. Send `'["MANAGE"]'` or `'["READ","CONTRIBUTE"]'`. Omit it unless you are filtering for a restricted user.
© imagekit-developer · MIT · imagekit-developer/skills