BB the-subtle-art-of-not-giving-a-fck
Mark Manson's "The Subtle Art of Not Giving a Fck" — an executable toolkit for choosing what to care about, embracing discomfort, and living a values-driven life. Covers 5 use cases: ① Values Clarification — ("How to know what really matters" "How to stop caring about the wrong things") ② Embracing Discomfort — ("How to deal with pain" "How to get comfortable with being uncomfortable") ③ Overcoming Entitlement — ("How to stop feeling special" "How to accept that life is hard") ④ Building Better Habits — ("How to stop avoiding problems" "How to develop good values") ⑤ Dealing with Failure — ("How to handle rejection" "How to learn from failure instead of fearing it") Trigger when users say: "The Subtle Art of Not Giving a Fck" "Mark Manson" "Not giving a fck" "Stop caring what others think" "How to be happy" "How to stop being entitled" "Embrace discomfort" "Choose better values" or mention: Mark Manson / fck / entitlement / values / happiness / problems / suffering / feedback loop from hell / you are not special / subtlety.
Mark Manson's "The Subtle Art of Not Giving a Fck" — an executable toolkit for choosing what to care about, embracing discomfort, and living a values-driven…
As a process B 68/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- Shorten the description to 1024 characters.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1039 chars, limit 1024
Process rating: all ten parameters 68/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 32 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2234 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1039: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 19 example trigger phrases
- +4Structure: 10 headings
- +3Step-by-step instructions: 32 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.