Oss Launch Kit Agent Skill
Higher-level OSS launch orchestrator that analyzes repos, selects channels, and coordinates launch plans.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/Varnan-Tech/opendirectory --skill oss-launch-kitThe instruction itself
3 sections, as written by the authorOSS 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, andreddit-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.
Other skills for the same job
different authors, same section of the catalogue
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
How to use it
Take varnan-tech/oss-launch-kit from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.