本文へ移動
cccskills
無料GitHub で公開

codexkit-inbox-priority-triage

Triage email, Slack, ticket, or shared request backlogs into priority buckets, owners, and next actions. Use when the work is repetitive queue handling, intake cleanup, or response sorting. Do not use for strategic decisions, policy interpretation, or substantive contract review.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md2.8 KB
  • agents/openai.yaml164 B

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Inbox Priority Triage

Purpose

Turn a messy request backlog into a short, actionable queue.

When to use

  • an inbox or request list needs fast prioritization
  • requests arrive in different formats and need one view
  • a manager needs owners and next actions, not long summaries

When not to use

  • the user needs deep analysis or a recommendation memo
  • the queue contains legal, finance, or policy work that needs expert review

Inputs

  • source inbox, backlog, or copied request list
  • priority rules or SLA if available
  • known owners, teams, or routing lanes

Procedure

  1. Normalize each item into request, owner, due date, and current state.
  2. Group duplicates and merge obviously repeated asks.
  3. Sort into priority buckets such as urgent, this week, waiting, and archive.
  4. Flag missing owner, missing deadline, or missing context.
  5. End with a short next-action queue.

Output

  • prioritized request list
  • owner and due-date gaps
  • next actions by person or lane

Definition of done

  • the queue is shorter and easier to act on
  • duplicates and stale items are collapsed
  • every urgent item has an owner or a routing gap called out

Examples

  • "Sort this shared inbox into urgent, this week, and waiting."
  • "Clean up this backlog of internal requests and tell me who should take each one."

Quality Criteria

  • Trigger conditions and input requirements are unambiguous
  • Each automated step produces a verifiable output
  • Error handling and fallback paths are defined
  • Manual override points are documented

Verification (4C)

CheckQuestion
CorrectnessDoes the workflow produce the expected output for the defined inputs?
CompletenessAre all trigger conditions, edge cases, and error paths handled?
Context-fitIs the automation appropriate for the frequency and criticality of this task?
ConsequenceIf this ran unattended and failed silently, what would the downstream impact be?

Edge Cases

  • Input format varies unexpectedly — Add a normalization step at entry. Alert the operator on format mismatches.
  • Downstream system is unavailable — Queue the output and retry with exponential backoff. Alert after N failures.
  • Partial execution completes — Ensure idempotency — re-running from the start produces the same result without duplication.

Changelog

  • v1.0.0 — Initial release

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design rigorous A/B test plans with hypothesis, sample size calculation, Minimum Detectable Effect (MDE), randomization strategy, and decision rules. Includes guardrail metrics and rollout playbook. Use when planning product experiments, conversion optimization, or data-driven feature decisions.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月8日 更新

Review REST and GraphQL API designs for consistency, usability, and best practices. Covers naming conventions, versioning strategy, error format, pagination, authentication patterns, and breaking change detection. Use when reviewing API specs, designing new APIs, or auditing existing endpoints.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月8日 更新

Write Architecture Decision Records (ADRs) following the Michael Nygard format. Captures context, options considered, decision rationale, and consequences. Use when making technology choices, framework selections, or any architectural decision that future developers need to understand.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月8日 更新

Assess organizational readiness for financial audits (internal or external). Map assertions to account balances, check evidence completeness, score readiness using a Red/Amber/Green framework, and generate a remediation timeline. Aligned with SOX, IFRS, and GAAP audit standards. Use before scheduled audits or when preparing for first-time compliance.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月8日 更新

Design safe recurring Codex automations with clear prompts, outputs, schedules, and gating rules.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月8日 更新

Refine Product Backlog Items to meet INVEST criteria. Write User Stories with Acceptance Criteria in Given/When/Then format, estimate with Story Points, and flag dependencies. Use before sprint planning when backlog items need grooming. Do not use to prioritize the backlog — that is the Product Owner's decision.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月8日 更新

hoavdc のスキルをすべて見る

このスキルの問題を報告する