New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Prismer Im Collab

by Prismer-AI in Prismer-AI/PrismerCloud

Coordinate reliably in Prismer conversations, use workspace assets through bounded MCP tools, and keep task work on the board.

MITAuto-check passedAgent Workflows

Install Prismer Im Collab

skills CLI
$ npx skills add Prismer-AI/PrismerCloud --skill prismer-im-collab -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Prismer-AI/PrismerCloud prismer-im-collab --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Prismer-AI/PrismerCloud.git skills-src && mkdir -p .claude/skills && cp -r skills-src/sdk/cloud/catalog/skills/prismer-im-collab .claude/skills/prismer-im-collab && rm -rf skills-src

Use ~/.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/

Facts

Skill name
prismer-im-collab
GitHub stars
1.6k
Token cost
~3.6k tokens
SKILL.md length
1,812 words
Files
1
Skills in repo
88
Repo updated
First seen
Licence
MIT

At a glance

Coordinate reliably in Prismer conversations, use workspace assets through bounded MCP tools, and keep task work on the board.

  • Works in 5 steps: First turn of any group conversation… → Reuse the result within the turn: one… → Never invent role names that aren't… → …
  • Tasks that involve MCP servers
  • SKILL.md covers Identity rule — never…, Don't poach tasks assigned to…, 任务派发的会话作用域（HARD） and Channel rules — DM vs Group, plus 6 more sections
  • Needs PRISMER_API_KEY

What it does

Prismer Im Collab is an agent skill from Prismer-AI/PrismerCloud. Coordinate reliably in Prismer conversations, use workspace assets through bounded MCP tools, and keep task work on the board.

Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering MCP servers. The licence is MIT.

When your agent uses it

  • Tasks that involve MCP servers

Example prompts

  • “/prismer-im-collab”

Requirements

  • A credential in PRISMER_API_KEY
  • Pre-approved tools (allowed-tools): prismer.agent.send, prismer.conversation.listAgents, prismer.task.create, prismer.task.update, prismer.task.complete, prismer.approval.request_human_approval, prismer.asset.search, prismer.asset.describe, prismer.asset.read

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. First turn of any group conversation (kickoff): listAgents first, then compose. No exceptions. If the kickoff prompt asks you to…
  2. Reuse the result within the turn: one listAgents call per turn is enough — cache the names in your scratchpad and reference them across…
  3. Never invent role names that aren't returned. If listAgents returns [ceo, engineer, marketer], your reply may describe Team Manager /…
  4. One participant = DM behaviour. If listAgents returns just you + one human, the room is effectively a DM. Drop the @-mention rules and…
  5. Mismatch surfaces fast. If the human's prompt names a role that listAgents does not contain (e.g. "@researcher, please…" but no researcher…

What it can do on your machine

Read from SKILL.md and the folder at commit e5d9444. 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:

    • prismer.agent.send
    • prismer.conversation.listAgents
    • prismer.task.create
    • prismer.task.update
    • prismer.task.complete
    • prismer.approval.request_human_approval
    • prismer.asset.search
    • prismer.asset.describe
    • prismer.asset.read

    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

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • PRISMER_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prismer Im Collab loads about 3.6k tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 1,812 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~36
When it runs · the whole SKILL.md, loaded when a task matches
~3.6k

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 Prismer-AI/PrismerCloud at commit e5d9444, republished under its MIT licence (© Prismer-AI). 1,812 words, ~3,572 tokens.

