Token导航 LogoToken导航

Agent Skill · 待分类

personal-productivity(个人生产力)

personal-productivity 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

personal-productivity 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,208 个 Skill 里排第 767。

总安装 7,932周安装 324GitHub Stars 3下载 2,540核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:personal-productivity(个人生产力)
来源仓库:https://github.com/oldwinter/skills
仓库路径:skills/personal-productivity
安装命令:
npx skills add https://github.com/oldwinter/skills --skill personal-productivity
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/oldwinter/skills --skill personal-productivity

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

用于处理 GitHub 仓库、Issue 和 Pull Request 协作信息。适合围绕代码变更和仓库状态进行整理与分析。可结合来源仓库 README 核验具体用法和权限范围。安装前建议确认是否会触发命令执行或文件读写操作。

personal-productivity 属于待分类类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/personal-productivity

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/oldwinter/skills --skill personal-productivity;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

personal-productivity 怎么安装?

在终端执行 npx skills add https://github.com/oldwinter/skills --skill personal-productivity。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

personal-productivity 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

personal-productivity 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

personal-productivity 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

personal-productivity 用的人多吗?

公开数据是累计安装 7,932 次,近一周安装 324 次,下载 2,540 次,GitHub 3 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

personal-productivity 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

待分类类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
infsh-cli

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
personal-productivity

个人生产力 · 本页

7,9323只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Personal Productivity

Scope

Covers

  • Designing a weekly timebox plan for a high-meeting-load job (meeting windows, focus blocks, admin buffers)
  • Building a write-it-down capture system so tasks don’t live in your head (inbox → lists → reviews)
  • Creating daily + weekly review rituals that keep you current without constant re-planning
  • Producing a practical 7-day rollout plan (small changes you can implement immediately)

When to use

  • “Help me timebox my week so I can handle meetings + deep work.”
  • “I keep forgetting tasks. Build me a write-it-down system and a review routine.”
  • “I’m juggling a demanding job plus side commitments (advising/board/etc.). Make it sustainable.”
  • “Create a personal productivity system I can follow next week.”

When NOT to use

  • You need medical/mental-health advice (including ADHD treatment), or you are in crisis. Seek professional help.
  • You want a team-wide process (meeting policy, org operating system). Use a team/ops skill instead.
  • You need a project plan, milestones, or delivery management. Use managing-timelines.
  • You primarily need to reduce burnout/energy drain (not just time). Use energy-management.

Inputs

Minimum required

  • Your role + primary responsibilities (and whether you manage people)
  • Your constraints/non-negotiables (time zones, caregiving, travel, on-call, deadlines)
  • A representative week (calendar text dump, recurring meetings list, or narrative)
  • Your current task system (or “none”) + tools you’re willing to use (any calendar + any to-do list works)
  • What “better” means in 2–4 weeks (e.g., fewer dropped tasks, more deep-work blocks, lower weekend spillover)

Missing-info strategy

  • Ask 3–5 questions at a time from references/INTAKE.md.
  • If the calendar is unavailable, proceed with a default-week draft using explicit assumptions and ask the user to correct it.
  • Do not request secrets, credentials, or sensitive personal/medical details.

Outputs (deliverables)

Produce a Personal Productivity System Pack (Markdown in chat; or as files if requested) in this order:

  1. Context Snapshot (goal, constraints, assumptions, success definition)
  2. Commitment & Workload Inventory (fixed commitments + “floating” responsibilities)
  3. Weekly Timebox Plan (meeting windows, focus blocks, admin buffers, protected time, weekend spillover rule)
  4. Capture + To-Do System Spec (inbox, lists, processing, prioritization, timeboxing method)
  5. Daily Plan + Shutdown Ritual (how you start the day; how you close loops)
  6. Weekly Review Ritual (calendar + task review; reset rules)
  7. 7-Day Rollout Plan (setup steps + first-week experiments)
  8. Risks / Open questions / Next steps (always included)

Templates: references/TEMPLATES.md Expanded guidance: references/WORKFLOW.md

Workflow (7 steps)

