AC time-capsule
Create, manage, and open time capsules — seal a thought, feeling, decision, or wish and have it delivered back to your future self with AI reflection on what changed. Use when: user wants to seal/capsule/bury a message for their future self, write a letter to future me, record a moment to revisit later, open a time capsule that has arrived, list or manage existing capsules. Trigger phrases: "time capsule", "seal this", "letter to future me", "bury this thought", "时间胶囊", "时光瓶", "封存", "给未来的自己", "写给N年后的我", "open my capsules", "我的胶囊", "时光胶囊". NOT for: simple reminders or alarms (use cron/reminders), daily journaling (use memory), saving passwords or secrets (use secure storage).
As a process C 62/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 62/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (time-capsule) differs from the folder (timebottle)
- 50When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 56 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Execution cost. Instruction body is 1624 tokens
- 100Running it twice. Mutating operations check current state
- 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
- +3Output format is not stated: the model decides each time
- -221 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 683: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 56 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.