@opendirectory.dev/skills 0.1.64 → 0.1.65

package/skills/docs-from-code/README.md

@@ -13,7 +13,7 @@ npx "@opendirectory.dev/skills" install docs-from-code --target claude
 ### Video Tutorial
 Watch this quick video to see how it's done:
 
-https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
+https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
 
 ### Step 1: Download the skill from GitHub
 1. Copy the URL of this specific skill folder from your browser's address bar.
@@ -27,95 +27,3 @@ https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
 4. Choose the option to **Upload a skill**, and drag and drop the `.zip` file (or you can extract it and drop the folder, both work).
 
 > **Note:** For some skills (like `position-me`), the `SKILL.md` file might be located inside a subfolder. Always make sure you are uploading the specific folder that contains the `SKILL.md` file!
-
-## What It Generates
-
-| Output | When |
-|--------|------|
-| `README.md` (full) | Project has no README |
-| `README.md` (sections) | README exists but API or architecture sections are stale |
-| `docs/API.md` | Project has HTTP routes |
-| Architecture section | Always, from graphify's god nodes and communities |
-| GitHub PR | When you ask it to open one |
-
-## Why graphify?
-
-The skill uses graphify as its extraction engine:
-- 20 languages via tree-sitter AST: Python, TypeScript, Go, Rust, Java, and 15 more
-- Architecture insight: god nodes and community clusters show what everything connects through
-- 71.5x fewer tokens than reading raw files, efficient on large codebases
-- SHA256 cache: re-runs only process changed files
-- Honest tagging: `EXTRACTED` (found in source) vs `INFERRED` (reasonable inference with confidence score)
-- Extracts rationale from `# NOTE:`, `# WHY:`, `# HACK:` comments and docstrings
-
-The bundled `scripts/` (TypeScript and Python AST extractors) serve as a fallback if graphify is unavailable.
-
-## Supported Languages (via graphify)
-
-Python, TypeScript, JavaScript, Go, Rust, Java, C, C++, Ruby, C#, Kotlin, Scala, PHP, Swift, Lua, Zig, PowerShell, Elixir, Objective-C, Julia
-
-## Requirements
-
-- Python 3.10+ (for graphify)
-- Node.js 18+ (for fallback TypeScript extractor)
-- `gh` CLI (optional, for opening PRs automatically)
-- `GITHUB_TOKEN` env var (optional, for PRs)
-
-## Setup
-
-### 1. Install graphify
-
-```bash
-pip install graphifyy
-```
-
-No API keys needed for extraction. graphify uses your agent's existing model access.
-
-### 2. Configure (Optional)
-
-```bash
-cp .env.example .env
-# Add GITHUB_TOKEN if you want auto-PR support
-```
-
-## How to Use
-
-Be inside your project and ask:
-
-```
-"Generate a README for this project"
-"My API docs are out of date, update them from the code"
-"Create docs/API.md from my FastAPI routes"
-"Add an architecture section to our README"
-"Document this TypeScript library"
-```
-
-The agent will:
-1. Run `graphify . --no-viz` to build a knowledge graph of your codebase
-2. Read `GRAPH_REPORT.md` for god nodes, communities, and architecture insights
-3. Query the graph for routes, types, and data models
-4. Read existing docs to understand what needs updating
-5. Generate accurate docs grounded in the graph
-6. Write files and optionally open a GitHub PR
-
-## Project Structure
-
-```
-docs-from-code/
-├── SKILL.md                         # Agent instructions
-├── README.md                        # This file
-├── .env.example                     # Environment variables template
-├── scripts/
-│   ├── package.json                 # Script dependencies (ts-morph)
-│   ├── extract_ts.ts                # TypeScript/JS AST extractor
-│   └── extract_py.py                # Python AST extractor
-├── references/
-│   ├── extraction-guide.md          # Per-framework extraction notes
-│   └── output-template.md          # README and API.md templates
-└── evals/
-    └── evals.json                   # Test prompts
-```
-
-## License
-
-MIT

package/skills/email-newsletter/README.md

@@ -11,7 +11,7 @@ npx "@opendirectory.dev/skills" install email-newsletter --target claude
 ### Video Tutorial
 Watch this quick video to see how it's done:
 