1) Intake + success definition + boundaries

  • Inputs: user context; references/INTAKE.md.
  • Actions: Confirm scope (personal productivity for career execution). Define “better” in 2–4 weeks and 1–2 measurable signals (e.g., dropped tasks/week, deep-work blocks/week). Confirm boundaries (not medical/therapy; not a team policy rewrite).
  • Outputs: Context Snapshot (draft) + assumptions/unknowns list.
  • Checks: Success definition is specific enough to evaluate after 2 weeks.

2) Build a commitment & workload inventory

  • Inputs: calendar/recur meetings; responsibilities; side commitments.
  • Actions: List fixed commitments (meetings, deadlines, recurring obligations) and floating workload (projects, people mgmt, admin). Identify 3–5 “high-leverage” responsibilities and the biggest sources of fragmentation.
  • Outputs: Commitment & Workload Inventory (table) + top constraints.
  • Checks: Inventory separates fixed vs flexible time and includes side commitments (if any).

3) Design the weekly timebox plan (default week)

  • Inputs: inventory; energy preferences; constraints.
  • Actions: Draft a default week: meeting windows, focus blocks, admin buffers, and protected personal time. Add explicit rules: meeting batching, buffer time, weekend spillover (if needed), and what gets timeboxed first.
  • Outputs: Weekly Timebox Plan (calendar-like block plan) + 5–8 rules.
  • Checks: At least 3 focus blocks/week exist; meeting time has limits or windows; buffers are real blocks (not wishes).

4) Specify the capture + to-do system (“write it down”)

  • Inputs: current tools; task volume; common failure modes (dropped tasks, unclear next actions).
  • Actions: Define: capture inbox, processing ritual, list taxonomy, and a prioritization rule. Ensure every task becomes either: (a) timeboxed on calendar, (b) next action on a list, (c) delegated, or (d) deleted.
  • Outputs: Capture + To-Do System Spec + “rules of the system”.
  • Checks: The system has a single trusted inbox and a daily processing rule that takes ≤15 minutes.

5) Add daily plan + shutdown ritual

  • Inputs: timebox plan; task system.
  • Actions: Create a daily routine: morning “top outcomes” + quick timeboxing; end-of-day shutdown (clear inbox, update next actions, plan first block tomorrow).
  • Outputs: Daily Plan + Shutdown Ritual (copy/paste checklist).
  • Checks: Ritual is small enough to actually do; includes handling of new tasks during the day (capture rule).

6) Add weekly review ritual (reset + recalibration)

  • Inputs: default week; backlog lists; upcoming commitments.
  • Actions: Create a weekly review to: reconcile calendar ↔ tasks, reset priorities, and re-timebox next week. Include a “kill list” (stop/defer) to prevent backlog bloat.
  • Outputs: Weekly Review Ritual + weekly reset checklist.
  • Checks: Review includes both (1) looking forward (next 2 weeks) and (2) backlog cleanup.

7) Quality gate + finalize rollout plan

  • Inputs: full draft pack.
  • Actions: Produce a 7-day rollout plan (setup + first experiments). Run references/CHECKLISTS.md and score with references/RUBRIC.md. Include Risks / Open questions / Next steps.
  • Outputs: Final Personal Productivity System Pack.
  • Checks: Next 7 days have specific actions scheduled; risks and unknowns are explicit.

Quality gate (required)

Examples

Example 1 (timeboxing + side commitments): “I’m a product leader with wall-to-wall meetings and I advise a startup. Use personal-productivity to create a Personal Productivity System Pack with a default week timebox plan and a task capture system.” Expected: weekly timebox plan with meeting windows + focus blocks, capture/to-do spec, daily/weekly reviews, 7-day rollout.

Example 2 (dropped tasks): “I keep forgetting small but important follow-ups. Build me a write-it-down system and a daily shutdown routine.” Expected: capture system with inbox → processing → lists, a 10–15 minute daily shutdown checklist, and success metrics.

Boundary example (medical): “Diagnose my ADHD and tell me what productivity meds to take.” Response: out of scope for medical advice; recommend professional help. Offer a neutral capture/timeboxing system and ask for work constraints only.

平台分布

Codex

37.76%
按下载量换算959

Claude

29.96%
按下载量换算761

Cursor

19.13%
按下载量换算486

Gemini CLI

9.92%
按下载量换算252

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills