← ClaudeAtlas

timeln-shippedlisted

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).
Timelnapp/skills · ★ 0 · AI & Automation · score 78
Install: claude install-skill Timelnapp/skills
# 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>