-https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
+https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
 
 ### Step 1: Download the skill from GitHub
 1. Copy the URL of this specific skill folder from your browser's address bar.
@@ -25,74 +25,3 @@ https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
 4. Choose the option to **Upload a skill**, and drag and drop the `.zip` file (or you can extract it and drop the folder, both work).
 
 > **Note:** For some skills (like `position-me`), the `SKILL.md` file might be located inside a subfolder. Always make sure you are uploading the specific folder that contains the `SKILL.md` file!
-
----
-
-## What it does
-
-- Asks the 19 questions that actually determine your newsletter layout
-- Writes all sections: hero, intro, main content, stat callout, CTA, footer
-- Generates table-based HTML with inline styles -- compatible with every major email client
-- Tunes variable syntax per platform (Loops, Mailchimp, Beehiiv, Resend)
-- Produces 3 subject line options using proven formulas
-- Includes a plain-text fallback for deliverability
-
-## Example
-
-> "Write a newsletter about how AI is changing B2B sales. Audience: VPs of Sales at 100-500 person SaaS companies. CTA: join our upcoming webinar. Tone: direct. Platform: Beehiiv."
-
-Output: full HTML email with hero headline, 3-section body, stat callout, CTA block, and footer -- plus 3 subject line options and a plain-text version, tuned for Beehiiv.
-
-## Supported platforms
-
-| Platform | Notes |
-|---|---|
-| Loops | `{{unsubscribe_url}}` syntax. Paste into custom HTML editor |
-| Mailchimp | `*\|UNSUB\|*` syntax. Use "Code your own" template. Includes `mc:edit` regions |
-| Beehiiv | `%%unsubscribe_url%%` syntax. Works with custom HTML block |
-| Resend | `{unsubscribeUrl}` syntax. React Email `.tsx` output available on request |
-| Generic | `[UNSUBSCRIBE_URL]` placeholder -- replace before sending |
-
-## Output formats
-
-- **Standard HTML** (default): inline-styled, table-based, 600px max-width
-- **Plain text**: always included unless you opt out
-- **React Email** (on request): `.tsx` component output for Resend / dev teams
-
-## Parameters
-
-| Param | Required | Notes |
-|---|---|---|
-| topic | Yes | What the newsletter is about |
-| audience | Yes | Who is reading |
-| cta | Yes | Primary action you want readers to take |
-| company_name | No | Brand name for header and footer |
-| tagline | No | One-line description for footer |
-| city_country | No | Footer location (e.g. "San Francisco, US") |
-| cta_url | No | Actual link for CTA button -- placeholder used if omitted |
-| brand_color | No | Hex code -- used for strip, stat border, category label |
-| background | No | dark / light / custom hex (default: dark) |
-| display_font | No | editorial serif / modern sans / system fonts (default: Instrument Serif) |
-| button_style | No | pill / softly rounded / sharp (default: pill) |
-| visual_style | No | editorial / technical+data / warm+founder / bold+campaign |
-| tone | No | educational / conversational / bold+direct / formal / playful |
-| platform | No | loops / mailchimp / beehiiv / resend (default: generic) |
-| personalization | No | none / first name / first name + company (default: none) |
-| length | No | brief (300w) / standard (500-700w) / deep dive (800w+) |
-| format | No | editorial article / numbered breakdown / personal story / data report |
-| subject_line | No | If omitted, 3 options are suggested |
-| secondary_sections | No | sponsor block / product callout / event / quick links |
-
-## No API keys required
-
-Pure AI skill. No external services, no scraping, no dependencies to install.
-
-## Design principles
-
-- Max width 600px (email client standard)
-- Inline styles only -- no external CSS, email clients strip it
-- Table-based layout for Outlook compatibility
-- Georgia serif for hero headlines, Arial/system font for body
-- CTA buttons use the table+td VML-compatible structure
-- All images include alt text
-- Dark mode aware where platform supports it

package/skills/explain-this-pr/README.md

@@ -14,7 +14,7 @@ npx "@opendirectory.dev/skills" install explain-this-pr --target claude
 ### Video Tutorial
 Watch this quick video to see how it's done:
 
-https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
+https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
 
 ### Step 1: Download the skill from GitHub
 1. Copy the URL of this specific skill folder from your browser's address bar.
