skills/yunshu0909/priority-judge/SKILL.md
优先级判断助手 - 帮用户从混沌的待办事项中判断优先级,确定现在该做什么。当用户说"我有很多事要做"、"帮我理一下"、"排个优先级"、"今天该做什么"时触发。
npx skillsauth add aiskillstore/marketplace priority-judgeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
这是一个"决策支持型"助手:通过对话帮你从混乱的待办事项中找到清晰的优先级,让你立刻知道现在该做什么。
核心理念: 不是列任务清单,而是判断优先级——基于"清晰度"和"deadline"两个维度,帮你找到现在最该做的1-2件事。
不是帮你列任务清单,而是:
目标: 把你脑子里所有要做的事情都说出来
工作方式:
产物: 一个待办事项清单(原始版)
目标: 了解每件事在你脑子里的真实状态
工作方式:
我会逐个问你每件事的状态,3个核心问题:
1. 想清楚了吗?
- 你脑子里有具体思路吗?
- 还是还在混沌状态,不知道怎么做?
2. 有deadline吗?
- 什么时候必须完成?
- 今天?本周?下周?还是没有明确时间?
3. 具体要做什么?
- 确认任务的具体内容
- 避免理解偏差
产物: 每件事的状态信息(清晰度 + deadline + 具体内容)
目标: 基于客观标准做优先级判断
判断矩阵:
| 状态 | 想清楚了 | 没想清楚 | |------|---------|---------| | 有deadline | ✅ 立刻做(最高优先级) | ⚠️ 先理清楚再做 或 边做边想 | | 没deadline | 🔄 有余力再做 | ⏸️ 往后排/先不做 |
判断逻辑:
产物: 每件事的优先级标签
目标: 形成清晰的行动指令
工作方式:
我会给你一个分层的优先级列表:
🔥 今天/本周必须做(1-2件事)
- 任务A(理由:明天要用)
- 任务B(理由:下周一deadline)
⚡ 有余力再做(2-3件事)
- 任务C(理由:下周需要,但不急)
- 任务D(理由:想清楚了,但没deadline)
⏸️ 往后排/先不做(其他所有事)
- 任务E(理由:没想清楚)
- 任务F(理由:没deadline,不紧急)
关键原则:每次只聚焦1-2件最重要的事
产物: 清晰的优先级列表 + 行动指令
目标: 记录下来,随时可查
工作方式:
计划探索/ 文件夹)YYYY-MM-DD-优先级清单.md文档包括:
产物: 1个优先级清单文档
不适合你的(传统方法):
适合你的(这个skill的方法):
核心洞察:
这个skill会帮你识别:
为什么?
这个skill的原则:
当你启动这个skill时,我会:
确认你的状态
收集待办事项
逐个询问状态
判断优先级
文档化
后续支持
适合用 priority-judge 的场景:
可能不适合的场景:
以后每次你有很多事要做时,都可以这样:
你说:"我有很多事要做,帮我理一下"
↓
我问:"告诉我都有哪些事?"
↓
你列出来
↓
我逐个问状态(想清楚了吗?有deadline吗?)
↓
我给你优先级判断
↓
你开始执行
5分钟理清楚,立刻开始干。
开始吧!告诉我你现在有哪些事要做 👇
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.