Specky + Claude
Build your own Specky board in Claude
Connect Specky to Claude, paste a recipe, and Claude builds you a private board over your live workspace: what needs your review, which goals are slipping, which signals deserve an insight. No code, and nothing to host.
1. What an artifact is
An artifact is a small app Claude writes and runs next to your chat, such as a dashboard, a tracker or a checklist. With Specky connected, Claude fills it from your real workspace instead of sample data, and the board stays private to you.
2. Connect Specky to Claude
You add Specky once, as a custom connector. After that, any chat can use it.
- 1In Claude, open Customize → Connectors, then choose + Add → Add custom connector.
- 2Name it Specky and paste the URL
https://www.specky.space/api/mcp. - 3No key. Approve the browser prompt, sign in to Specky and pick a workspace.
On a Claude Team or Enterprise plan, an Owner adds Specky first under Organization settings → Connectors; each member then connects it from Customize → Connectors. You can revoke access any time in Specky under Settings → Developer → Connected apps.
3. Paste a recipe
Each recipe is a prompt. Copy one, paste it into a new Claude chat and send it. Claude calls the Specky connector with read-only tools and builds the board. Each recipe starts with a 7-day window, and you can change it on the board.
If your Claude client supports MCP prompts, the same three recipes also appear as built-in commands from the Specky connector, so you can run them without pasting.
Founder board
A private board over your live Specky workspace: what needs review, what is at risk or stalled, blocked coding agents, recent signals, the opportunity pipeline and today's brief.
Build me a private interactive founder board as a Claude artifact, using my connected Specky connector. It should tell me in one glance what needs me today. 1. Use my real workspace - Find the Specky connector and call its tools now. Read only with: list_workspace_items, list_inbox_items, list_documents, list_recent_signals, list_agent_runs. - Never use sample, placeholder or invented data. If a call fails, show the error on the board instead of filling the gap. - If the Specky connector is not connected, stop and ask me to connect it as a custom connector at https://www.specky.space/api/mcp. 2. Be honest about scope - Show what was loaded: which tool and filters, the item count, the fetched time, and whether more results remain (has_more is true, or a tool without has_more returned exactly its limit). - Never present a partial list or a failed request as the complete picture. Show a missing field as "unknown", never as zero. 3. Load - list_workspace_items with limit 100. Follow next_cursor for up to 5 pages; if has_more is still true after that, say so on the board. - For Stalled, also call list_workspace_items with types ["opportunity","experiment","ticket"], updated_before set to now minus the stalled window (14 days), and limit 100, and merge it with the pages above by id. If that call returns has_more true, say Stalled may be incomplete. - list_inbox_items with status "pending" and list_documents with status "review", each with limit 100. - list_recent_signals with source_types ["SLACK","JIRA","GITHUB","GONG","PENDO","POSTHOG","INTERVIEW","USER_RESEARCH","user_research","RESEARCH_STUDY","RESEARCH_OBSERVATION","RESEARCH_FINDING","PUBLIC_FEEDBACK","PUBLIC_FEEDBACK_COMMENT","FEEDBACK","FEEDBACK_INTEL","FILE_UPLOAD","GOOGLE_DRIVE","NOTION","CONFLUENCE","CHROME_EXTENSION","COMPETITIVE_INTEL","MARKET_INTEL","HIRING_INTEL"] and limit 100. Pass this list exactly: it keeps product items, Specky documents and agent records out. Say so in the scope line, e.g. "N signals from customer and team sources". - list_agent_runs with limit 100. It has no has_more, so if it returned exactly its limit, more may exist. 4. Focus view Named groups. Each card says why it qualifies, in one line. An item may sit in several groups, but the header totals count unique items. Inside a group, rank by waiting time: the longest-waiting item first. - Review now: pending inbox items and documents in review. - Unblock agents: coding-agent runs whose data.status is awaiting_review, changes_requested, blocked or failed. Title the card with data.ticket_title (else name); the reason names the status and data.next_action when present. Link to data.pull_request_url when present, else url. - At risk: OKRs with status at_risk or off_track. - Stalled: opportunities, experiments and tickets whose status, ignoring case, is not shipped, done, closed, completed, validated or invalidated, with no update in the last 14 days. - Recent signals: signals captured in the last 7 days. - Needs checking: items with too little evidence to judge, such as a missing status. Keep this group visible even when it is empty. - Every card links to its item's url in Specky. - Label items whose fields.origin is "onboarding" as "AI-generated at signup", so they never read as my team's own work. 5. Pipeline Opportunity lanes by status, ignoring case, in order: identified, proposed, planned, in_progress, testing, validated, shipped, plus an "Other" lane for any other or missing status. Show empty lanes. Time since last update is not time in a stage; the connector only gives updated_at, so label it "last update". 6. Today's brief Up to 3 suggested next actions, each pointing at a real loaded item by name and link. If nothing qualifies, say so; never pad the list. 7. Ask Claude A question box over the loaded data. Use in-artifact Claude when available, only on a click, never on load or in a loop: it uses the viewer's own usage. Otherwise offer filters plus a "Copy question for Claude" button. No fake chat and no canned answers. 8. Editable thresholds Let me change the stalled window (default 14 days) and the recent-signal window (default 7 days) on the board, and regroup instantly without reloading. 9. Stay read-only - The artifact must never call any Specky tool not listed in step 1. - Drafting happens in this chat, not in the artifact: use a "Copy prompt for Claude" button whose text names the exact item id and tells Claude to draft in the chat first and save nothing until I approve. 10. Make it work - Clean layout, readable cards, status badges, a search box and a details drawer. Usable at narrow width. - If the artifact cannot re-call the connector itself, label the data "Snapshot" with its fetched time. Never show a "Live" label you can't back. - Keep the artifact private. People outside my organization get no connector access, so share this recipe, never a board that carries my data.
Signal triage
A private triage board for the signals Specky captured recently, grouped by source, with a one-click hand-off to draft an insight in Claude.
Build me a private interactive signal triage board as a Claude artifact, using my connected Specky connector. It should help me decide which recent customer and team signals deserve an insight. 1. Use my real workspace - Find the Specky connector and call its tools now. Read only with: list_recent_signals, list_workspace_items, read_workspace_item. - Never use sample, placeholder or invented data. If a call fails, show the error on the board instead of filling the gap. - If the Specky connector is not connected, stop and ask me to connect it as a custom connector at https://www.specky.space/api/mcp. 2. Be honest about scope - Show what was loaded: which tool and filters, the item count, the fetched time, and whether more results remain (has_more is true, or a tool without has_more returned exactly its limit). - Never present a partial list or a failed request as the complete picture. Show a missing field as "unknown", never as zero. 3. Load - list_recent_signals with source_types ["SLACK","JIRA","GITHUB","GONG","PENDO","POSTHOG","INTERVIEW","USER_RESEARCH","user_research","RESEARCH_STUDY","RESEARCH_OBSERVATION","RESEARCH_FINDING","PUBLIC_FEEDBACK","PUBLIC_FEEDBACK_COMMENT","FEEDBACK","FEEDBACK_INTEL","FILE_UPLOAD","GOOGLE_DRIVE","NOTION","CONFLUENCE","CHROME_EXTENSION","COMPETITIVE_INTEL","MARKET_INTEL","HIRING_INTEL"] and limit 100. Pass this list exactly: it keeps product items, Specky documents and agent records out. Say so in the scope line, e.g. "N signals from customer and team sources". - Keep signals captured in the last 7 days. The tool returns at most 100 rows and has no cursor: if the oldest row returned is still inside the window, say older signals in the window may be missing. - list_workspace_items with types ["insight"] and limit 100, to show which insights already exist. - read_workspace_item for one signal at a time, only when I open its details drawer. 4. Triage view - Group signals by source_type (Slack, Jira, Gong, extension captures and so on). Each group header shows its count; sources with no signals in the window are not shown. - Newest first inside a group. Each card shows the name, the excerpt, the captured time and a link to its url. - A side panel lists the existing insights by title and link, so I can spot a duplicate before drafting. The connector does not say which signals an insight cites, so never mark a signal as covered or uncovered. - A filter for source and a text search over name and excerpt. - Every card links to its item's url in Specky. - Label items whose fields.origin is "onboarding" as "AI-generated at signup", so they never read as my team's own work. 5. Turn into insight Each card has a "Turn into insight" button that copies a prompt for this chat, for example: "In Specky, read signal <id> with read_workspace_item and draft an insight from it. Draft the insight here in the chat first; only after I approve, save it with create_insight citing <id> in evidence_node_ids." Use the real id. create_insight saves a live insight, not a draft, so the approval step matters. 6. Editable window Let me change the window (default 7 days) on the board and regroup without reloading. 7. Stay read-only - The artifact must never call any Specky tool not listed in step 1. - Drafting happens in this chat, not in the artifact: use a "Copy prompt for Claude" button whose text names the exact item id and tells Claude to draft in the chat first and save nothing until I approve. 8. Make it work - Clean layout, readable cards, status badges, a search box and a details drawer. Usable at narrow width. - If the artifact cannot re-call the connector itself, label the data "Snapshot" with its fetched time. Never show a "Live" label you can't back. - Keep the artifact private. People outside my organization get no connector access, so share this recipe, never a board that carries my data.
OKR tracker
A private OKR tracker over your live Specky workspace: OKRs by quarter, key-result progress bars, at-risk OKRs first.
Build me a private interactive OKR tracker as a Claude artifact, using my connected Specky connector. It should show me which goals are slipping before the quarter ends. 1. Use my real workspace - Find the Specky connector and call its tools now. Read only with: list_workspace_items, read_workspace_item. - Never use sample, placeholder or invented data. If a call fails, show the error on the board instead of filling the gap. - If the Specky connector is not connected, stop and ask me to connect it as a custom connector at https://www.specky.space/api/mcp. 2. Be honest about scope - Show what was loaded: which tool and filters, the item count, the fetched time, and whether more results remain (has_more is true, or a tool without has_more returned exactly its limit). - Never present a partial list or a failed request as the complete picture. Show a missing field as "unknown", never as zero. 3. Load - list_workspace_items with types ["okr"] and limit 100. Follow next_cursor while has_more is true, up to 5 pages, and say so if more remain. - read_workspace_item for one OKR at a time, only when I open its details drawer. 4. Tracker view - Group OKRs by fields.quarter, newest quarter first. OKRs with no quarter go in a "No quarter" group. - Inside a quarter, at-risk first: off_track, then at_risk, then on_track, then any other or missing status (shown as "unknown"). - Each card shows the title, owner, status badge, last update and a link to its url. - One progress bar per key result in fields.key_results: current divided by target, only when both are numbers and target is not zero. Otherwise show the raw values and "progress unknown" instead of a bar. Never estimate a percentage. - Flag OKRs with no update in the last 7 days as "quiet". - Every card links to its item's url in Specky. - Label items whose fields.origin is "onboarding" as "AI-generated at signup", so they never read as my team's own work. 5. Summary strip Counts by status for the selected quarter, counting each OKR once. 6. Check-in hand-off Each card has a "Draft a check-in" button that copies a prompt for this chat, for example: "In Specky, read OKR <id> with read_workspace_item and draft a check-in: what moved, what is blocked, one next step per key result. Draft it here in the chat first; only after I approve, save it with create_document, which saves a draft." Use the real id. 7. Editable threshold Let me change the quiet window (default 7 days) on the board without reloading. 8. Stay read-only - The artifact must never call any Specky tool not listed in step 1. - Drafting happens in this chat, not in the artifact: use a "Copy prompt for Claude" button whose text names the exact item id and tells Claude to draft in the chat first and save nothing until I approve. 9. Make it work - Clean layout, readable cards, status badges, a search box and a details drawer. Usable at narrow width. - If the artifact cannot re-call the connector itself, label the data "Snapshot" with its fetched time. Never show a "Live" label you can't back. - Keep the artifact private. People outside my organization get no connector access, so share this recipe, never a board that carries my data.
4. What the board can and can't do
The board is a private view, not a shared dashboard. Know these before you send someone the link.
Everyone sees it through their own connection
The board does not carry your access. Each person who opens it loads data through their own Specky connection in Claude, so they see only what their own account can see.
People outside your organization see no data
They get no connector access, so the board stays empty for them. To share the idea, share the recipe, not the board.
Data refreshes on demand
The board loads when you open it or ask Claude to refresh. It does not update in the background, and it shows when the data was fetched.
The board is built to be read-only
It only calls Specky's read tools. Drafting happens in the Claude chat, and nothing is saved to your workspace until you approve it.
No Specky workspace yet?
The board is only as good as what is in your workspace. Connect Slack, Jira or your call recorder, and the signals, decisions and OKRs show up on the board.
Card required · Nothing charged until day 14 · 30-day refund