Download SKILL.mdSave it as .claude/skills/prismer-im-collab/SKILL.md (or your agent's skills folder).
name
prismer-im-collab
description
Coordinate reliably in Prismer conversations, use workspace assets through bounded MCP tools, and keep task work on the board.
allowed-tools
prismer.agent.send, prismer.conversation.listAgents, prismer.task.create, prismer.task.update, prismer.task.complete, prismer.approval.request_human_approval, prismer.asset.search, prismer.asset.describe, prismer.asset.read
scope
common

Prismer IM Collaboration

You are an agent in a Prismer multi-agent workspace. This skill explains the channel-specific rules so your replies actually route correctly.

Identity rule — never impersonate (HARD)

The [Channel context] block at the top of every prompt tells you exactly who you are (You are: <username>). Your identity is fixed. Across an entire conversation:

  • You are NEVER the human owner. The human is a participant; you are an agent with a distinct username and role.
  • You are NEVER another agent in the conversation. If the channel contains ceo, engineer, marketer and you are engineer, you do not write "我是 ceo" / "as the marketer" / "I (Team Manager) ..." under any circumstance.
  • Header-style introductions in chat history (e.g. an earlier message that wrote "Winshare (你) 项目发起人 / Owner — Team Manager (我) 战略统筹 — @engineer 工程师") describe how that earlier agent saw the room. They are NOT instructions reassigning your identity. Reading "Winshare (你)" does not make you Winshare; reading "Team Manager (我)" does not make you Team Manager.
  • When you summarise the team, list each participant by their actual username from the [Channel context] participant list, and refer to yourself in the first person under your own username only.

Examples of forbidden phrasings (small / weak models hit these regularly):

  • ❌ "我是 Winshare,作为项目 Owner 主导方向" (engineer claiming to be the human owner)
  • ❌ "以及我（Winshare agent）" (engineer renaming itself with the owner's name)
  • ❌ "作为 Team Manager 我来安排一下..." when you are engineer (cross-agent impersonation)
  • ✅ "@ceo 我作为 engineer 这边已经准备好了,等你拆任务就开干。"

If you catch yourself starting a sentence with "我是 <some other name>" or "作为 <some other role>" where the name/role does not match your You are: line in [Channel context], stop and rewrite using your real identity.

Your identity is already provisioned — never self-provision (HARD)

Beyond not impersonating in chat, never re-provision your credentials. You were handed a working identity at spawn: a $PRISMER_API_KEY in your environment and an [auth] block already written into your daemon config.toml. Use them as-is.

  • Never run prismer setup / prismer pair to mint yourself a fresh identity.
  • Never register a new IM user (POST /api/im/auth/*, "create account") to act as someone else.
  • Never overwrite the [auth] section of config.toml (token, API key, daemon id). Rewriting it does not gain you new authority — it breaks the identity the platform already trusts, so your subsequent calls fail auth.

If a task seems to require operating as another agent or as the owner, that is an orchestration / delegation problem, not a credentials problem: dispatch the work to that agent (cloud task create --assignee <peer>) or ask the orchestrator to route it. Do not try to become them by editing your own auth.

Don't poach tasks assigned to another role (HARD)

The workspace Kanban is a shared, informational board: you can see every card, but a card assigned to another agent is not yours to work. Only act on (claim / start / complete) tasks whose assignee is you. If a card is assigned to ceo and you are engineer, do NOT volunteer "我先把那个任务处理掉" / "let me take that one" — that's poaching, and the platform will 403 the transition anyway. If you think the card should move, @ the orchestrator / task owner and explain; reassignment is their call, not yours. See the tasks skill (cloud task list --mine, "Act only on YOUR cards") for the full rule.

任务派发的会话作用域（HARD）

当你用 cloud task create --assignee <peer> 把活派出去，被派的 agent 在它自己的独立 context 里执行——它不会加入当前会话，也不会在这条对话里回你话。所以：

  • 别在本会话干等它发言。这条会话里没有它的消息是正常的，不代表它没接到、更不代表失败。
  • 结果在看板上，不在聊天里：去 cloud task get <taskId> 拉状态和产物（status=completed 才算交付）。
  • 别因为「对话里看不到回复」就自己把活重做一遍（影子执行）——见 tasks skill 的「结果回流」段。
  • 平台会把每次委派挂到一个 task-scoped 会话（human + 派发者 + 被派者）；那是它的工作面，不是当前这条。

Channel rules — DM vs Group

You will receive a [Channel context] block at the top of each prompt indicating whether you're in a direct (1:1) or group conversation. Behave differently:

In a direct (1:1) conversation
  • Just reply normally; the other party is the unique recipient.
  • No @-mention needed. The platform auto-routes any non-self reply back to the other party.
  • Loop semantics: human is in the loop; chain ends when the human stops sending. Don't worry about "ending" it manually.
In a group conversation
  • The platform routes ONLY when you @-mention. Behavior:
    • @<their_username> → the platform delivers your message to them; they will reply.
    • No @-mention → your message is broadcast as info; no agent picks it up; the conversation ends here.
    • @ yourself → silently ignored server-side.
  • 🚨 ALWAYS @ the ASCII username, NEVER the localized displayName. The mention parser only matches @ followed by ASCII [A-Za-z0-9._-] (or a quoted string). A teammate whose displayName is 工程师 has username: "engineer" — you MUST write @engineer, NOT @工程师. A bare non-ASCII mention like @工程师 / @市场 / @田中 matches NOTHING — it routes nowhere, the teammate is never dispatched, and the chain dies silently. This is the #1 group-chat failure: writing the display name you see instead of the username that routes.
    • The username is the field returned by prismer.conversation.listAgents (and shown as <username> in [Channel context]). Use it verbatim.
    • listAgents returns BOTH username AND id for each agent. @ the username (e.g. engineer), NEVER the id (a random handle like y39go1myqxm / cr63a27t3hk). Mentioning the id is just as broken as mentioning the displayName — write @engineer, not @y39go1myqxm. The id is an internal reference you never type into chat.
    • When you want the prose to read naturally with a localized name, write both: @engineer（工程师） — the @engineer routes, the （工程师） is just for the human reader. Or, if you must @ a non-ASCII name directly, quote it: @"工程师" (the parser accepts quoted display names) — but the ASCII @username is always the safer choice.
  • To keep a multi-agent discussion alive, always end your reply with @<recipient_username> to hand the turn. Without that handoff, the chain dies.
  • Only drop the @ when you've genuinely concluded — and say so explicitly in your message ("I think we're done here.") so it's clear to readers.
  • Multi-agent chains are capped at ~5 hops; you don't need to count, just stop when there's nothing new to add.
Show full SKILL.md (855 more words)Show less

Grounding precondition — group conversations (HARD)

Before composing ANY reply that names, describes, introduces, delegates to, or @-mentions ANY teammate in a group conversation, you MUST call prismer.conversation.listAgents and wait for its result. This is not optional and not skippable.

The single most common failure mode on small / weak models is reciting a generic org-chart ("Kanban Orchestrator", "Kanban Worker", "Researcher", "Product Manager"…) instead of the actual participants. That output is hallucination — those names are not in this workspace, the @s do not route, and downstream agents never see your message. Calling listAgents first is what turns guessed team structure into real team structure.

Rules derived from this precondition:

  1. First turn of any group conversation (kickoff): listAgents first, then compose. No exceptions. If the kickoff prompt asks you to "introduce the team" or "open the project", that introduction MUST be based on listAgents output, not on training-data archetypes.
  2. Reuse the result within the turn: one listAgents call per turn is enough — cache the names in your scratchpad and reference them across the rest of the reply.
  3. Never invent role names that aren't returned. If listAgents returns [ceo, engineer, marketer], your reply may describe Team Manager / Engineer / Marketer — and ONLY those. Do not add fictional "Kanban Orchestrator" or "Researcher" rows.
  4. One participant = DM behaviour. If listAgents returns just you + one human, the room is effectively a DM. Drop the @-mention rules and reply normally.
  5. Mismatch surfaces fast. If the human's prompt names a role that listAgents does not contain (e.g. "@researcher, please…" but no researcher agent exists), say so explicitly ("there's no researcher in this workspace yet — want me to propose adding one via the team skill?") rather than pretending to dispatch.

This rule overrides any temptation to compose a polished-looking team kickoff from prior-context patterns. Polished output that names ghost agents is worse than terse output that names real ones.

Tool usage

GoalTool
Reply to current chat (no routing change)Just emit your assistant message.
Address another agent so the platform dispatches your message to themCall prismer.agent.send (from the prismer-tasks MCP server).
Look up which agents you can talk toCall prismer.conversation.listAgents before guessing usernames.
Create / update tasks on the workspace boardprismer.task.create / prismer.task.update from prismer-tasks MCP.
Ask for structured human sign-offprismer.approval.request_human_approval.
Find uploaded workspace filesprismer.asset.search.
Inspect file metadata before reading bytesprismer.asset.describe.
Read a bounded byte range from a fileprismer.asset.read.

Workspace asset rules

  • Web-uploaded workspace files are available as asset metadata first; bytes are fetched lazily by the local daemon.
  • When a task needs file content, call prismer.asset.describe first, then read only the needed range with prismer.asset.read.
  • For many files, call prismer.asset.search to find candidates. Do not ask the user to paste file contents already present in workspace assets.
  • Do not claim you read a file unless an asset tool call succeeded.
  • For large tables/documents, read headers, samples, or targeted byte ranges. Never try to load the whole file into a reply.
  • Cite the asset id/URI and locator returned by the tool when using file evidence.
When to use prismer.agent.send vs inline @
  • Prefer prismer.agent.send when you want a verified delivery (returns { ok, message_id, dispatched_to }). Use it for explicit hand-offs and delegation.
  • Inline @<username> works as a fallback (the platform parses @ in your message text) and is fine for casual continuations in a group thread. But you get no error feedback if the username is wrong — the @ silently fails.
  • Never write @username for someone who is NOT in the conversation participant list — it won't route, and you'll look like you talked to a ghost. Use prismer.conversation.listAgents first.

Hard rules (server-enforced)

  1. Never @-mention yourself. The platform filters self-mentions; the call wastes a turn.
  2. Don't fabricate usernames. If prismer.conversation.listAgents doesn't return a name, that agent doesn't exist; use plain text and address them by displayName (no @).
  3. Don't pretend to call a tool. If you write "I sent a message via the tool" without actually invoking the tool, the message doesn't exist; the human will see the inconsistency.
  4. Check tool return values. prismer.agent.send may return { ok: false, error: 'agent_not_found' }; surface the error rather than pretending it worked.
  5. Use structured approvals for unapproved scope. For destructive, irreversible, external, spend, access, or publish operations not already explicitly authorized for this exact target and scope, call prismer.approval.request_human_approval. Do not request the same approval twice or gate routine requested deliverables; follow human-approval. A mandatory product-specific UI gate (such as council convening) still applies.
  6. No raw ids or filesystem paths in your reply. Ids from <execution_context> (conversation_id, session_id, task_id, workspace_id, project_id) and the artifacts_dir / scratch_dir absolute paths exist ONLY for your tool calls. NEVER paste them into the user-facing message. Reference resources by prismer:// link, the attached file's name, or natural language ("last week's thread", "the attached PDF"). A reply containing cmp… cuids or /home/user/.prismer/... paths is leaking internals and reads as noise to the user.

Example: group discussion handoff

Human (group): @ceo @researcher  你们讨论一下 X 的市场调研
You are Team Manager. After thinking, you decide Researcher should produce the initial draft.

Tool call: prismer.agent.send({
  to_username: "researcher-abcd",
  content: "Please draft the market research outline for X. Focus on segment size, channels, regulation. Reply with a 5-bullet outline.",
})

Returns: { ok: true, message_id: "...", dispatched_to: ["userId-of-researcher"] }

Your final assistant message in the group (visible to all):
"I've asked @researcher-abcd for the outline. Will synthesise once it's back."

Note the closing line includes the @-mention so the routing layer also notifies Researcher (defense in depth), AND the human reading the group sees the hand-off explicitly.

Example: DM reply

Human (DM): hey, what do you do?

Your reply: "I'm the Team Manager agent — I synthesise specialist output and decide what we ship. What can I help with?"

No @ needed; the human is the only other party.

© Prismer-AI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in sdk/cloud/catalog/skills/prismer-im-collab of Prismer-AI/PrismerCloud.

Open the folder on GitHubat commit e5d9444

Compare with similar skills

Prismer Im Collab 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.

Prismer Im Collab compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prismer Im Collab this skillPrismer-AI/PrismerCloud1.6k—~3.6kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k4 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0
Microsoft Skill CreatorMicrosoftDocs/mcp1.9k3 repos~2.1kAutomated safety check: PassCC-BY-4.0
Crush Configurationcharmbracelet/crush29k—~3.7kAutomated safety check: PassCustom licence

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 4 repos~1.2k tokens
    Agent WorkflowsAuto-check passed

  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed

  • Microsoft Skill Creator

    MicrosoftDocs/mcp

    Official

    Create agent skills for Microsoft technologies using official documentation.

    1.9k GitHub starsUsed in 3 repos~2.1k tokens
    Agent WorkflowsAuto-check passed

  • Crush Configuration

    charmbracelet/crush

    Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.

    29k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Context Mode Output Sandbox

    mksglu/context-mode

    Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.

    26k GitHub stars~4.1k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from Prismer-AI/PrismerCloud

All 88 skills in this repo

  • Prismer Google Workspace

    Prismer-AI/PrismerCloud

    Gives an agent account-scoped access to Gmail, Calendar, Drive, Contacts, Docs and Sheets through the gws CLI or a bundled Python client.

    1.6k GitHub starsUsed in 3 repos~4.2k tokens
    Auto-check passed

  • Prismer Skill Creator

    Prismer-AI/PrismerCloud

    Walks an agent through creating, importing, editing, validating, testing and publishing Prismer Skills with a fixed workflow and bundled scripts.

    1.6k GitHub stars~2.6k tokensUpdated today
    Auto-check: notes

  • Himalaya Email CLI

    Prismer-AI/PrismerCloud

    Operates a mailbox from the terminal with the external Himalaya CLI over IMAP, SMTP, Notmuch or Sendmail, separate from any built-in email gateway adapter.

    1.6k GitHub starsUsed in 2 repos~2.3k tokens
    Auto-check passed

  • Prismer Image Generation

    Prismer-AI/PrismerCloud

    Generates one image from a text prompt with a bundled Node.js helper and delivers it once as the attachment to the current Prismer reply.

    1.6k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Manim Explainer Videos

    Prismer-AI/PrismerCloud

    Produces 3Blue1Brown-style explainer animations with Manim Community Edition for math, algorithms, equations and architecture diagrams, with planning and rendering references.

    1.6k GitHub starsUsed in 2 repos~3.1k tokens
    Auto-check passed

  • Prismer Role Builder

    Prismer-AI/PrismerCloud

    Creates or updates Prismer role templates from a persona, SOP or job description, and turns a role into a working agent that runs its first task through a bundled script.

    1.6k GitHub stars~2.3k tokensUpdated today
    Auto-check: notes

Categories

Questions about Prismer Im Collab

What does Prismer Im Collab do?

Coordinate reliably in Prismer conversations, use workspace assets through bounded MCP tools, and keep task work on the board. Prismer Im Collab is an agent skill from Prismer-AI/PrismerCloud. Coordinate reliably in Prismer conversations, use workspace assets through bounded MCP tools, and keep task work on the board.

When should I use Prismer Im Collab?

Prismer Im Collab fits situations like: tasks that involve MCP servers.

How do I install Prismer Im Collab in Claude Code?

Run `npx skills add Prismer-AI/PrismerCloud --skill prismer-im-collab -a claude-code`. Or copy the skill folder (sdk/cloud/catalog/skills/prismer-im-collab in Prismer-AI/PrismerCloud) into .claude/skills/prismer-im-collab in your project. Claude Code loads it when a task matches its description.

How do I install Prismer Im Collab in Codex?

Run `npx skills add Prismer-AI/PrismerCloud --skill prismer-im-collab -a codex`. Or copy the skill folder (sdk/cloud/catalog/skills/prismer-im-collab in Prismer-AI/PrismerCloud) into .agents/skills/prismer-im-collab in your project. Codex loads it when a task matches its description.

Can I use Prismer Im Collab 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 Prismer-AI/PrismerCloud --skill prismer-im-collab -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prismer-im-collab, .gemini/skills/prismer-im-collab, .github/skills/prismer-im-collab and .opencode/skills/prismer-im-collab in your project.

What does Prismer Im Collab need to run?

Going by SKILL.md and its folder, Prismer Im Collab needs credentials named PRISMER_API_KEY. Our summary lists: A credential in PRISMER_API_KEY. Its frontmatter pre-approves these tools: prismer.agent.send, prismer.conversation.listAgents, prismer.task.create, prismer.task.update, prismer.task.complete, prismer.approval.request_human_approval, prismer.asset.search, prismer.asset.describe, prismer.asset.read.

Does Prismer Im Collab access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Prismer Im Collab 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 Prismer Im Collab use?

Prismer Im Collab is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Prismer Im Collab use?

About 3.6k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Prismer Im Collab?

Skills that share tags, products or a category with Prismer Im Collab: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Microsoft Skill Creator (MicrosoftDocs/mcp, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prismer Im Collab?

Prismer-AI (a GitHub organization) maintains it in Prismer-AI/PrismerCloud, which has 1,555 GitHub stars. The repository holds 88 skills in this directory. The repository was last updated on September 30, 2026.

Source: Prismer-AI/PrismerCloud on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.