Agent skill

Status Card Query

Create and maintain agent-authored Paperclip status cards, or compile a prose interest prompt into bounded CompanySearchQuery objects and write the first summary from the assigned Summarizer run.

MITAuto-check passed

Install Status Card Query

skills CLI

$ npx skills add paperclipai/paperclip --skill status-card-query -a claude-code

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

GitHub CLI

$ gh skill install paperclipai/paperclip status-card-query --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/paperclipai/paperclip.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/skills-catalog/catalog/bundled/paperclip-operations/status-card-query .claude/skills/status-card-query && 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/

Paste into Claude Code

Install the "status-card-query" agent skill from https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/bundled/paperclip-operations/status-card-query into .claude/skills/status-card-query/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "status-card-query", 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

$skill-installer install https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/bundled/paperclip-operations/status-card-query

Type 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.

skills CLI

$ npx skills add paperclipai/paperclip --skill status-card-query -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install paperclipai/paperclip status-card-query --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/skills-catalog/catalog/bundled/paperclip-operations/status-card-query .agents/skills/status-card-query && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "status-card-query" agent skill from https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/bundled/paperclip-operations/status-card-query into .agents/skills/status-card-query/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "status-card-query", 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.

skills CLI

$ npx skills add paperclipai/paperclip --skill status-card-query -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install paperclipai/paperclip status-card-query --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/skills-catalog/catalog/bundled/paperclip-operations/status-card-query .cursor/skills/status-card-query && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "status-card-query" agent skill from https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/bundled/paperclip-operations/status-card-query into .cursor/skills/status-card-query/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "status-card-query", 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

$ gemini skills install https://github.com/paperclipai/paperclip.git --path packages/skills-catalog/catalog/bundled/paperclip-operations/status-card-query

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add paperclipai/paperclip --skill status-card-query -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install paperclipai/paperclip status-card-query --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/skills-catalog/catalog/bundled/paperclip-operations/status-card-query .gemini/skills/status-card-query && rm -rf skills-src

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

Paste into Gemini CLI

Install the "status-card-query" agent skill from https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/bundled/paperclip-operations/status-card-query into .gemini/skills/status-card-query/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "status-card-query", 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.

GitHub CLI

$ gh skill install paperclipai/paperclip status-card-query

Installs 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).

skills CLI

$ npx skills add paperclipai/paperclip --skill status-card-query -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/skills-catalog/catalog/bundled/paperclip-operations/status-card-query .github/skills/status-card-query && rm -rf skills-src

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

Paste into GitHub Copilot

Install the "status-card-query" agent skill from https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/bundled/paperclip-operations/status-card-query into .github/skills/status-card-query/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "status-card-query", 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.

skills CLI

$ npx skills add paperclipai/paperclip --skill status-card-query -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install paperclipai/paperclip status-card-query --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/skills-catalog/catalog/bundled/paperclip-operations/status-card-query .opencode/skills/status-card-query && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "status-card-query" agent skill from https://github.com/paperclipai/paperclip/tree/master/packages/skills-catalog/catalog/bundled/paperclip-operations/status-card-query into .opencode/skills/status-card-query/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "status-card-query", 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: status-card-query
GitHub stars: 100k
Token cost: ~1.6k tokens
SKILL.md length: 622 words
Files: 1
Skills in repo: 60
Repo updated: Oct 11, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Create and maintain agent-authored Paperclip status cards, or compile a prose interest prompt into bounded CompanySearchQuery objects and write the first summary from the assigned Summarizer run.

Works in 2 steps: Agent authoring: create or maintain a… → Summarizer compilation: compile a card's…
SKILL.md covers Agent-authored card recipe, Summarizer compilation, CompanySearchQuery and Compilation guidance, plus 2 more sections
Calls curl; needs PAPERCLIP_API_KEY

What it does

Status Card Query is an agent skill from paperclipai/paperclip. Create and maintain agent-authored Paperclip status cards, or compile a prose interest prompt into bounded CompanySearchQuery objects and write the first summary from the assigned Summarizer run.

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

