- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add paperclipai/paperclip --skill status-card-query -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add paperclipai/paperclip --skill status-card-query -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add paperclipai/paperclip --skill status-card-query -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add paperclipai/paperclip --skill status-card-query -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/paperclipai/paperclip/tree/HEAD/packages/skills-catalog/catalog/bundled/paperclip-operations/status-card-query게시자 제공
Use this skill in one of two modes:
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:
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:
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.
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.
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.
q for status, priority, assignee, project, label, and recency.updatedWithin whenever the prompt says recent, current, this week, lately, or otherwise implies a moving window.q short and specific. Avoid copying the whole prose prompt into it.scope: "issues", offset: 0, and an explicit bounded limit on every query.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:
{
"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:
{
"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.
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.
incremental, patch the supplied previous Markdown using only the changed issues. Do not refetch the issue list.full, rebuild from the supplied bounded snapshot. Do not expand the scope with issue-list endpoint calls.STATUS: lines and the <<<SUMMARY-DRAFT>>> block, then write the final Markdown to PUT /api/status-cards/{statusCardId}/summary from the assigned run.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.
---name: status-card-querydescription: Create and maintain agent-authored Paperclip status cards, or compile a prose interest prompt into bounded…---# packages/skills-catalog/catalog/bundled/paperclip-operations/status-card-query/SKILL.mdFAQ
게시자에게서 packages/skills-catalog/catalog/bundled/paperclip-operations/status-card-query/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/paperclipai/paperclip에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.