@@ -28,71 +28,3 @@ https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
 4. Choose the option to **Upload a skill**, and drag and drop the `.zip` file (or you can extract it and drop the folder, both work).
 
 > **Note:** For some skills (like `position-me`), the `SKILL.md` file might be located inside a subfolder. Always make sure you are uploading the specific folder that contains the `SKILL.md` file!
-
-## What It Does
-
-- Fetches the PR diff and metadata via `gh`
-- Writes two paragraphs: what changed (technical) and why it matters (impact)
-- Posts the explanation as a PR comment with `gh pr comment`
-- Works with any public or private repo you have access to via `gh`
-
-## Requirements
-
-| Requirement | Purpose | How to Set Up |
-|------------|---------|--------------|
-| `gh` CLI | Fetching PR data and posting comments | https://cli.github.com, then run `gh auth login` |
-
-No API keys needed.
-
-## How to Use
-
-Explain a PR by URL:
-
-```
-"Explain this PR: https://github.com/owner/repo/pull/123"
-"What does this PR do? https://github.com/owner/repo/pull/456"
-"Summarize this pull request: [URL]"
-```
-
-Explain by PR number (in the current repo):
-
-```
-"Explain PR #42"
-"Add a summary comment to PR #99"
-```
-
-Explain the current branch PR:
-
-```
-"Explain the current branch PR"
-"Add a plain-English comment to my PR"
-```
-
-Output without posting:
-
-```
-"Explain this PR but don't post the comment: [URL]"
-"What does this PR change? Just give me the text."
-```
-
-## Output Format
-
-Two paragraphs, under 150 words total.
-
-Paragraph 1: What it does (technical). Names the specific files, functions, or systems that changed. States the before/after if visible in the diff.
-
-Paragraph 2: Why it matters (impact). Explains who benefits and what problem is solved. Omitted if there is no clear "why" in the diff or commits. The skill never guesses at impact.
-
-## Project Structure
-
-```
-explain-this-pr/
-├── SKILL.md
-├── README.md
-└── evals/
-    └── evals.json
-```
-
-## License
-
-MIT

package/skills/gh-issue-to-demand-signal/README.md

@@ -11,12 +11,12 @@ npx "@opendirectory.dev/skills" install gh-issue-to-demand-signal --target claud
 ### Video Tutorial
 Watch this quick video to see how it's done:
 
-https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
+https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
 
 ### Step 1: Download the skill from GitHub