The repository describes itself as: The open-source app everyone uses to manage agents at work. The licence is MIT.

Example prompts

“/status-card-query”

Requirements

A credential in PAPERCLIP_API_KEY

Workflow steps

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

Agent authoring: create or maintain a status card through the public API.
Summarizer compilation: compile a card's prose prompt into structured company-search queries and write the first summary from the assigned…

What it can do on your machine

Read from SKILL.md and the folder at commit de9ab8e. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- PAPERCLIP_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Status Card Query loads about 1.6k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 622 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~53
When it runs · the whole SKILL.md, loaded when a task matches: ~1.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 paperclipai/paperclip at commit de9ab8e, republished under its MIT licence (© paperclipai). 622 words, ~1,591 tokens.

Download SKILL.mdSave it as .claude/skills/status-card-query/SKILL.md (or your agent's skills folder).

name: status-card-query
description: Create and maintain agent-authored Paperclip status cards, or compile a prose interest prompt into bounded CompanySearchQuery objects and write the first summary from the assigned Summarizer run.
key: paperclipai/bundled/paperclip-operations/status-card-query
recommendedForRoles: general, manager
tags: paperclip, status, search, reporting, operations

Status card query

Use this skill in one of two modes:

Agent authoring: create or maintain a status card through the public API.
Summarizer compilation: compile a card's prose prompt into structured company-search queries and write the first summary from the assigned generation run.

Agent-authored card recipe

Agent-authored cards require tasks:assign, remain company-scoped, and are available only when enableStatusCards is enabled. An agent may manage only cards it authored, may author at most 20 cards, and may send at most 4,000 characters in interestPrompt.

Normalize the run-provided API base and create a manual card:

bash

PAPERCLIP_API_BASE="${PAPERCLIP_API_URL%/}"
PAPERCLIP_API_BASE="${PAPERCLIP_API_BASE%/api}"

curl -sS -X POST \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"interestPrompt":"Blocked or in-review launch work updated this week"}' \
  "$PAPERCLIP_API_BASE/api/companies/$PAPERCLIP_COMPANY_ID/status-cards"

Creation returns 201 and queues compilation automatically. Save the returned card id. To refine an owned card or request a refresh:

bash

curl -sS -X PATCH \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"interestPrompt":"Blocked or in-review launch work updated this week. Call out the single next decision."}' \
  "$PAPERCLIP_API_BASE/api/status-cards/$STATUS_CARD_ID"

curl -sS -X POST \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"full":false}' \
  "$PAPERCLIP_API_BASE/api/status-cards/$STATUS_CARD_ID/refresh"

Do not call /query or /summary while authoring. Those write-back routes are reserved for the assigned Summarizer generation issue and run.

Summarizer compilation

You are the Summarizer compiling a status card's prose interest prompt into structured Paperclip company-search queries. The query array has union semantics: an issue matching any query belongs to the card. Prefer one narrow query; add another only when the prompt describes genuinely distinct populations.

CompanySearchQuery

Each object accepts these fields:

q: optional free-text search across matching company resources. Use it only for concepts not represented by structured filters.
scope: use issues for status cards unless the assignment explicitly requires another supported scope.
status: issue-status array.
priority: issue-priority array.
assigneeAgentId / assigneeUserId: a resolved assignee id.
projectId: one resolved project UUID.
labelId: one resolved label UUID.
updatedWithin: a bounded duration such as 24h, 7d, 4w, or 3m.
sort: relevance, updated, created, or priority.
limit: 1–50. Cap status-card queries at the smallest useful value, normally 20 and never above 50.
offset: normally 0.

Resolve project and label names to ids before writing the query. Do not put human-readable names into projectId or labelId. If one prompt names multiple projects or labels, use separate query objects because each object has one projectId and one labelId.

Compilation guidance

