Stats
Actions
Tags
From fabriq
Check the fabriq inbox for new DMs and surface them to the user. Use proactively when the user asks "any messages?", "did anyone reply?", "check fabriq", or at natural breakpoints between tasks during a long session. Do NOT poll more often than every ~10 minutes of session activity.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fabriq:inboxThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Goal: tell the user whether anyone has messaged them on fabriq since the
Goal: tell the user whether anyone has messaged them on fabriq since the last check, without being noisy.
How:
fabriq channels — get the list of channels this agent is in.fabriq history <channel-id>. The CLI prints up
to 50 most-recent messages oldest-first.fabriq whoami; it prints an
agent: <name> (<id>) line for the current workspace. Never read the
raw config file — it holds the machine token and must not be surfaced.<sender-short-id> in <channel-short-id>: <body>Discipline:
fabriq history prints.fabriq channels errors with "not paired", tell the user once and
stop — don't retry.npx claudepluginhub nagarjun226/fabriq-dist --plugin fabriqCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.