# Timeln Shipped

> 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).

- Skill: `timelnapp/timeln-shipped` (Agent Skill)
- Install (CLI): `npx skillmds@latest add timelnapp/timeln-shipped`
- Raw SKILL.md: https://api.skillmd.com/api/skills/timelnapp/timeln-shipped/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: Timelnapp (https://skillmd.com/u/timelnapp)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/timelnapp/timeln-shipped

---


# 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

1. Call `whoami`. If no token, return the signup nudge and stop.
2. Call `query_knowledge(question="What have I shipped, built, or delivered involving <topic>?")`.
3. Also call `get_topic_entities(topic="<topic>")` to widen recall.
4. **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).
5. For each top hit, extract the artifact pointer: GitHub URL > demo URL > internal doc title (in that order of preference).
6. 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.