Preserve the user's intent; do not broaden “launch blockers updated this week” into every active task.
Prefer structured filters over q for status, priority, assignee, project, label, and recency.
Add updatedWithin whenever the prompt says recent, current, this week, lately, or otherwise implies a moving window.
Keep q short and specific. Avoid copying the whole prose prompt into it.
Set scope: "issues", offset: 0, and an explicit bounded limit on every query.
Return at least one query. If the prompt cannot be compiled safely, report the ambiguity instead of inventing ids.

Show full SKILL.md (201 more words)Show less

Exact write-back sequence

The generation issue contains statusCardId, companyId, and generationIssueId. Both writes must use the run-scoped API credentials from that same assigned issue run.

First write the compiled query:

json

{
  "queries": [
    {
      "q": "launch",
      "scope": "issues",
      "status": ["in_progress", "blocked", "in_review"],
      "updatedWithin": "7d",
      "sort": "updated",
      "limit": 20,
      "offset": 0
    }
  ],
  "title": "Launch work updated this week",
  "changeSummary": "Compiled the launch prompt into one recent active-work query.",
  "generationIssueId": "<generation-issue-id>"
}

Send it to PUT /api/status-cards/{statusCardId}/query.

Then, without creating or waiting for another task, execute the stored scope, write the first full Markdown summary, and complete the same run with:

json

{
  "markdown": "<full status summary>",
  "title": "Launch work updated this week",
  "changeSummary": "Created the first full summary from the compiled query.",
  "generationIssueId": "<generation-issue-id>",
  "model": "<model-id>"
}

Send it to PUT /api/status-cards/{statusCardId}/summary. Never write either endpoint from an unrelated issue or run.

Update assignments

Later generation issues use the same summary write-back endpoint and include operation: "update", kind, trigger, the target fingerprint, and the exact changed-issue delta in their JSON payload.

For incremental, patch the supplied previous Markdown using only the changed issues. Do not refetch the issue list.
For full, rebuild from the supplied bounded snapshot. Do not expand the scope with issue-list endpoint calls.
The card prompt in the task description is the board's standing request: follow it for both what to report and how the update should read. It never overrides the streaming or write-back requirements.
Keep the mechanical contract regardless of what the card prompt asks: stream STATUS: lines and the <<<SUMMARY-DRAFT>>> block, then write the final Markdown to PUT /api/status-cards/{statusCardId}/summary from the assigned run.

Files

Just SKILL.md in packages/skills-catalog/catalog/bundled/paperclip-operations/status-card-query of paperclipai/paperclip.

Open the folder on GitHubat commit de9ab8e

Compare with similar skills

Status Card Query 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.

Status Card Query compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Status Card Query this skillpaperclipai/paperclip	100k	—	~1.6k	Automated safety check: Pass	MIT	today
PaperclipK-Dense-AI/scientific-agent-skills	48k	1 repos	~3.2k	Automated safety check: Notes	MIT	6 days ago
Authoring Skillsvercel/next.js	143k	—	~1k	Automated safety check: Pass	MIT	today
Hermes Agent Skill AuthoringNousResearch/hermes-agent	252k	—	~3.6k	Automated safety check: Pass	MIT	yesterday
Wiki Maintaineropenclaw/openclaw	392k	1 repos	~462	Automated safety check: Pass	MIT	today
Routing Card Authoringagentlas-ai/Agentlas-OS	1.6k	—	~2.7k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Paperclip
K-Dense-AI/scientific-agent-skills
Searches and reads biomedical papers, FDA/PMDA/EMA documents, clinical trials, and protein records with the GXL Paperclip CLI and Python SDK.
48k GitHub starsUsed in 1 repo~3.2k tokens
Research & ScienceAuto-check: notes
Authoring Skills
vercel/next.js
Official
How to create and maintain agent skills in .agents/skills/. An agent skill from vercel/next.js.
143k GitHub stars~1k tokensUpdated today
Agent WorkflowsAuto-check passed
Hermes Agent Skill Authoring
NousResearch/hermes-agent
Author in-repo SKILL.md files: frontmatter and structure. An agent skill from NousResearch/hermes-agent.
252k GitHub stars~3.6k tokensUpdated yesterday
Agent WorkflowsAuto-check passed
Wiki Maintainer
openclaw/openclaw
Maintain the OpenClaw memory wiki vault with deterministic pages, managed blocks, and source-backed updates.
392k GitHub starsUsed in 1 repo~462 tokens
Knowledge ManagementAuto-check passed
Routing Card Authoring
agentlas-ai/Agentlas-OS
A skill your agent uses whenever a build emits or repairs .agentlas/routing-card.json — the shared card contract for the single-agent builder, the team builder, and the packager.
1.6k GitHub stars~2.7k tokensUpdated today
AI & LLM EngineeringAuto-check passed
Configuring Oauth2 Authorization Flow
mukul975/Anthropic-Cybersecurity-Skills
Configures secure OAuth 2.0 authorization flows, including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant, covering flow selection, PKCE implementation, token…
34k GitHub stars~1.7k tokensUpdated 1 mo ago
Backend & APIsAuto-check passed