-1. Click the **Code** button on this repo's GitHub page.
-2. Select **Download ZIP** to download the repository.
-3. Extract the ZIP file on your computer.
+1. Copy the URL of this specific skill folder from your browser's address bar.
+2. Go to [download-directory.github.io](https://download-directory.github.io/).
+3. Paste the URL and click **Enter** to download.
 
 ### Step 2: Install the Skill in Claude
 1. Open your **Claude desktop app**.
@@ -25,94 +25,3 @@ https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
 4. Choose the option to **Upload a skill**, and drag and drop the `.zip` file (or you can extract it and drop the folder, both work).
 
 > **Note:** For some skills (like `position-me`), the `SKILL.md` file might be located inside a subfolder. Always make sure you are uploading the specific folder that contains the `SKILL.md` file!
-
-## What It Does
-
-- Fetches up to 200 open issues from any public GitHub repo (no auth required)
-- Filters noise locally: removes PRs, bot issues, zero-engagement issues, and chore-pattern titles
-- Computes a demand score per issue: `(reactions["+1"] x 2) + (comments x 0.5)`
-- Detects "ignored demand": issues with 10+ reactions, open 6+ months, no planned label
-- Clusters issues into 6 categories using the AI running the skill (no external API key needed): feature gaps, bug patterns, UX complaints, performance issues, missing integrations, missing docs
-- Generates 5-8 cluster themes with total demand scores
-- Messaging brief: 3 positioning angles + 3 outreach hooks + cluster-specific headlines
-- Saves output to `docs/demand-signals/[owner]-[repo]-[date].md`
-
-## Requirements
-
-| Requirement | Purpose | How to Set Up |
-|---|---|---|
-| GitHub token | Raises rate limit from 60/hr to 5000/hr | github.com/settings/tokens (no scopes needed for public repos) |
-
-No external AI API key needed. The skill uses the AI assistant running it (Claude, Gemini, Copilot) to do the clustering and messaging brief. GitHub token is optional but recommended for repeated use.
-
-## Setup
-
-```bash
-cp .env.example .env
-# Add GITHUB_TOKEN (optional, recommended for repeated use)
-```
-
-## How to Use
-
-```
-"Scan competitor GitHub issues: https://github.com/vercel/next.js"
-"What are users asking for in facebook/react?"
-"Find demand gaps in linear-app/linear"
-"Turn GitHub complaints into messaging: https://github.com/supabase/supabase"
-"What should I build based on competitor issues? vercel/next.js"
-"Which features are users begging for in this repo?"
-```
-
-## Why This Matters
-
-A busy product team cannot read 500 open issues. This skill does the work: ranks by real user demand (reaction counts), clusters into actionable GTM categories, detects ignored demand (where competitors have been silent the longest), and translates raw complaints into positioning language.
-
-**The demand score formula:** `(reactions["+1"] x 2) + (comments x 0.5)`. Reactions are weighted higher than comments because reactions are pure signal -- a thumbs-up means "I want this." Comments include maintainer responses, off-topic discussion, and spam.
-
-**Ignored demand is your opportunity:** An issue with 50 reactions that has been open for 2 years with no planned label means their users have been waiting. That is your product's first billboard.
-
-## The 6 Demand Categories
-
-| Category | What it captures |
-|---|---|
-| `feature_gap` | Functionality that does not exist yet |
-| `bug_pattern` | Recurring broken behavior that erodes trust |
-| `ux_complaint` | Friction, confusion, or workflow problems |
-| `performance` | Slowness, timeouts, resource usage |
-| `integration_missing` | Requests to connect with other tools or APIs |
-| `docs_missing` | Confusion caused by absent or wrong documentation |
-
-## Output
-
-Each run produces:
-
-1. **Demand Gap Leaderboard**: clusters ranked by total demand score
-2. **Ignored Demand section**: issues open 6+ months with 10+ reactions and no response
-3. **Top 10 Highest-Demand Issues**: verbatim titles, reaction counts, direct GitHub links
-4. **Cluster Deep Dives**: top 3 clusters with theme name, pain summary, top 3 verbatim issues
-5. **Messaging Brief**: 3 positioning angles citing exact demand evidence
-6. **GTM Angles**: 3 outreach hooks using verbatim issue language
-
-## Cost per Run
-
-- GitHub API: 2 calls -- free (unauthenticated: 60/hr limit, token: 5000/hr)
-- AI analysis: uses the model already running the skill -- no additional cost
-- Total: free
-
-## Project Structure
-
-```
-gh-issue-to-demand-signal/
-├── SKILL.md
-├── README.md
-├── .env.example
-├── evals/
-│   └── evals.json
-└── references/
-    ├── demand-categories.md
-    └── gtm-translation.md
-```
-
-## License
-
-MIT

package/skills/google-trends-api-skills/README.md

@@ -13,7 +13,7 @@ npx "@opendirectory.dev/skills" install google-trends-api-skills --target claude
 ### Video Tutorial
 Watch this quick video to see how it's done:
 
-https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
+https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
 
 ### Step 1: Download the skill from GitHub
 1. Copy the URL of this specific skill folder from your browser's address bar.
@@ -27,76 +27,3 @@ https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
 4. Choose the option to **Upload a skill**, and drag and drop the `.zip` file (or you can extract it and drop the folder, both work).
 
 > **Note:** For some skills (like `position-me`), the `SKILL.md` file might be located inside a subfolder. Always make sure you are uploading the specific folder that contains the `SKILL.md` file!
-
-## Skills
-
-### 1. `google-trends-api/`
-The API layer — knows how to query Google Trends through SerpApi, handle responses, manage rate limits, and cache results.
-
-### 2. `seo-keyword-research/`
-The SEO workflow — uses Google Trends data to find breakout keywords, build content structure, and generate SEO-optimized blog outlines.
-
-## Quick Start
-
-```bash
-# 1. Get a free API key (250 searches/month)
-# https://serpapi.com/
-
-# 2. Set your key
-export SERPAPI_KEY="your_key_here"
-
-# 3. Install dependency
-pip install requests
-
-# 4. Run keyword research for a blog topic
-python seo-keyword-research/scripts/blog_seo_research.py "kubernetes deployment"
-
-# 5. Or just discover trending keywords
-python google-trends-api/scripts/discover_keywords.py "AI developer tools"
-```
-
-## Directory Structure
-
-```
-google-trends-api/
-├── SKILL.md                        # API skill (endpoints, params, usage)
-├── scripts/
-│   └── discover_keywords.py        # Keyword discovery script
-└── references/
-    └── api-responses.md            # Full API response structures
-
-seo-keyword-research/
-├── SKILL.md                        # SEO workflow skill (research -> outline)
-├── scripts/
-│   └── blog_seo_research.py        # Full blog SEO research script
-└── references/
-    ├── keyword-placement-guide.md  # Detailed keyword placement rules
-    └── tech-blog-examples.md       # Real examples for tech/dev blogs
-```
-
-## How It Works
-
-```
-User: "Write a blog about kubernetes deployment"
-  |
-  v
-[google-trends-api] RELATED_QUERIES -> finds "kubernetes vs docker" (Breakout!)
-[google-trends-api] RELATED_TOPICS  -> finds "Helm", "CI/CD", "Container Orchestration"
-  |
-  v
-[seo-keyword-research] Selects primary keyword, builds outline
-  |
-  v
-Output: SEO-optimized blog outline targeting trending keywords
-```
-
-## Specification
-
-These skills follow the [Agent Skills specification](https://agentskills.io/specification). Each skill has:
-- `SKILL.md` with YAML frontmatter (name, description, compatibility, metadata)
-- `scripts/` for executable code
-- `references/` for detailed documentation (loaded on demand)
-
-## License
-
-MIT

package/skills/graphic-case-study/README.md

@@ -7,10 +7,11 @@ Generate a professionally designed case study PDF for B2B SaaS sales and marketi
 ```bash
 npx "@opendirectory.dev/skills" install graphic-case-study --target claude
 ```
+
 ### Video Tutorial
 Watch this quick video to see how it's done:
 
-https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
+https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
 
 ### Step 1: Download the skill from GitHub
 1. Copy the URL of this specific skill folder from your browser's address bar.
@@ -23,99 +24,4 @@ https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
 3. Click on the **Skills** tab, then click on the **+** (plus) icon button to create a new skill.
 4. Choose the option to **Upload a skill**, and drag and drop the `.zip` file (or you can extract it and drop the folder, both work).
 
-> **Note:** Make sure you upload the folder that contains the `SKILL.md` file directly.
-
----
-
-## What it does
-
-- Asks the questions that determine how the case study should be structured
-- Interviews you (or processes your notes) to extract customer story details
-- Structures the narrative: customer context → challenge → solution → results → testimonial
-- Generates a single self-contained HTML file -- opens in any browser, no build tools
-- Splits into per-page HTML files for individual sharing or editing
-- Exports a print-ready PDF via Playwright (A4 portrait, 1200×1697px)
-- Supports 1-pager summary card, standard 2-pager, and detailed 4-pager formats
-
-## Example
-
-> "Create a 2-page case study for Acme Corp. They were spending 20 hrs/week on manual reporting. We automated it. They saved 80% of that time and reduced errors by 95%. Use midnight-editorial style."
-
-Output: 2-page PDF with cover, challenge/solution spread, results stat page, and closing CTA.
-
----
-
-## Supported Styles
-
-| Style | Best for |
-|---|---|
-| clean-slate | Enterprise B2B, sales teams, any audience that expects professionalism |
-| midnight-editorial | Tech/AI companies, premium B2B, investor-grade materials |
-| matt-gray | Board materials, internal reviews, professional mixed audiences |
-| product-minimal | Product companies, design-forward B2B, design-savvy buyers |
-| mint-pixel-corporate | SaaS sales, tech startups, growth-stage B2B |
-| warm-earth | Agencies, consultancies, service businesses, health/education tech |
-| brutalist | Standout sales materials, design-forward agencies, bold brands |
-| magazine-red | Marketing agencies, brand-forward companies, editorial-style stories |
-| soft-cloud | Onboarding materials, customer education, approachable SaaS |
-
----
-
-## Supported Page Layouts
-
-| Layout | Purpose |
-|---|---|
-| cover | Opening page -- customer name, headline result, logos |
-| overview | At-a-glance: company profile, industry, use case |
-| challenge | The problem -- context paragraph + pain points |
-| solution | How your product solved it -- feature callouts |
-| results | Key metrics in large stat format + supporting narrative |
-| testimonial | Full-width pull quote with attribution |
-| closing-cta | Vendor logo + contact info + next step CTA |
-
----
-
-## Output
-
-| File | What it is |
-|---|---|
-| `case-study/[slug]/index.html` | Full case study, browser-ready |
-| `case-study/[slug]/page-01.html` ... | Per-page HTML files for individual sharing |
-| `case-study/[slug].pdf` | Print-ready PDF (A4 portrait) |
-
-Standard dimensions: 1200×1697px (A4 portrait). Landscape 4:3 (1200×900) available on request.
-
----
-
-## Parameters
-
-| Param | Required | Notes |
-|---|---|---|
-| customer_name | Yes | Company name (or "Anonymous Fortune 500 Retailer" to anonymize) |
-| challenge | Yes | Core problem in 2-5 sentences |
-| solution | Yes | What your product did |
-| results | Yes | Measurable outcomes -- ideally 3 stats |
-| customer_context | No | Industry, size, location (for overview page) |
-| testimonial | No | Customer quote + name + title |
-| page_count | No | 1 / 2 / 4 (default: 2) |
-| customer_logo | No | Logo URL for cover page |
-| your_company_name | No | Vendor name + logo URL for CTA page |
-| style | No | One of 9 named presets or "show me options" (default: clean-slate) |
-| orientation | No | A4 portrait (default) or landscape 4:3 |
-| anonymize | No | Keep name or replace with industry descriptor |
-| slug | No | Filename slug (derived from customer name if omitted) |
-
----
-
-## Dependencies
-
-This skill requires the `frontend-slides` skill files at:
-`/Users/ksd/Desktop/Varnan_skills/frontend-slides/`
-
-Specifically:
-- `viewport-base.css` -- responsive page foundation (included verbatim in generated HTML)
-- `scripts/export-pdf.sh` -- PDF export via Playwright (Node.js required, auto-installs; use `--portrait` flag for A4)
-
-## No API keys required
-
-Pure AI skill. No external services, no scraping, no dependencies beyond the above.
+> **Note:** For some skills (like `position-me`), the `SKILL.md` file might be located inside a subfolder. Always make sure you are uploading the specific folder that contains the `SKILL.md` file!

package/skills/graphic-chart/README.md

@@ -8,6 +8,24 @@ Generate publication-quality data visualization charts as PNG using Chart.js v4.
 npx "@opendirectory.dev/skills" install graphic-chart --target claude
 ```
 
+### Video Tutorial
+Watch this quick video to see how it's done:
+
+https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
+
+### Step 1: Download the skill from GitHub
+1. Copy the URL of this specific skill folder from your browser's address bar.
+2. Go to [download-directory.github.io](https://download-directory.github.io/).
+3. Paste the URL and click **Enter** to download.
+
+### Step 2: Install the Skill in Claude
+1. Open your **Claude desktop app**.
+2. Go to the sidebar on the left side and click on the **Customize** section.
+3. Click on the **Skills** tab, then click on the **+** (plus) icon button to create a new skill.
+4. Choose the option to **Upload a skill**, and drag and drop the `.zip` file (or you can extract it and drop the folder, both work).
+
+> **Note:** For some skills (like `position-me`), the `SKILL.md` file might be located inside a subfolder. Always make sure you are uploading the specific folder that contains the `SKILL.md` file!
+
 ### Manual Install (2 steps)
 
 1. Copy the URL of this skill folder, paste it at [download-directory.github.io](https://download-directory.github.io/), download the zip.
@@ -102,3 +120,4 @@ Auto-installed on first run via npm:
 - Chromium browser binary (~200MB, downloaded once and cached)
 
 No API keys required.
+