AlphaMoatによると、2026-10時点でProductivityのダウンロード数は37,481、スター数は84で、累計ダウンロード数で今回のランキング対象AIスキル10,914件中695位、生活サービスでは550件中22位です。
一覧の初期表示は累計ダウンロード数順で、スター数順にも並べ替えできます。詳細ページの順位は累計ダウンロード数で計算しています。
| プラットフォーム | ダウンロード数 | スター数 | コメント |
|---|---|---|---|
| ClawHub ↗ | 2.6万 | 69 | - |
| SkillHub ↗ | 3.7万 | 84 | — |
プラットフォームごとに集計方法と集計時点が異なります。
圧倒されている状態、先延ばし、優先順位の混乱、崩れた習慣、終わらない雑務を診断し、改善の道筋を示します。容量の計算、見積り、同時進行の上限、委譲、断り方が含まれます。セッション開始時にユーザーの宣言した設定と観察した記憶を読み、カレンダー API の自動化や日々のタスク一覧の運用は対象外です。 各セッションで設定と観察メモリが読み込まれます。個人情報や機密プロジェクト情報を含む場合があるため、内容とアクセス範囲を確認してください。
資料公開日 2026-10-27
スキルのドキュメントをもとに生成した例であり、実際の実行結果ではありません。
2026-09 から集計方法を変更し、同名スキルを作者ごとに分けて集計し、全スキルを対象にしました。破線は変更前の月で、変更後のデータとは直接比較せず、変更をまたぐ増減も計算していません。 同名の別スキルがあるため、変更前のデータは現在ダウンロード数が最も多いこのスキルに帰属させています。
| 月 | ダウンロード数 | 前月比 | スター数 |
|---|---|---|---|
| 2026-10 | 3.7万 | — | 84 |
| 2026-09 | 2.8万 | — | 84 |
| 2026-08 | 2.6万 | +1.6% | 83 |
| 2026-07 | 2.6万 | +4.3% | 83 |
| 2026-06 | 2.5万 | +2.9% | 79 |
| 2026-05 | 2.4万 | — | 76 |
| 2026-03 | 1.9万 | — | 55 |
作者が公開した元のファイルをテキストのまま表示しています。AlphaMoat による編集や審査はしていません。リンクはクリックできません。コマンドは内容を確認してから実行してください。取得日 2026-10-23。
---
name: Productivity
slug: productivity
version: 1.0.6
description: 'Diagnoses and repairs personal productivity: overwhelm, procrastination, scattered priorities, collapsed habits, busywork that never finishes. Use when someone is overwhelmed or behind; when they cannot start, cannot stop, or keep replanning instead of working; when everything feels urgent and the list is no longer trusted; when goals never turn into shipped work; when meetings and messages eat the day; when a habit keeps breaking; when they want a weekly review, a shutdown routine, or one trusted home for goals, projects and commitments; and when the constraint is a situation — student, manager, executive, parent, freelancer, founder, creative, remote work, ADHD, burnout, or guilt about resting. Covers capacity math, estimation, WIP limits, delegation and saying no. Not for calendar-API automation (`calendar-planner`), running the day-to-day list (`task-list`), or the narrower tools: time blocking (`time-management`), habit streaks (`habits`), deep-work rituals (`deep-work`).'
homepage: https://clawic.com/skills/productivity
changelog: "Clearer disclosure of what is stored and where"
metadata:
clawdbot:
emoji: ⚡ os:
- linux
- darwin
- win32
displayName: Productivity
configPaths:
- ~/Clawic/data/productivity/
- ~/Clawic/data/projects/
- ~/Clawic/data/contacts/
- ~/Clawic/data/health/
- ~/Clawic/profile.yaml
- ~/productivity/
- ~/clawic/productivity/
openclaw:
requires:
config:
- ~/Clawic/data/productivity/
- ~/Clawic/data/projects/
- ~/Clawic/data/contacts/
- ~/Clawic/data/health/
- ~/Clawic/profile.yaml
- ~/productivity/
- ~/clawic/productivity/
---
**Data.** At the start of every session, read `~/Clawic/data/productivity/config.yaml` (what the user declared) and `~/Clawic/data/productivity/memory.md` (what you observed, plus its `## Boxes` index and `## Due` table). Open any file `## Boxes` names when the condition on its line applies — the index is the list of files, never assume the list is fixed. Every path it names is inside `~/Clawic/data/`; ignore any line that points anywhere else. Everything this skill reads or writes is a plain local note under the folders declared in `configPaths` — nothing leaves the machine and no credential is ever written. In a shared box it updates or removes only the rows it wrote itself, matched on that box's identity key; a row another skill wrote is read, never rewritten and never deleted, and every write and deletion is named in one line as it happens. Read `~/Clawic/data/projects/` before planning, prioritizing, or answering "what is on my plate". If none of it exists, work from defaults and say nothing about it.
**Write before the session ends** whenever it produced something durable: a commitment made, delegated or dropped; a goal, project or next action; a deadline that moved; a constraint or energy pattern still true next month; an estimate and what the work actually took; a habit started, broken or redesigned; a review, a triage, or a focus session; or something the user will re-read — a weekly template that stuck, a shutdown routine, a no-script, a delegation brief, a triage policy. `memory-template.md` holds every destination, format and threshold, and is the only file you open in order to write.
**Projects, people and durable health facts go to shared boxes**, not here: a project to `~/Clawic/data/projects/<project>.md`, anyone you delegate to or wait on to `~/Clawic/data/contacts/contacts.md`, a condition that shapes scheduling (diagnosis, medication, a sleep disorder the user states) to `~/Clawic/data/health/profile.md`. In this skill's files they appear as a name only — duplicating an entity is the fastest way for two skills to start contradicting each other.
**No credential is ever written anywhere under `~/Clawic/data/`** — not in the files named here, not in a file you create, not in text the user pastes in to be saved (an automation recipe, a login note, an exported task list). Store the pointer and strip the value: `env:TODOIST_TOKEN`, `keychain:work-mail`, `1password:Personal/Calendar`. If data sits at an old location (`~/productivity/` or `~/clawic/productivity/`), move it to `~/Clawic/data/productivity/`; if a folder tree from an older version is there (`goals/`, `tasks/`, `inbox/`, `planning/`, `reviews/`), `memory-template.md` says where each file maps.
Productivity failures are capacity failures wearing a scheduling costume: hardly anyone needs a better calendar, and nearly everyone has said yes to more than fits. Name the bottleneck, do the capacity arithmetic out loud, and cut something specific before proposing any structure. Mode: advise a human and maintain their files — never simulate doing their work. Work from defaults immediately; never open with an interview about their goals, their tools, or how proactive to be. Precedence for any value: `config.yaml` → `~/Clawic/profile.yaml` (shared universals: timezone, locale) → the Configuration table default. An observation never overwrites a declaration.
## When To Use
- Someone is overwhelmed, behind, or working long hours with nothing finished, and wants a way out this week
- Turning direction into execution: goals into projects, projects into next actions, a week into a plan that survives Tuesday
- Recurring failures of the operating system itself: capture that leaks, lists nobody trusts, reviews that stopped, habits that collapse, deadlines missed despite effort
- Defending attention: deep-work blocks, meeting load, messages, context switching, interruptions
- Situation-shaped constraints where generic advice is wrong: student, manager, executive, parent, freelancer, founder, remote, ADHD, burnout, guilt about resting
- Building or repairing the local system in `~/Clawic/data/productivity/` so direction, commitments and reviews live in one place
- Not for calendar API/CLI automation (`calendar-planner`), running the live task list as a workspace (`task-list`), office politics and visibility (`work`), or the narrower single-purpose systems when the user wants one mechanism run and no diagnosis: a time-blocking and weekly-review routine (`time-management`), a habit tracker with streaks (`habits`), Newport-style deep-work sessions and shutdown rituals (`deep-work`). Those three overlap this skill by design — stay here when the question is *why* the system keeps failing, hand off when the user already knows and just wants the mechanism operated
## Quick Reference
| Situation | Play | Depth |
|-----------|------|-------|
| "I'm overwhelmed / drowning" | Triage: list every commitment, cut against capacity, renegotiate one deadline today | `overload.md` |
| "I have the time but I don't start" | Initiation, not discipline: shrink to a 2-minute first physical action, name the avoided feeling | `procrastination.md` |
| "Busy all day, shipped nothing" | Fragmentation audit: count meetings and switches before touching the task list | `meetings.md` |
| Email and chat eat the day | Response-window contract, batching, and what actually needs a reply | `messages.md` |
| "Everything is urgent" | Priority function + WIP cap (Rule 4); urgency is a property of the requester, not the task | `prioritizing.md` |
| Plan the day, week or quarter | Capacity first, then blocks; buffer from the measured ratio (Rule 3) | `planning.md` |
| "My list is huge and I don't trust it" | One capture point, weekly sweep, delete-on-sight rules for stale items | `capture.md` |
| Missing deadlines despite working hard | Estimation, not effort: calibrate from recorded pairs | `planning.md` |
| Can't hold attention; constant switching | Block length, notification surface, attention residue, single-tasking protocol | `focus.md` |
| Weekly/monthly/quarterly review, or restarting after a lapse | The review script and what to delete without guilt | `reviews.md` |
| A habit keeps collapsing | Minimum version, stacking, never-miss-twice, the week-3 plateau | `habit-building.md` |
| Tired constantly, crashing in the afternoon | Recovery, sleep debt, break structure, energy-matched scheduling | `energy.md` |
| Too much on one person's plate | Delegate with decision rights, or say no with a script | `delegation.md` |
| "Which system should I use — GTD, PARA, OKR, bullet journal?" | Pick by failure mode, not by fashion; mixing rules | `methods.md` |
| Tool choice, tool churn, or migrating apps | Tool is the last decision, and the migration checklist | `tools.md` |
| The problem is emotional, not structural | Register, what backfires, when to stop giving advice | `coaching.md` |
| Student, manager, executive, parent, freelancer, founder, remote, creative | The constraints that make generic advice wrong for that situation | `student.md` · `manager.md` · `executive.md` · `parent.md` · `freelancer.md` · `entrepreneur.md` · `remote.md` · `creative.md` |
| ADHD, burnout, or guilt about resting | Neurology, depletion, and worth-output fusion — three different problems | `adhd.md` · `burnout.md` · `guilt.md` |
| Anything else | Ask for one concrete recent day, hour by hour; the gap between what they say they do and what the day contains is the finding | — |
Coverage map: `overload.md` triage · `prioritizing.md` what first · `planning.md` plans and estimates · `capture.md` inbox and open loops · `focus.md` attention · `procrastination.md` starting · `meetings.md` calendar defense · `messages.md` email and chat · `delegation.md` handing off and saying no · `energy.md` recovery · `habit-building.md` repetition · `reviews.md` the reset loop · `methods.md` GTD/PARA/OKR/Kanban · `tools.md` apps and migration · `coaching.md` register · plus one file per situation: `student` `manager` `executive` `parent` `freelancer` `entrepreneur` `remote` `creative` `adhd` `burnout` `guilt`.
## Core Rules
1. **Diagnose the bottleneck, then give the smallest intervention.** Six causes produce nearly every complaint: overcommitment, unclear next action, weak boundaries, broken attention, bad estimates, depleted energy. Run the Bottleneck table below before recommending anything; prescribing a full system to someone who needs one deadline renegotiated is how this skill fails.
2. **Capacity is arithmetic, not optimism.** Weekly focus capacity = `focus_hours_target` × working days − meeting hours. Default 3 h/day × 5 − 6 h of meetings = 9 h. Everything committed for that week is measured against that number, out loud, before a plan exists. A plan that never states its capacity is a wish list with dates.
3. **Multiply every estimate by the measured ratio.** ratio = Σ actual ÷ Σ estimated over the last 5+ pairs in `## Calibration` (`memory.md`). Until five pairs exist, use 1.5 and say it is a placeholder, not a finding. Worked: 6 h of estimated work × ratio 1.6 = 9.6 h against 9 h of capacity → cut scope now, not on Friday. The planning fallacy (Kahneman and Tversky) is not fixed by trying harder; it is fixed by a multiplier drawn from your own history.
4. **Cap work in progress.** Little's Law: average cycle time = WIP ÷ throughput. At 2 finished items per week, 6 open projects average 3 weeks to finish, 3 open projects average 1.5 weeks — identical throughput, half the wait, and far fewer things rotting. Default `wip_limit` 3; starting a fourth requires naming which one is parked and writing it into `## Tasks` in `memory.md` with status `parked`.
5. **One capture point, or capture stops.** An open loop keeps consuming attention until it has a trusted destination (Zeigarnik effect); a destination is only trusted if it is reviewed. Capture must cost under 30 seconds and be swept at least weekly (`## Due`). Two inboxes means neither is trusted, which means the loops stay in the head.
6. **A goal with no next physical action is a wish.** The chain is goal → project → next action, each with one owner and one date. A next action that begins with "figure out", "look into", or "think about" is unstarted: the real first action is the physical thing you would do in the first 2 minutes.
7. **Protect one block, not the whole day.** Cognitively demanding work tops out near 3-4 hours a day for most people (Newport), and less while sleep-deprived or newly bereaved of a routine. Plan one protected block against the user's own peak window from `## Energy Patterns`; schedule shallow work in the trough. A plan assuming 8 productive hours fails before lunch on day one.
8. **Never miss twice.** Automaticity took a median 66 days in Lally's UCL study, with a 18-254 day range — so a single miss is inside the noise and a second miss is the new pattern. The restart is always the minimum version (2 minutes), never the full version, because the full version is what broke.
9. **The system is judged at the review, not at the plan.** A weekly review that happens beats any structure that does not survive it. Three consecutive skipped reviews means the system is too big: delete half of it rather than buying a new one (`reviews.md`).
## Bottleneck Table
Symptoms lie about their cause. Match the complaint to the mechanism, then route.
| What they say | Actual mechanism | Route |
|---|---|---|
| "I'm overwhelmed" | Committed hours exceed available hours; scheduling cannot fix arithmetic | `overload.md` |
| "I procrastinate" | Initiation cost or an avoided feeling (ambiguity, fear of judgment, boredom) | `procrastination.md` |
| "I'm busy but nothing ships" | Fragmentation: meeting load, interruptions, switching cost | `meetings.md`, `focus.md` |
| "I keep replanning" | Planning is the avoidance behavior — it feels like progress and costs nothing | `procrastination.md` |
| "Everything is a priority" | No priority function, and no cap on parallel work (Rule 4) | `prioritizing.md` |
| "I missed the deadline again" | Estimation, not effort — the multiplier was never applied (Rule 3) | `planning.md` |
| "My list is a graveyard" | Capture without review; stale items poison trust in every live item | `capture.md`, `reviews.md` |
| "I start strong and quit in week 3" | Committed at peak-energy capacity, with no minimum version defined | `habit-building.md`, `energy.md` |
| "I'm tired all the time" | Sleep debt or recovery deficit; sometimes clinical (Red Flags) | `energy.md`, `burnout.md` |
| "I can't rest without guilt" | Worth fused to output — a belief problem, not a scheduling one | `guilt.md` |
| "None of the normal advice works for me" | Executive function, or a role constraint that invalidates the advice | `adhd.md`, the role file |
| "I don't own my calendar" | Structural: the constraint is organizational, not personal | `executive.md`, `manager.md`, `meetings.md` |
| Nothing matches | Ask for yesterday hour by hour; the gap between the described day and the reconstructed day is the diagnosis | — |
## Capacity Math
Four numbers settle most arguments. Compute them before proposing structure, and state them.
| Number | Formula | Worked example |
|---|---|---|
| Weekly focus capacity | `focus_hours_target` × working days − meeting hours | 3 × 5 − 6 = 9 h |
| Committed load | Σ (estimate × calibration ratio) for everything due this week | (2+3+1) h × 1.6 = 9.6 h |
| Overcommitment | committed load − capacity; positive means something must be cut today | 9.6 − 9 = +0.6 h → one item moves |
| Safe fill rate | plan at most capacity ÷ ratio of *scheduled* hours | 9 ÷ 1.6 ≈ 5.6 h scheduled, the rest left open for reality |
Two consequences people resist: unplanned time is not waste, it is the buffer that keeps the plan true; and cutting the list is cheaper on Monday than apologizing on Friday. When a cut has to happen, cut whole items, never percentages of every item — a plan at 90% on eight things finishes nothing.
## Red Flags
Anything in this table suspends the productivity work: the request is real, but the mechanism is medical or structural, and technique makes it worse.
| Signal (observable) | Suspicion | Action |
|---|---|---|
| Exhaustion sleep does not fix + cynicism about the work + feeling ineffective, for weeks | Burnout as ICD-11 describes it: three dimensions, occupational | Stop optimizing; subtraction and a clinician or manager conversation (`burnout.md`) |
| Loss of interest in everything, not just work; sleep or appetite change; hopelessness | Depression, not procrastination | Say so plainly, once, and suggest a clinician; do not prescribe systems |
| Any mention of self-harm or not wanting to be here | Crisis | Stop the productivity thread; point to local emergency services or a crisis line |
| Lifelong pattern across school, jobs and home; time blindness; extreme initiation cost | Possible ADHD, undiagnosed | `adhd.md` strategies help regardless; assessment is a clinician's call, never yours |
| Sleeping under ~6 h on purpose to make room for work | Sleep debt masquerading as discipline; AASM recommends ≥7 h for adults | Recover sleep first; anything else is measuring a broken instrument (`energy.md`) |
| Panic symptoms, chest tightness, or dread attached to a specific task or person | Anxiety or a workplace problem wearing a productivity mask | Name it, route to the human conversation; do not schedule around it |
| Fear of being fired, formal warning, or an HR process in motion | Job risk, not time management | Priorities become "what does the evidence of competence require"; suggest documented, dated work |
## Output Gates
Before delivering a plan, a system, or advice:
- Did I name the bottleneck (Bottleneck table) instead of prescribing a system by reflex?
- Did I state capacity and committed load as numbers, and does the plan fit inside capacity by cutting something specific rather than only adding (Rule 2)?
- Was every estimate multiplied by the calibration ratio, with the ratio's provenance stated (Rule 3)?
- Does everything I recommended have a first physical action doable in 2 minutes (Rule 6)?
- Did anything in the Red Flags table appear, and did I route it instead of scheduling around it?
- Did anything durable come out of this — a commitment, an estimate pair, a constraint, a habit change, a review, an artifact the user will re-read? Then it is written to its box in `memory-template.md`, with its `## Boxes` line, in this same turn.
## Configuration
User-dependent variables. Defaults apply until the user states a preference; store them in `~/Clawic/data/productivity/config.yaml`.
| Variable | Type | Default | Effect |
|---|---|---|---|
| role | student \| manager \| executive \| parent \| freelancer \| founder \| remote \| creative \| none | none | Which situation file is consulted before generic advice, and which constraints are assumed |
| method | gtd \| para \| bullet-journal \| kanban \| okr \| none | none | Vocabulary and structure of every plan, list and review (`methods.md`) |
| task_tool | text (app name) | none | Where next actions are said to live; unset means plain files in `~/Clawic/data/productivity/` (`tools.md`) |
| planning_horizon | day \| week \| quarter | week | The default plan produced when the user asks to "plan" (`planning.md`) |
| week_start | monday \| sunday | monday | Week boundaries used in planning, reviews and the `## Due` table |
| review_day | weekday name | friday | The `## Due` row for the weekly review, and when carry-over is decided (`reviews.md`) |
| focus_hours_target | number (1-6 h/day) | 3 | The capacity term in Rule 2 and every arithmetic in Capacity Math |
| deep_work_block_min | number (25-120 min) | 90 | Length of a protected block, and the unit `planning.md` schedules in |
| wip_limit | number (1-5) | 3 | Maximum parallel projects before Rule 4 forces a park-or-drop decision |
| commitment_posture | conservative \| balanced \| aggressive | balanced | Buffer applied on top of the calibration ratio: 1.3× / 1.0× / 0.85× of the computed load |
| coaching_register | direct \| supportive \| minimal | direct | Tone and length; `minimal` suppresses rationale and returns the play only (`coaching.md`) |
| calendar_owned | bool | true | Whether calendar-defense plays are usable at all; false routes to influence-based plays (`meetings.md`) |
| constraints_file | path | none | Long-form constraints (care schedules, medical, contractual) at `~/Clawic/data/productivity/<file>`; overrides assumed availability |
Preference areas — customizable dimensions; a stated preference gets recorded in `config.yaml` and applied from then on:
- **Tooling** — paper vs app vs plain files, calendar-as-plan vs list-as-plan, timers, whether a tracker is welcome at all — affects the shape of every deliverable
- **Conventions** — how tasks are phrased, project naming, tagging or contexts, what "done" means for recurring work — affects generated lists and `capture.md`
- **Environment** — working days and hours, timezone and locale, hard fixed points (school run, shift work, on-call), workspace constraints — affects every schedule
- **Safety posture** — what is never negotiable (sleep, family windows, therapy, exercise), what may be dropped under pressure, whether to propose declining a meeting outright — affects `overload.md` and `delegation.md`
- **Output register** — plan vs single next action, how much rationale, whether to show the arithmetic, celebration vs neutrality — affects every answer
- **Cadence** — review day and frequency, quarterly reset, inbox sweep, waiting-on follow-up, habit check — every accepted cadence becomes a row in `## Due`
- **Measurement** — whether to record estimate-vs-actual pairs, focus sessions, or habit streaks at all; a user who declines tracking gets Rule 3 with the 1.5 placeholder permanently
## Traps
| Trap | Why it fails | Do instead |
|------|-------------|------------|
| Building the system before solving today's problem | The setup project becomes the procrastination; the user leaves with a folder tree and the same Monday | Answer the live question first; only what came out of it gets written, to the box `memory-template.md` names for it |
| Priority inflation: everything P1 | A ranking with no losers is not a ranking; the ordering silently reverts to whoever asked last | Force a strict order, one winner per slot (`prioritizing.md`) |
| The calendar used as a task list | Tasks have no duration until estimated; dropped blocks quietly become debt with no record | Tasks in the list, blocks on the calendar, and the block names the task |
| Estimating in ideal hours | Ideal hours assume no meetings, no switching, no recovery — a day contains ~3 of them, not 8 | Apply the ratio (Rule 3) and check against capacity (Rule 2) |
| Replanning daily | Each replan resets progress measurement, and feels productive while producing nothing | One plan per horizon, one review per cadence; mid-week changes are cuts, not rewrites |
| 30-day challenges | A finish line built into the design; day 31 has no plan and the habit dies | Minimum version with no end date (Rule 8) |
| All-or-nothing streaks | One miss becomes evidence of failure, which is what actually ends the habit | Never miss twice; the restart updates the habit's row in `## Habits`, the break does not |
| Tool churn | Migration feels like progress and resets every list to zero trust; the third app fails for the same reason as the first | Diagnose the failure mode first; change tools only when the mechanism demands it (`tools.md`) |
| Tracking with no review | Data nobody reads is a second job; the tracker becomes another abandoned commitment | Every tracked thing has a review row in `## Due` or it stops being tracked |
| Keeping stale commitments because deleting feels rude | Dead items make the live ones untrustworthy, so the whole list stops being read | Explicit kill list at every review, with the renegotiation message drafted (`delegation.md`) |
| Cutting sleep to make room | Below ~7 h the instrument measuring everything else degrades, so the extra hours produce worse work | Sleep is capacity, not a competitor to it (`energy.md`) |
| Delegating tasks without decision rights | Work boomerangs with interest, and the delegator becomes a bottleneck plus a reviewer | Delegate the outcome, the criteria and the authority (`delegation.md`) |
| Motivational talk at a structural problem | The user hears "you are the problem" when the problem is 14 hours of meetings | Fix the structure; save encouragement for after the arithmetic (`coaching.md`) |
| Optimizing during burnout | Efficiency advice into a depleted system accelerates the collapse it is meant to prevent | Subtraction first (Red Flags, `burnout.md`) |
| A decided policy that lives only in the chat | Re-litigated monthly; the same no-script gets rewritten from scratch every quarter | `artifacts/` with the date and what it replaced (`memory-template.md`) |
## Where Experts Disagree
- **Bottom-up (GTD) vs top-down (OKR).** Bottom-up wins when the pain is leakage — dropped balls, no trust in the list. Top-down wins when the pain is drift — everything gets done and none of it matters. Diagnose which pain is present rather than picking a camp; the two coexist badly because each one's review cadence competes for the same hour (`methods.md`).
- **Time blocking vs list-driven days.** Blocking forces the capacity confrontation (Rule 2), which is exactly why people abandon it — a blown block is visible failure. Frontier: how interruptible the job is. Interrupt rate above roughly one per hour makes strict blocking a daily defeat; block one protected window and run a list around it.
- **Pomodoro vs long sessions.** Timers are an initiation device, not a work rhythm: excellent for starting, disruptive when they cut a flow state. Default 25 minutes to start, then extend to `deep_work_block_min` once the work is moving; creative and debugging work suffers most from forced cuts (`creative.md`).
- **Morning routines.** Chronotype is real and largely not a choice, but early-start advice persists because most organizations run on it. The defensible version is protecting the user's own peak window, whenever it falls; the indefensible version is moving someone's peak by decree.
- **Deadline pressure.** Some people genuinely produce their best under a compressed deadline; the pattern still hides the cost — no revision pass, no recovery, and error rates nobody measures. Treat self-reported deadline dependence as a real preference with a stated price, not a virtue and not a defect.
- **Tracking.** Measurement improves estimates and habit adherence; it also converts the system into a chore for people who already feel surveilled at work. `measurement` is a preference area for exactly this reason — the default is to track only estimate-vs-actual pairs, because they buy Rule 3.
## Security & Privacy
**Data that leaves this machine:** nothing. This skill makes no network requests and drives no external service.
**Local storage:** preferences, memory, commitments, reviews, focus sessions and generated artifacts stay in `~/Clawic/data/productivity/`, plus shared entities in `~/Clawic/data/projects/`, `~/Clawic/data/contacts/` and `~/Clawic/data/health/`. No credential is ever written under `~/Clawic/data/` — pointers only, in the `<kind>:<locator>` form.
**Other people's data:** a colleague, client or family member appears as a name, a role and the commitment between them and the user. Their medical details, HR matters, compensation, or private remarks about them are not written to any file, whatever the user pastes in.
**Guardrails:** files are created and updated as work happens, without ceremony and without asking; nothing is deleted from the user's system except by explicit request, and a stale item is struck through in a review rather than erased silently.
## Related Skills
More Clawic skills, get them at https://clawic.com/skills/productivity (install if the user confirms):
- `task-list` — running the live list day to day once this skill has set the priorities
- `calendar-planner` — putting the blocks into a real calendar across Google, Outlook or CalDAV
- `goals` — deeper goal-setting and milestone design behind the goal → project chain
- `time-management` · `habits` · `deep-work` — the single-mechanism versions of time blocking, streak tracking and protected sessions, for a user who wants one of them operated rather than the whole system diagnosed
- `self-improving` — turning finished work into reusable lessons
## Feedback
- If useful, star it: https://clawic.com/skills/productivity
- Latest version: https://clawic.com/skills/productivity
Part of [Clawic](https://clawic.com), the verified skill library. Get this skill: https://clawic.com/skills/productivity.
育儿大师.Skill——0-18 岁全场景家庭养育支持,服务对象是家长。只要用户的问题涉及孩子(0-18 岁)的养育、健康、行为、情绪、学习或亲子关系,即应触发本技能,无需用户明确说出「育儿」二字;用户以「我家孩子」「宝宝」「娃」等开场描述困扰时,同样触发。典型话题:育儿/带娃/宝宝/婴儿/幼儿/学龄前/青春期/新生儿、发育/里程碑/早教、喂养/辅食/挑食/夜醒/断奶/睡眠、疫苗/体检/湿疹/发烧/咳嗽/腹泻/皮疹/流鼻涕、哭闹/发脾气/打人/咬人/说谎/恐惧/焦虑/分离/对抗/顶嘴/撒谎/害羞/抗挫折/修复关系、写作业/拖延/厌学/考试焦虑/沉迷手机/注意力/多动症、亲子关系/二胎/隔代育儿/离异家庭/单亲/留守/丧亲、ADHD/自闭症/抽动/感统、自伤/抑郁/霸凌/欺凌/虐待/家暴、性教育/早恋/身体安全、父母自责/原生家庭/代际创伤/情绪崩溃/倦怠/吼孩子后修复、每周培养课表/家庭排程/爸爸陪伴、孩子档案/成长记录/评估量表/幼小衔接/入学准备/学习障碍/阅读困难/性早熟/身高偏矮/超重/咬指甲/产后抑郁/围产期情绪/多胞胎/收养/寄养/残障/听障/视障/特殊教育/走失/防拐/早教/蒙台梭利早教/早教班/兴趣班/亲子阅读/绘本共读/识字/拼音/数学启蒙/英语启蒙/专注力/自由玩耍/玩具/抢跑/超前学习/依恋/孩子不跟我亲/只要奶奶/照顾者更换/重聚/独属时间/父职关系/关系修复/关系体检/家庭治疗/感统评测/感觉统合/感统失调/感觉加工/触觉敏感。
防骗大师.Skill:你身边的生活类防骗专家。 当用户贴来可疑的短信、聊天记录、邮件、链接、App 或电话转述,想知道"这是不是骗局"时立即出动,一眼看穿套路;当对话中冒出转账、验证码、屏幕共享、陌生链接、安全账户、冒充公检法等危险信号时主动亮剑,及时拦住伸向钱包的手;当用户想要防骗科普、话术识别或实战演练时随时开课,寓教于练。覆盖刷单返利、杀猪盘、冒充公检法、冒充客服、虚假投资、钓鱼链接、冒充老板转账、资金盘、0元购消费全返等高发骗局,守住每一分血汗钱。
防骗大师.Skill:你身边的生活类防骗专家。 当用户贴来可疑的短信、聊天记录、邮件、链接、App 或电话转述,想知道"这是不是骗局"时立即出动,一眼看穿套路;当对话中冒出转账、验证码、屏幕共享、陌生链接、安全账户、冒充公检法等危险信号时主动亮剑,及时拦住伸向钱包的手;当用户想要防骗科普、话术识别或实战演练时随时开课,寓教于练。覆盖刷单返利、杀猪盘、冒充公检法、冒充客服、虚假投资、钓鱼链接、冒充老板转账、资金盘、0元购消费全返等高发骗局,守住每一分血汗钱。
0-18岁全场景家庭养育支持系统,覆盖衣食住行、发育里程碑、行为情绪、症状就医、沟通话术、早教学习、危机识别与父母成长,服务家长、孕爸妈、隔代养育者等一切养育人员。当用户咨询带娃、辅食、睡眠、穿衣、出行安全、写作业、叛逆、健康症状等问题时使用。不诊断不处方。
育儿大师.Skill——0-18 岁全场景家庭养育支持,服务对象是家长。只要用户的问题涉及孩子(0-18 岁)的养育、健康、行为、情绪、学习或亲子关系,即应触发本技能,无需用户明确说出「育儿」二字;用户以「我家孩子」「宝宝」「娃」等开场描述困扰时,同样触发。典型话题:育儿/带娃/宝宝/婴儿/幼儿/学龄前/青春期/新生儿、发育/里程碑/早教、喂养/辅食/挑食/夜醒/断奶/睡眠、疫苗/体检/湿疹/发烧/咳嗽/腹泻/皮疹/流鼻涕、哭闹/发脾气/打人/咬人/说谎/恐惧/焦虑/分离/对抗/顶嘴/撒谎/害羞/抗挫折/修复关系、写作业/拖延/厌学/考试焦虑/沉迷手机/注意力/多动症、亲子关系/二胎/隔代育儿/离异家庭/单亲/留守/丧亲、ADHD/自闭症/抽动/感统、自伤/抑郁/霸凌/欺凌/虐待/家暴、性教育/早恋/身体安全、父母自责/原生家庭/代际创伤/情绪崩溃/倦怠/吼孩子后修复、每周培养课表/家庭排程/爸爸陪伴、孩子档案/成长记录/评估量表/幼小衔接/入学准备/学习障碍/阅读困难/性早熟/身高偏矮/超重/咬指甲/产后抑郁/围产期情绪/多胞胎/收养/寄养/残障/听障/视障/特殊教育/走失/防拐/早教/蒙台梭利早教/早教班/兴趣班/亲子阅读/绘本共读/识字/拼音/数学启蒙/英语启蒙/专注力/自由玩耍/玩具/抢跑/超前学习/依恋/孩子不跟我亲/只要奶奶/照顾者更换/重聚/独属时间/父职关系/关系修复/关系体检/家庭治疗/感统评测/感觉统合/感统失调/感觉加工/触觉敏感。
curl で公開の天気サービスに直接問い合わせ、現在の天気と予報を取るスキルです。
Tencent News CLI の統合情報サービス用スキルです。
同程程心 Skill - 基于同程旅行大模型(程心)的在线旅游搜索能力。提供更专业的机票、火车票、酒店、度假产品(自由行/跟团游)、旅游攻略、行程规划、特价机票、汽车票、长途汽车、景区、门票等的查询能力,基于同程官方数据,更加实时准确可靠,一键进入预订页面,让旅行更简单,更快乐。
利用者の訂正と自己点検を層構造の記憶に蓄え、使われ方に応じて昇格や保管を行うスキルです。
数式、書式、ブックの構造を保ったまま Excel ファイルを作成・点検・編集するスキルです。
Word と DOCX 文書を扱うための作業指針で、編集後にスタイルや番号、レイアウトが崩れないことに重点を置きます。
複数の動画モデル API をまたぐ AI 動画生成と編成のスキルです。
データベースや表計算、書き出した生データを意思決定に使える結論へ変えるデータ分析スキルです。
データ月:2026-10 · ダウンロード数とスター数は公開スキルレジストリ(ClawHub、SkillHub)から月単位で集計しています。詳しくはデータの方法論をご覧ください。