Questions about Status Card Query

What does Status Card Query do?

Create and maintain agent-authored Paperclip status cards, or compile a prose interest prompt into bounded CompanySearchQuery objects and write the first summary from the assigned Summarizer run. Status Card Query is an agent skill from paperclipai/paperclip. Create and maintain agent-authored Paperclip status cards, or compile a prose interest prompt into bounded CompanySearchQuery objects and write the first summary from the assigned Summarizer run.

How do I install Status Card Query in Claude Code?

Run `npx skills add paperclipai/paperclip --skill status-card-query -a claude-code`. Or copy the skill folder (packages/skills-catalog/catalog/bundled/paperclip-operations/status-card-query in paperclipai/paperclip) into .claude/skills/status-card-query in your project. Claude Code loads it when a task matches its description.

How do I install Status Card Query in Codex?

Run `npx skills add paperclipai/paperclip --skill status-card-query -a codex`. Or copy the skill folder (packages/skills-catalog/catalog/bundled/paperclip-operations/status-card-query in paperclipai/paperclip) into .agents/skills/status-card-query in your project. Codex loads it when a task matches its description.

Can I use Status Card Query 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 paperclipai/paperclip --skill status-card-query -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/status-card-query, .gemini/skills/status-card-query, .github/skills/status-card-query and .opencode/skills/status-card-query in your project.

What does Status Card Query need to run?

Going by SKILL.md and its folder, Status Card Query needs the command-line tools its instructions call (curl) and credentials named PAPERCLIP_API_KEY. Our summary lists: A credential in PAPERCLIP_API_KEY.

Does Status Card Query access the network?

SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Status Card Query 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 Status Card Query use?

Status Card Query 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 Status Card Query use?

About 1.6k tokens (SKILL.md is roughly 6.4k 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 Status Card Query?

Skills that share tags, products or a category with Status Card Query: Paperclip (K-Dense-AI/scientific-agent-skills, 48k stars), Authoring Skills (vercel/next.js, 143k stars), Hermes Agent Skill Authoring (NousResearch/hermes-agent, 252k stars) and Wiki Maintainer (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Status Card Query?

paperclipai (a GitHub organization) maintains it in paperclipai/paperclip, which has 99,905 GitHub stars. The repository holds 60 skills in this directory. The repository was last updated on October 11, 2026.

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

Status Card Query

Install Status Card Query

Facts

At a glance

What it does

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Status card query

Agent-authored card recipe

Summarizer compilation

CompanySearchQuery

Compilation guidance

Exact write-back sequence

Update assignments

Files

Compare with similar skills

Similar skills

Paperclip

Authoring Skills

Hermes Agent Skill Authoring

Wiki Maintainer

Routing Card Authoring

Configuring Oauth2 Authorization Flow

More from paperclipai/paperclip

Garden Inbox

Paperclip

Paperclip

Design Guide

Paperclip Page

Paperclip Create Agent

Questions about Status Card Query