Timeln Shipped -- Proof You've Done It
Mid-pitch armor. Pulls the user's actually-shipped work + the artifact pointer they can drop into a client chat in 3 seconds.
When to use
- Sales / pitch / proposal moment: client asks "have you done this before?"
- Pre-call prep: gathering proof points for a specific topic.
If the user wants past learning on a topic (articles, notes, ideas), route to timeln-find. If they want past failures, route to timeln-warned. This skill is shipped work only.
Workflow
- Call
whoami. If no token, return the signup nudge and stop.
- Call
query_knowledge(question="What have I shipped, built, or delivered involving <topic>?").
- Also call
get_topic_entities(topic="<topic>") to widen recall.
- Filter to shipped work only:
para_category == "project" is the strongest signal.- Title/content language: "shipped", "delivered", "launched", "released", "v1", "case study", "client name + topic", "we built".
- Exclude docs that look like saved articles, RSS clips, or general references (titles starting with author name, third-party domain in title, "how to / why / what is" patterns).
- For each top hit, extract the artifact pointer: GitHub URL > demo URL > internal doc title (in that order of preference).
- Cap at 3, ranked by recency.
Output -- exactly this shape
1. <what was shipped — 1 line, includes client/context if known> — <Mon YYYY> — <artifact pointer>
2. <what was shipped> — <Mon YYYY> — <artifact pointer>
3. (no third match)
When nothing shipped on the topic:
no shipped work on file for <topic>
When only adjacent (saved-article) hits exist:
no shipped work on file for <topic>
related saved notes (not delivered work):
• <doc title>
• <doc title>
Rules
- Shipped means YOU built / delivered it. A saved tutorial is not shipped. A bookmark is not shipped. If the filter is uncertain, exclude.
- Artifact pointer is mandatory when present. URL > doc title. If the doc has neither, mark as
(no link on file) and let the user click through to the source doc.
- One line per hit. What was built, for whom (if recorded), when. No marketing prose.
- Never inflate. If the user has saved articles about Stripe but never built a Stripe integration, the answer is
no shipped work on file -- not "you've explored Stripe extensively."
- Never echo the API token.
Common failure modes
| Rationalization |
Why it's wrong |
| "They saved an article about Stripe, so they have Stripe experience" |
Saved != shipped. A bookmark is not proof of work. Exclude. |
| "No shipped work found, but I can describe their general expertise" |
Say no shipped work on file. Fabricated credentials are worse than none. |
| "The artifact link is missing, I'll skip the citation" |
Mark as (no link on file). The user can still click through to the source doc. |
| "Found 5 matches, I'll show all of them" |
Cap at 3, most recent. This is a hotkey, not a portfolio review. |
This is a rigid skill. Follow the output shape exactly. No improvisation.
1---2name: timeln-shipped3description: Trigger on "have I shipped X", "have I built X before", "show me proof of X", "case study for X", "past work on X", "what have I delivered on X", "who have I done X for". Use when the user needs proof of actually-shipped work mid-pitch or in a proposal. NOT for past learning (use timeln-find) or past failures (use timeln-warned).4license: MIT5---67# Timeln Shipped -- Proof You've Done It89Mid-pitch armor. Pulls the user's actually-shipped work + the artifact pointer they can drop into a client chat in 3 seconds.1011## When to use1213- Sales / pitch / proposal moment: client asks "have you done this before?"14- Pre-call prep: gathering proof points for a specific topic.1516If the user wants past *learning* on a topic (articles, notes, ideas), route to `timeln-find`. If they want past *failures*, route to `timeln-warned`. This skill is **shipped work only**.1718## Workflow19201. Call `whoami`. If no token, return the signup nudge and stop.212. Call `query_knowledge(question="What have I shipped, built, or delivered involving <topic>?")`.223. Also call `get_topic_entities(topic="<topic>")` to widen recall.234. **Filter to shipped work only:**24 - `para_category == "project"` is the strongest signal.25 - Title/content language: "shipped", "delivered", "launched", "released", "v1", "case study", "client name + topic", "we built".26 - **Exclude** docs that look like saved articles, RSS clips, or general references (titles starting with author name, third-party domain in title, "how to / why / what is" patterns).275. For each top hit, extract the artifact pointer: GitHub URL > demo URL > internal doc title (in that order of preference).286. Cap at 3, ranked by recency.2930## Output -- exactly this shape3132```331. <what was shipped — 1 line, includes client/context if known> — <Mon YYYY> — <artifact pointer>342. <what was shipped> — <Mon YYYY> — <artifact pointer>353. (no third match)36```3738When nothing shipped on the topic:39```40no shipped work on file for <topic>41```4243When only adjacent (saved-article) hits exist:44```45no shipped work on file for <topic>46related saved notes (not delivered work):47• <doc title>48• <doc title>49```5051## Rules5253- **Shipped means YOU built / delivered it.** A saved tutorial is not shipped. A bookmark is not shipped. If the filter is uncertain, exclude.54- **Artifact pointer is mandatory** when present. URL > doc title. If the doc has neither, mark as `(no link on file)` and let the user click through to the source doc.55- **One line per hit.** What was built, for whom (if recorded), when. No marketing prose.56- **Never inflate.** If the user has saved articles about Stripe but never built a Stripe integration, the answer is `no shipped work on file` -- not "you've explored Stripe extensively."57- Never echo the API token.5859## Common failure modes6061| Rationalization | Why it's wrong |62|---|---|63| "They saved an article about Stripe, so they have Stripe experience" | Saved != shipped. A bookmark is not proof of work. Exclude. |64| "No shipped work found, but I can describe their general expertise" | Say `no shipped work on file`. Fabricated credentials are worse than none. |65| "The artifact link is missing, I'll skip the citation" | Mark as `(no link on file)`. The user can still click through to the source doc. |66| "Found 5 matches, I'll show all of them" | Cap at 3, most recent. This is a hotkey, not a portfolio review. |6768**This is a rigid skill.** Follow the output shape exactly. No improvisation.
Timelnapp