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

attention-reset

Get your attention back with a 30-day protocol that assumes you'll break it — a screen-time ledger without moralizing, friction engineering (what to delete, grayscale, where the phone sleeps), planned relapses, and honest replacement activities for the boredom that shows up on day 3. Use when someone says 'my screen time is 7 hours', 'I want a dumbphone', 'digital detox', 'I can't read books anymore', or 'my attention span is gone'. Produces the ledger, a personal friction plan, and the 30-day protocol with expected failure points.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md6.8 KB

SKILL.md(原文)

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

Attention Reset Skill

Attention didn't get weak — it got outbid. Apps engineered by thousands of people compete for it against your unread book, and the book was never going to win on willpower. So this protocol doesn't use willpower: it uses friction — making the scroll slightly harder and the alternative slightly easier — plus honest accounting, planned relapses (day 3 and day 12 are coming; a plan that pretends otherwise is a plan for shame), and the missing piece in every detox thread: you can't delete a habit, only replace it, so the replacement gets designed with the same care as the deletions. Bennett wrote the original time audit in 1908; this is the sequel his readers didn't need yet — [[bennett-time-audit]] assumed your evening was empty; your phone disagrees.

What This Skill Produces

  • An attention ledger: where the hours actually go (from their screen- time stats), split by chosen vs captured time — the distinction that replaces moralizing
  • A personal friction plan: the delete/keep/cripple list for their actual apps, plus environmental moves (grayscale, where the phone sleeps, the launcher diet)
  • The 30-day protocol: week-by-week, with expected failure points pre-written and re-entry rules for after a relapse
  • A replacement menu: what fills the specific moments the phone currently owns (the queue, the toilet, the 11pm bed scroll), matched to what they actually miss doing

Required Inputs

Ask for (if not already provided):

  • The screen-time screenshot or numbers: total, top 5 apps, pickups — today's truth, no editorializing
  • The moments it happens: first-thing? queues? work escapes? the bed spiral? (the when determines the friction plan more than the what)
  • What they miss being able to do (read? sit through a film? be bored?) — this becomes the replacement menu, and the motivation anchor
  • Constraints: apps genuinely needed for work/family, past attempts and how they died

Framework

  1. Ledger without judgment. Sort the hours: CHOSEN (the show you meant to watch, the chat with your sister) vs CAPTURED (the 40-minute scroll you don't remember starting). The target is captured time only — this protocol defends chosen pleasures explicitly, or it becomes puritanism and dies by day 5.
  2. Engineer friction, not resolve. Per app: DELETE (captured-only apps — the feed apps; the account survives, the pocket access doesn't) · CRIPPLE (needed apps made boring: log-out-after-use, no notifications, moved off home screen, web-only) · KEEP (tools and chosen media, left alone). Environment: phone charges outside the bedroom (buy the £10 alarm clock — this one change carries half the protocol) · grayscale · home screen reduced to tools · one no-phone anchor block daily.
  3. Design the replacements before the void opens. For each captured moment, a specific fitted replacement with lower activation energy than the scroll: the book already open on the nightstand, the podcast queued, the actual boredom (rehabilitating boredom is the end-boss and worth naming as a goal). Vague "read more" loses to a feed every time; the pre-opened book sometimes wins.
  4. The 30 days, with failure built in. Week 1: ledger + environment moves only (no usage targets yet — change the terrain first). Week 2: deletions + replacements live; expect day 2–4 to be irritable and say so in advance. Week 3: the relapse window — the rule is written now: a relapse ends at the next sleep, not the next Monday; no streak resets, streaks are the enemy of restarts. Week 4: re-add ONE deleted thing deliberately if wanted, on the crippled tier — the goal is a phone that serves, not a monastery.
  5. Measure what matters. Success metrics: captured hours ↓, the missed-thing returning (pages read, films finished), pickup count ↓. NOT total screen time — a 3-hour chosen movie is a win, and metrics that can't tell wins from losses train the wrong thing.

Output Format

## Your attention ledger
| Where hours go | h/day | Chosen or captured? |
Captured total: X h/day — that's the whole target. Chosen stays.

## Friction plan
DELETE: … · CRIPPLE (how, per app): … · KEEP: …
Environment: [bedroom charge · grayscale · home screen · anchor block]

## Replacement menu (moment → fitted swap)
| The moment | What fills it (activation energy ≤ the scroll) |

## The 30 days
[Week-by-week · day 2-4 irritability forecast · the relapse rule verbatim ·
week-4 deliberate re-add]

## What we count
[Captured ↓ · the missed-thing returning · pickups ↓ — not total time]

Quality Checks

  • The ledger preserves chosen time explicitly — the protocol never touches the things the user actually loves
  • Every deleted app's moment has a fitted replacement with named lower activation energy
  • The relapse rule appears verbatim and no streak language survives anywhere in the output
  • The bedroom-charging move and its £10 alarm clock appear unless genuinely impossible
  • Metrics can distinguish a chosen movie night from a captured scroll — total screen time is never the headline number

Anti-Patterns

  • Do not moralize — "you spent 47 hours on TikTok" is data, not a character reading; shame relapses users faster than any app
  • Do not prescribe the monastery — plans that ban chosen pleasures die by day 5 and take the user's confidence with them
  • Do not rely on willpower anywhere a design change exists
  • Do not medicalize — persistent compulsion that resists structural change, or scrolling that's masking something heavier, gets the honest "this might need a human" line, not a sterner protocol
  • Do not promise a rewired brain in 30 days — the honest pitch is captured hours returned and the first finished book

Related

[[bennett-time-audit]] for what to do with the reclaimed evening; [[deep-work-blocking]] for the work-hours version; [[weekly-review-ritual]] as the protocol's maintenance home after day 30.

Example Trigger Phrases

  • "My screen time is 7 hours."
  • "I want a dumbphone."
  • "I can't read books anymore."
  • "My attention span is gone."

レビュー

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

同じリポジトリのスキル

概要と使いどころ

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

mohitagw15856 のスキルをすべて見る

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