@opendirectory.dev/skills 0.1.44 → 0.1.46

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@opendirectory.dev/skills",
-  "version": "0.1.44",
+  "version": "0.1.46",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
   "bin": {

package/registry.json

@@ -196,6 +196,14 @@
     "version": "1.0.0",
     "path": "skills/newsletter-digest"
   },
+  {
+    "name": "noise-to-linkedin-carousel",
+    "description": "Transforms messy, unstructured source material (transcripts, rough notes, etc.",
+    "tags": [],
+    "author": "ajaycodesitbetter",
+    "version": "1.0.0",
+    "path": "skills/noise-to-linkedin-carousel"
+  },
   {
     "name": "noise2blog",
     "description": "Turns rough notes, bullet points, voice transcripts, or tweet dumps into a polished, publication-ready blog post.",
@@ -217,6 +225,14 @@
     "version": "0.0.1",
     "path": "skills/npm-downloads-to-leads"
   },
+  {
+    "name": "oss-launch-kit",
+    "description": "Higher-level OSS launch orchestrator that analyzes repos, selects channels, and coordinates launch plans.",
+    "tags": [],
+    "author": "OpenDirectory",
+    "version": "0.2.0",
+    "path": "skills/oss-launch-kit"
+  },
   {
     "name": "outreach-sequence-builder",
     "description": "Takes a buying signal and generates a personalized multi-channel outreach sequence across email, LinkedIn, and phone.",

package/skills/noise-to-linkedin-carousel/README.md

@@ -0,0 +1,81 @@
+![noise-to-linkedin-carousel](./cover.png)
+
+# noise-to-linkedin-carousel
+
+**noise-to-linkedin-carousel** turns rough notes, transcripts, and idea dumps into a LinkedIn-ready carousel content pack with a strong hook, clear slide-by-slide structure, and a CTA — built for founders, GTM teams, and technical marketers who think faster than they write.
+
+## Why This Skill?
+
+Founders and technical operators often think in fragments: voice notes, bullet dumps, rambling transcripts, or Slack thoughts. They have valuable insights but lack a repeatable workflow to convert those noisy inputs into highly readable, LinkedIn-native carousel content.
+
+LinkedIn carousels routinely outperform single-image or text-only posts because they encourage swipe-through engagement and let you teach in a structured, visual way. While `linkedin-post-generator` focuses on crafting a single post, **noise-to-linkedin-carousel** is designed specifically to turn messy raw thinking into a multi-slide narrative that a founder, GTM engineer, or designer can immediately turn into a carousel asset.
+
+This agent skill helps by taking that unstructured "noise" and transforming it into a structured asset pack containing:
+- 3 strong cover hook options
+- 5-9 correctly sized insight slides (one idea per slide)
+- A clear narrative progression
+- A custom CTA slide
+- A supporting LinkedIn caption
+
+## Prerequisites
+
+- [OpenDirectory CLI](https://github.com/Varnan-Tech/opendirectory)
+- An OpenDirectory-compatible agent (e.g., **Anti-Gravity** or **OpenCode**)
+
+## Installation
+
+Install directly into your agent via OpenDirectory:
+```bash
+npx "@opendirectory.dev/skills" install noise-to-linkedin-carousel --target anti-gravity
+```
+*(Replace `anti-gravity` with your preferred agent target.)*
+
+## Usage Examples
+
+Once installed, you can simply message your agent with noisy source material. 
+
+**Example Prompt:**
+> I recorded this rough voice note about why most devtools marketing fails. It’s a rant, not a clean outline. Here’s the transcript — turn this into a LinkedIn carousel I can hand to my designer:  
+>  
+> “okay so basically what i realized is that most devtools fail because they market features not use cases like everyone lists api endpoints and configs but nobody explains when you’d actually use this thing in production you know what i mean and founders think more features will solve it but the buyer just wants to know what problem disappears after they install you and how fast they get there”
+
+**Sample Output Shape:**
+
+- **Thesis:**  
+  Most devtools fail because they market features instead of clear, real-world use cases.
+
+- **Hooks (3 options):**  
+  1. “90% of devtools die because they market features, not outcomes.”  
+  2. “Your devtool doesn’t have a feature problem. It has a use-case problem.”  
+  3. “If your devtool landing page looks like an API manual, this is for you.”
+
+- **Slide Breakdown (example):**  
+  - **Slide 1 – Cover (Hook):** One of the hooks above.  
+  - **Slide 2 – Problem:** What most devtools marketing looks like today.  
+  - **Slide 3 – Insight:** Buyers buy outcomes and solved problems, not endpoints.  
+  - **Slide 4 – Insight:** Why “more features” doesn’t fix the positioning gap.  
+  - **Slide 5 – Example:** Before/after example of reframing features as use cases.  
+  - **Slide 6 – Framework:** Simple checklist to rewrite your own devtool pitch.  
+  - **Slide 7 – CTA:** Ask readers to audit their landing page or share with a founder.
+
+- **Caption:**  
+  A LinkedIn-ready caption that tees up the carousel, adds 1–2 sentences of context, and ends with a natural CTA (e.g., “Reply ‘DEVS’ if you want a teardown of your current page”), plus 2–4 relevant hashtags.
+
+## Under the Hood
+
+Unlike simple text generators, this skill operates as a structured workflow:
+1. **Thesis Extraction** - It strips away the noise to find the actual point.
+2. **Hook Selection** - It maps the thesis to known high-performing LinkedIn hook patterns.
+3. **Slide Constraint Enforcement** – It forces one main idea per slide and short, punchy copy so the deck feels like a high-signal LinkedIn carousel, not a pasted blog post.
+
+## File Architecture
+
+- `SKILL.md` - Core workflow instructions and formatting constraints.
+- `references/output-format.md` - The deterministic output schema.
+- `references/hook-patterns.md` - High-performing hook structures.
+- `references/slide-types.md` - Rules for cover, context, insight, and CTA slides.
+- `references/quality-checklist.md` - GTM-aligned checks run before returning output.
+
+## Contributing
+
+Pull requests to refine hook patterns, add new slide structures, or include helper scripts that refine raw transcripts are welcome.

package/skills/noise-to-linkedin-carousel/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: noise-to-linkedin-carousel
+description: Transforms messy, unstructured source material (transcripts, rough notes, etc.) into a polished, structured LinkedIn carousel content pack for founders and GTM teams.
+author: ajaycodesitbetter
+version: 1.0.0
+---
+
+# noise-to-linkedin-carousel
+
+You are an expert ghostwriter, technical marketer, and content strategist specializing in LinkedIn distribution. Your task is to take noisy source material and transform it into a structured, highly valuable LinkedIn carousel content pack.
+
+## Input Considerations
+The user will provide source material which may be:
+- Raw voice note transcripts
+- Bulleted brain dumps
+- Launch notes or Slack thoughts
+- Article or blog excerpts
+
+## Core Workflow
+
+You must follow these steps precisely to fulfill the user's request:
+
+### Step 1: Analyze and Extract Formulation
+Read the noisy input. Before drafting any content:
+1. Extract the strongest Distilled Thesis.
+2. Determine the Audience Angle.
+3. Identify the Content Goal (educate, provoke, summarize, convert, or inspire).
+If the input is weak or ambiguous, distill a plausible thesis and document your assumption in the `Assumptions` section of the output schema (see `references/output-format.md`). Omit that section if no assumptions are needed.
+
+### Step 2: Establish the Structure
+Determine the optimal length (5-9 slides). Map out a narrative arc determining which Slide Role each slide will play (Cover, Problem, Reframe, Insight, Framework, Example, Proof, Takeaway, CTA).
+*Refer to `references/slide-types.md` for understanding the exact nature and execution rules of these slide roles.*
+
+### Step 3: Generate Hooks
+Draft 3 distinct cover hook options explicitly labeled with the pattern used.
+*Refer to `references/hook-patterns.md` for the formulas needed.*
+
+### Step 4: Draft the Slide-by-Slide Content
+Create the content. You must adhere strictly to the quality constraints:
+- One main idea per slide.
+- Short, punchy copy. Absolutely no large paragraphs.
+- Provide a visual direction/intent for each slide indicating how a designer should construct it.
+*Review `references/quality-checklist.md` during drafting and perform a strict rubric check to ensure high standards.*
+
+### Step 5: Final Output Generation
+Format the final response strictly and deterministically according to the schema provided in `references/output-format.md`.
+
+## Tone and Style Constraints
+- Clear, sharp, and founder-friendly.
+- Educational, credible, and practical.
+- AVOID: Vague motivational fluff, heavy jargon without context, or cliché "growth-hacking" tones.
+
+Return ONLY the structured markdown response expected by the output schema.

package/skills/noise-to-linkedin-carousel/references/hook-patterns.md

@@ -0,0 +1,45 @@
+# Hook Patterns
+
+A strong hook on Slide 1 is critical for LinkedIn carousels. Expand beyond generic statements and use these specific patterns when generating the "Hook Options":
+
+## 1. The Contrarian Hook
+- **What it does:** Goes against common industry advice or accepted "best practices."
+- **When to use it:** When the source material debunks a myth or introduces a paradigm shift.
+- **Examples:**
+  - "Stop prioritizing features. Here is why the best product teams ship less."
+  - "The 'best' marketing channels are dead. Do this instead."
+
+## 2. The Mistake Hook
+- **What it does:** Agitates a specific pain point or error the audience is currently making.
+- **When to use it:** When the carousel acts as a corrective guide.
+- **Examples:**
+  - "90% of GTM engineers make this one mistake when launching Open Source tools."
+  - "Your devtool doesn't have a feature problem. It has a use-case problem."
+
+## 3. The Operator Lesson Hook
+- **What it does:** Shares a hard-won, tactical lesson from the trenches.
+- **When to use it:** When the source material shares personal, company, or team learnings.
+- **Examples:**
+  - "We spent 6 months building the wrong API. Here are the 5 red flags we missed."
+  - "How we scaled our technical documentation to 10k readers with 0 budget."
+
+## 4. The Framework Hook
+- **What it does:** Promises a clear, structured, step-by-step path to success.
+- **When to use it:** When the input provides a highly structured methodology to follow.
+- **Examples:**
+  - "The 4-step framework we use to write product docs that developers actually read."
+  - "A simple, repeatable system to onboard enterprise users in 5 days."
+
+## 5. The Teardown Hook
+- **What it does:** Analyzes a recognizable success or failure.
+- **When to use it:** When the source material reviews other companies, products, or strategies.
+- **Examples:**
+  - "Stripe's documentation is a masterclass. Here is a 5-minute teardown of why."
+  - "Why [Company X] failed their launch (and the 3 things you can learn from it)."
+
+## 6. The Pattern-Break Hook
+- **What it does:** Uses extreme brevity or bold formatting to stop the scroll immediately.
+- **When to use it:** When the thesis is incredibly simple but powerful.
+- **Examples:**
+  - "Nobody cares about your features."
+  - "Your pricing model is broken."

package/skills/noise-to-linkedin-carousel/references/output-format.md

@@ -0,0 +1,59 @@
+# Output Format Schema
+
+When returning the LinkedIn carousel content pack, you MUST format your response deterministically according to this exact schema. 
+
+## Assumptions *(optional)*
+Use this section **only** when the source input is weak, ambiguous, or too sparse to extract a clear thesis. State what you assumed and why.  
+**Omit this section entirely when the input is sufficient.**
+
+
+
+## 1. Distilled Thesis
+**Thesis:** *[One sharp, clear sentence capturing the core idea that the entire carousel will communicate. No jargon.]*
+
+## 2. Audience Angle
+**Target Audience & Angle:** *[A short statement explaining exactly who this carousel is for, and why this specific angle is highly relevant to them.]*
+
+## 3. Content Goal
+**Goal:** *[Educate, provoke, summarize, convert, or inspire. What should the reader feel at the end?]*
+
+## 4. Hook Options
+**Hooks:**  
+Offer 3 alternative cover-slide hook lines to grab attention, citing the pattern used.
+- **Option 1 ([Hook Pattern Name]):** *[Text]*
+- **Option 2 ([Hook Pattern Name]):** *[Text]*
+- **Option 3 ([Hook Pattern Name]):** *[Text]*
+
+## 5. Recommended Carousel Structure
+**Slide Count:** *[e.g., 7 slides]*
+
+## 6. Slide-by-Slide Breakdown
+
+Produce a detailed breakdown for each slide. Each slide should focus on ONE core idea.
+
+### Slide 1: Cover
+- **Slide Role:** Cover
+- **Slide Title / Headline:** *[The chosen best hook from above]*
+- **Visual Direction:** *[e.g., Large bold text centered, dark background with subtle neon accent]*
+
+### Slide 2: [Slide Role (e.g., Problem)]
+- **Slide Role:** *[e.g., Problem, Reframe, Insight, Proof, etc.]*
+- **Slide Title / Headline:** *[Short, punchy headline]*
+- **Slide Body Copy:** *[Concise body copy (no long paragraphs, bullet points preferred)]*
+- **Visual Direction:** *[e.g., Two-column layout: text on left, simple diagram on right]*
+
+*[Repeat for Slides 3 to N-1 as appropriate, ensuring fluid narrative progression...]*
+
+### Slide [N]: CTA (Call to Action)
+- **Slide Role:** CTA
+- **Slide Title / Headline:** *[Clear takeaway or action prompt]*
+- **Slide Body Copy:** *[What the user should do next (e.g., Follow, subscribe, comment)]*
+- **Visual Direction:** *[e.g., Profile picture, arrow pointing to the "Follow" button]*
+
+## 7. Supporting LinkedIn Caption
+**Caption:**  
+*[A caption to post alongside the document on LinkedIn. It should complement the slide deck, add 1-2 sentences of context without repeating verbatim, pose a question or brief hook, and include 3-5 relevant hashtags.]*
+
+## 8. Designer Handoff (Optional)
+**Visual/Formatting Guidance:**  
+*[Brief notes for the person or tool building the carousel (e.g., formatting styles, hierarchy, or structural intent limits).]*

package/skills/noise-to-linkedin-carousel/references/quality-checklist.md

@@ -0,0 +1,12 @@
+# Quality Checklist Rubric
+
+Before finalizing the output for the user, aggressively evaluate the draft against this strict grading rubric:
+
+- [ ] **One idea per slide:** Does any slide contain more than one distinct point? If yes, split it into two slides or delete one point.
+- [ ] **No duplicated points:** Does Insight 3 just re-say Insight 1 differently? Ensure every slide earns its place.
+- [ ] **No paragraph-heavy slides:** Are there walls of text? Ensure all body copy is scannable (short sentences or 2-3 bullets).
+- [ ] **Intentional slide flow:** Does the progression (Problem -> Reframe -> Insight -> Framework) logically build momentum?
+- [ ] **Meaningfully distinct hooks:** Are the 3 provided cover hooks truly different from one another (using different formulas)?
+- [ ] **Specific CTA:** Does the call-to-action make a specific request tied to the topic, rather than a generic "like and subscribe"?
+- [ ] **Complementary caption:** Does the LinkedIn caption add value without just summarizing the slides verbatim?
+- [ ] **Target audience alignment:** Does the output fit a founder, GTM engineer, or technical marketing use case? (No overly generic life-coach fluff.)

package/skills/noise-to-linkedin-carousel/references/slide-types.md

@@ -0,0 +1,57 @@
+# Slide Types & Taxonomy
+
+Use these defined slide roles when structuring the slide sequence in the content pack. 
+
+## Cover
+- **Purpose:** Stops the scroll. The hook that buys you attention.
+- **When to Use:** Always the first slide (Slide 1).
+- **Copy:** Massive contrast, highly clickable headline. Very little other text.
+- **Avoid:** Subtitles that are too long, or introducing the solution immediately.
+
+## Problem
+- **Purpose:** Agitates the pain point or sets the stage. Why does the reader need to keep swiping?
+- **When to Use:** Usually Slide 2, right after the cover.
+- **Copy:** Short statement of the status quo and why it hurts.
+- **Avoid:** Blaming the reader directly without empathy; getting bogged down in edge cases.
+
+## Reframe
+- **Purpose:** Shifts the reader's perspective on the problem.
+- **When to Use:** After the problem, before the deep insights.
+- **Copy:** "Instead of X, think Y." A punchy paradigm shift.
+- **Avoid:** Generic platitudes. It must be a specific paradigm shift.
+
+## Insight
+- **Purpose:** The "meat" of the carousel. One specific, strong point per slide.
+- **When to Use:** The core body of the carousel (Slides 3-6). 
+- **Copy:** One clear, declarative sentence and optionally 1-3 crisp bullets.
+- **Avoid:** Mixing multiple ideas. If there are 3 insights, use 3 separate insight slides.
+
+## Framework
+- **Purpose:** A sequential or structured piece of advice.
+- **When to Use:** When teaching an actionable method or process.
+- **Copy:** Step 1, Step 2, Step 3, or a named methodology.
+- **Avoid:** Overcomplicating the steps. Keep it scannable.
+
+## Example
+- **Purpose:** Demonstrates the insight in action.
+- **When to Use:** Immediately after a complex insight or framework.
+- **Copy:** A quick case study, before/after metric, story, or screenshot description.
+- **Avoid:** Long-winded stories. Keep it grounded and brief.
+
+## Proof
+- **Purpose:** Builds immediate credibility.
+- **When to Use:** Towards the end, or right after introducing a controversial reframe.
+- **Copy:** Hard numbers, recognized logos, or direct quotes.
+- **Avoid:** Vague statements like "many companies do this."
+
+## Takeaway
+- **Purpose:** Brings the previous slides together into one lesson.
+- **When to Use:** The second to last slide, right before the CTA.
+- **Copy:** The "TL;DR" summary of the carousel.
+- **Avoid:** Introducing new information not covered in the carousel.
+
+## CTA (Call to Action)
+- **Purpose:** Converts the attention into an action.
+- **When to Use:** Always the final slide.
+- **Copy:** Tells the reader exactly what to do next (e.g., Follow, DM me, Drop a comment).
+- **Avoid:** Asking for multiple conflicting actions (e.g., "Like, subscribe, click the link, and comment").

package/skills/oss-launch-kit/.env.example

@@ -0,0 +1,2 @@
+# GitHub API access for repo context fetching
+GITHUB_TOKEN=

package/skills/oss-launch-kit/PRD.md

@@ -0,0 +1,122 @@
+# oss-launch-kit PRD
+
+## Overview
+`oss-launch-kit` is an advanced OpenDirectory skill that turns a public GitHub repo URL into a grounded launch package for open-source projects.
+
+The v1 output is a single Markdown document containing:
+- executive summary & launch readiness
+- Launch Readiness Fix Plan
+- soft launch strategy (for medium readiness)
+- coordinated launch timeline (for medium/high readiness)
+- channel strategy hooks (Show HN, PH, Reddit, X)
+- explicit handoffs to specialized skills ([!TIP])
+- full confidence notes & assumptions
+
+## Problem Statement
+Open-source maintainers often know how to build and ship the product, but not how to package it for launch. The hardest part is not writing generic marketing copy; it is translating a repo’s real signal into channel-specific content that is honest, specific, and usable.
+
+This skill solves that by taking one repo URL and generating launch assets that a maintainer can post or adapt with minimal editing.
+
+### Why a repo URL is enough for v1
+A GitHub repo already exposes the highest-signal inputs for launch copy:
+- repository name and description
+- README content
+- topics and homepage
+- primary language
+- stars, forks, license
+- optional release metadata
+
+That is enough to infer what the project is, who it is for, what problem it solves, and what makes it worth announcing. V1 does not need deeper scraping or user-provided briefs.
+
+### Why this is better scoped than the previous FAQ attempt
+The closed `api-error-to-faq-builder` idea tried to infer support content from noisy inputs and broad product repos, which made hallucination and generic output more likely.
+
+`oss-launch-kit` is narrower in three ways:
+- input is a single public repo with structured metadata
+- output is a bounded launch kit, not open-ended support material
+- the skill can stay grounded in the repo’s own README and metadata
+
+That makes the challenge more mergeable and easier to validate.
+
+## Goals
+- Analyze repo context to determine appropriate launch channels and project maturity.
+- Act as a Phase 0 orchestrator: decide *if* and *how* to launch, not to write every post.
+- Provide a prioritized, actionable Launch Readiness Fix Plan for missing signals.
+- Generate strategic hooks and positioning for key channels.
+- Provide a coordinated, day-by-day launch strategy.
+- Minimize hallucinations and unsupported claims.
+- Explicitly flag low-confidence areas when the README or metadata is sparse.
+
+## Non-Goals
+- No direct posting to Product Hunt, Reddit, HN, or X.
+- No scraping of private sites.
+- No invented traction, testimonials, users, or metrics.
+- No attempt to infer hidden business strategy or audience beyond available evidence.
+
+## User Input Contract
+### Required CLI input
+- `--repo-url <url>`: public GitHub repository URL.
+
+### Optional CLI inputs
+- `--output <path>`: write Markdown to a file instead of stdout.
+  - default: `launch-kit.md`
+
+### Environment variables
+- `GITHUB_TOKEN`: optional, used to raise GitHub API rate limits.
+- `OPENAI_API_KEY` or equivalent model credentials only if the implementation uses a hosted LLM.
+
+### Validation rules
+- Repo URL must resolve to a public GitHub repository.
+- Invalid or private repos should fail with a clear message.
+- If README is missing, the skill should continue with lowered confidence and flag the gap.
+
+## Output Contract
+The output must be a single Markdown document with stable headings.
+
+### Required structure
+1. `# Launch Orchestrator for <repo>`
+2. `## Executive Summary & Launch Readiness` (with readiness score and CAUTION nodes)
+3. `## Launch Readiness Fix Plan` (Condition: Readiness is LOW/MEDIUM)
+4. `## Soft Launch Strategy` (Condition: Readiness is MEDIUM)
+5. `## Coordinated Launch Timeline` (Condition: Readiness is MEDIUM/HIGH)
+6. `## Channel Strategy & Positioning` (Condition: Readiness is HIGH)
+7. `## Full Confidence Notes & Assumptions`
+
+### Content expectations
+- Executive Summary cites only verified repo facts and computed project maturity.
+- Fix Plan provides prioritized, actionable steps (e.g., "Add Quickstart", "Add License").
+- Channel Strategy provides hooks, taglines, and niche community targets.
+- Coordinated Launch Timeline is a practical, day-based coordination plan.
+- Integration uses `[!TIP]` handoffs to specialized skills (`producthunt-launch-kit`, `show-hn-writer`, etc.).
+- Low-confidence areas must explicitly list anything inferred rather than verified.
+
+## Data Sources
+### Essential
+- repo name
+- repo description
+- README
+- topics
+- homepage
+- primary language
+- stars
+- forks
+- license
+
+### Optional
+- latest release metadata
+- release notes
+- repo archived/fork status
+- README badges if easily parsed
+
+### Priority order
+1. README
+2. repo description
+3. topics and homepage
+4. language, stars, forks, license
+5. optional release info
+
+## Success Criteria
+- Launch assets feel specific to the repo, not generic.
+- No fabricated claims.
+- The user can use the drafts with light editing.
+- Weak repos still produce honest output with confidence notes.

package/skills/oss-launch-kit/README.md

@@ -0,0 +1,27 @@
+<img src="./hero.png" width="100%" alt="OSS Launch Kit Cover" />
+
+# oss-launch-kit (Orchestrator)
+
+The high-level **OSS Launch Orchestrator** for GitHub repositories. It serves as the strategic entry point that analyzes your repo and coordinates a multi-channel launch plan.
+
+## Features
+
+- **Project Analysis**: Differentiates between CLI tools, libraries, apps, and templates.
+- **Enhanced Readiness**: Checks for installation guides, usage examples, license, and metadata.
+- **Channel Orchestration**: Recommends the best channels (PH, HN, Reddit, X) based on fitness.
+- **Skill Hand-offs**: Provides hooks and pointers to `show-hn-writer`, `producthunt-launch-kit`, and `reddit-post-engine`.
+- **Honest Feedback**: Explicitly flags low-readiness repos and recommends documentation sprints.
+
+## Usage
+
+```bash
+# Generate a launch strategy and checklist for a repo
+python scripts/run.py --repo-url https://github.com/owner/repo
+```
+
+## Differentiation
+
+Unlike single-channel generators, `oss-launch-kit` acts as the **Root Strategy Layer**:
+1. It tells you **if and where** you should launch.
+2. It provides a **timed checklist** for coordination.
+3. It hands off to **specialized skills** for channel-specific drafting.

package/skills/oss-launch-kit/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: oss-launch-kit
+description: Higher-level OSS launch orchestrator that analyzes repos, selects channels, and coordinates launch plans.
+compatibility: [claude-code, gemini-cli, github-copilot]
+author: OpenDirectory
+version: 0.2.0
+---
+
+# OSS Launch Kit (Orchestrator)
+
+The `oss-launch-kit` is the **root orchestration layer** for open-source launches in OpenDirectory. It turns a GitHub repository URL into a grounded, coordinated launch strategy. 
+
+Rather than just writing generic copy, this skill serves as the **Strategic Entry Point**: it evaluates readiness, determines channel fitness (Show HN vs. Product Hunt vs. Reddit), and provides the coordination logic needed to use specialized skills effectively.
+
+## How it works
+
+- **Project Analysis**: Differentiates between CLI tools, libraries, apps, and templates.
+- **Launch Readiness**: Stronger checks for installation guides, examples, and licenses.
+- **Skill Orchestration**: Provides hooks and explicit handoffs to `show-hn-writer`, `producthunt-launch-kit`, and `reddit-post-engine`.
+- **Coordinated Strategy**: A timed checklist for multi-channel launches.
+- **Honest Feedback**: Proactively flags sparse READMEs and recommends documentation sprints.
+
+## When to use
+
+- **Primary Entry Point**: Use this first to map out your launch strategy.
+- **Readiness Assessment**: Determine if your repo is actually ready for high-friction channels.
+- **Skill Orchestration**: Get hooks and handoffs to specialized skills:
+  - `show-hn-writer` (for technical deep-dives)
+  - `producthunt-launch-kit` (for PH assets and badges)
+  - `reddit-post-engine` (for community-specific variants)
+  - `tweet-thread-from-blog` (for Twitter/X threads)
+  - `linkedin-post-generator` (for LinkedIn posts)
+- **Coordinated Strategy**: Get a realistic, timed checklist for multiple platforms.