@opendirectory.dev/skills 0.1.65 → 0.1.67

package/skills/graphic-slide-deck/README.md

@@ -1,4 +1,4 @@
-# graphic-slide-deck
+# graphic-slide-deck
 
 Generate a professionally designed HTML slide deck from a brief, content notes, or an existing PowerPoint. Outputs a browser-ready presentation + optional PDF. Supports 13 named layout types and 8 business style presets.
 
@@ -24,4 +24,106 @@ https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
 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!
+> **Note:** Make sure you upload the folder that contains the `SKILL.md` file directly.
+
+---
+
+## What it does
+
+- Asks the questions that determine how a deck should be structured
+- Plans the slide sequence with named layout types for each slide
+- Generates a single self-contained HTML file -- opens in any browser, no build tools
+- Splits into per-slide HTML files for individual sharing or editing
+- Exports a PDF via Playwright (renders animations to final state)
+- Optionally deploys to a live URL via Vercel for phone/tablet sharing
+- Converts existing PowerPoint files to HTML
+
+## Example
+
+> "Create a 12-slide Series A investor deck for DataPulse. Audience: Series A VCs. Style: midnight-editorial."
+
+Output: 12-slide HTML presentation, per-slide HTML files, and a PDF -- covering problem/solution/traction/team/market/ask.
+
+---
+
+## Supported Styles
+
+| Style | Best for |
+|---|---|
+| midnight-editorial | Investor decks, premium B2B, thought leadership |
+| matt-gray | Internal decks, operational reviews, mixed audiences |
+| clean-slate | Sales decks, customer-facing, enterprise-safe |
+| brutalist | Startup pitches, design-forward, tech conferences |
+| mint-pixel-corporate | SaaS sales, product demos, growth-stage pitches |
+| product-minimal | Product demos, feature showcases, design audiences |
+| magazine-red | Marketing reports, campaign reviews, bold internal |
+| soft-cloud | Onboarding, customer education, approachable SaaS |
+
+---
+
+## Supported Layouts
+
+| Layout | Use case |
+|---|---|
+| title-hero | Opening slide -- large headline + subtext |
+| section-divider | Section break -- bold label, minimal design |
+| text-full | Headers + bullet points or paragraphs |
+| text-left-image-right | Side-by-side: text column + visual |
+| image-left-text-right | Side-by-side: image first, text second |
+| two-column-text | Comparisons, pros/cons, before/after |
+| image-full | Full-bleed image with optional caption overlay |
+| image-grid | 2x2 or 3x2 grid of images or screenshots |
+| stat-highlight | 2-4 large KPI metrics (the unmissable slide) |
+| quote-callout | Pull quote with attribution |
+| comparison-table | Feature or option comparison grid |
+| timeline | Horizontal or vertical milestones |
+| closing-cta | Final slide -- CTA, contact info, next steps |
+
+---
+
+## Output
+
+| File | What it is |
+|---|---|
+| `deck/[name]-slides/index.html` | Full presentation, browser-ready |
+| `deck/[name]-slides/slide-001.html` ... | Per-slide HTML files for individual sharing |
+| `deck/[name].pdf` | PDF export (if requested) |
+| Live URL | Deployed Vercel URL (if requested) |
+
+Slides are 1920x1080px (16:9) by default. 1:1 (1080x1080) available for LinkedIn.
+
+---
+
+## Parameters
+
+| Param | Required | Notes |
+|---|---|---|
+| purpose | Yes | investor pitch / sales call / conference talk / internal / onboarding |
+| audience | Yes | VCs, prospects, your team, executives, conference room |
+| topic_or_content | Yes | Freeform brief, notes, URL, or uploaded file |
+| key_message | No | Single sentence the audience must remember |
+| slide_count | No | Default: 12 |
+| style | No | One of 8 named presets or "show me options" (default: clean-slate) |
+| aspect_ratio | No | 16:9 or 1:1 (default: 16:9) |
+| inline_editing | No | Yes/No -- editable in-browser (default: No) |
+| output_format | No | HTML only / HTML+PDF / HTML+PDF+deploy (default: HTML+PDF) |
+| deck_name | No | Slug for file/folder naming (derived from topic if omitted) |
+
+---
+
+## Dependencies
+
+This skill requires the `frontend-slides` skill files at:
+`/Users/ksd/Desktop/Varnan_skills/frontend-slides/`
+
+Specifically:
+- `viewport-base.css` -- responsive slide foundation (included verbatim in generated HTML)
+- `html-template.md` -- SlidePresentation class and inline editing system
+- `animation-patterns.md` -- entrance animations and background effects
+- `scripts/export-pdf.sh` -- PDF export via Playwright (Node.js required, auto-installs)
+- `scripts/deploy.sh` -- Vercel deployment (Node.js required)
+- `scripts/extract-pptx.py` -- PowerPoint content extraction (Python + `python-pptx` required)
+
+## No API keys required
+
+Pure AI skill. No external services, no scraping, no dependencies to install beyond the above.

package/skills/hackernews-intel/README.md

@@ -1,4 +1,4 @@
-# hackernews-intel
+# hackernews-intel
 
 <img width="1280" height="640" alt="hackernews-intel" src="https://github.com/user-attachments/assets/8d75cba9-7c2b-4693-8365-00779ed2b3d3" />
 
@@ -28,3 +28,158 @@ https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
 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 new posts from HN using the free Algolia search API (no API key needed)
+- Checks each match against a local SQLite cache and never alerts on the same post twice
+- Sends a Slack notification with title, URL, points, and comment count
+- Supports dry-run mode to preview matches without sending alerts
+- Configurable lookback window, minimum points threshold, and comment inclusion
+
+## Requirements
+
+| Requirement | Purpose | Where to Get It |
+|------------|---------|-----------------|
+| HN_KEYWORDS | Keywords to monitor | Set in .env, comma-separated list |
+| SLACK_WEBHOOK | Slack alerts | https://api.slack.com/apps, Incoming Webhooks |
+| Node.js 20+ | Running the script | https://nodejs.org |
+
+No API key needed for Hacker News. The HN Algolia API is free and public.
+
+## Setup
+
+### 1. Install dependencies
+
+```bash
+cd hackernews-intel
+npm install
+```
+
+### 2. Configure environment variables
+
+```bash
+cp .env.example .env
+```
+
+Edit `.env`:
+
+```bash
+HN_KEYWORDS=claude code,LLM agents,deno runtime
+SLACK_WEBHOOK=https://hooks.slack.com/services/your/webhook/url
+HN_MIN_POINTS=0
+```
+
+### 3. Create a Slack webhook
+
+1. Go to https://api.slack.com/apps and create or select your app
+2. Enable "Incoming Webhooks" in the app settings
+3. Add a webhook to your workspace and select the target channel
+4. Copy the webhook URL (starts with `https://hooks.slack.com/services/`)
+5. Set it as `SLACK_WEBHOOK` in `.env`
+
+## How to Use
+
+Preview the last 7 days without sending alerts:
+
+```bash
+npm run dry-run:week
+# or
+node scripts/monitor-hn.js --dry-run --days=7
+```
+
+Live run:
+
+```bash
+npm run monitor
+# or
+node scripts/monitor-hn.js
+```
+
+Schedule via cron (every 4 hours):
+
+```bash
+crontab -e
+# Add:
+0 */4 * * * cd /path/to/hackernews-intel && node scripts/monitor-hn.js >> /tmp/hn-intel.log 2>&1
+```
+
+Schedule via GitHub Actions:
+
+```yaml
+name: HN Intel Monitor
+on:
+  schedule:
+    - cron: '0 */4 * * *'
+  workflow_dispatch:
+jobs:
+  monitor:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+      - run: npm install
+      - run: node scripts/monitor-hn.js
+        env:
+          HN_KEYWORDS: ${{ secrets.HN_KEYWORDS }}
+          SLACK_WEBHOOK: ${{ secrets.SLACK_WEBHOOK }}
+```
+
+Add `HN_KEYWORDS` and `SLACK_WEBHOOK` as repository secrets.
+
+## Slack Alert Format
+
+Each alert looks like:
+
+```
+Story Title Here
+47 points  23 comments  authorname
+Keyword: claude code  |  HN discussion
+```
+
+## Options
+
+| Variable | Default | Purpose |
+|----------|---------|---------|
+| `HN_KEYWORDS` | required | Comma-separated keywords |
+| `SLACK_WEBHOOK` | required | Slack Incoming Webhook URL |
+| `HN_MIN_POINTS` | `0` | Minimum points to alert |
+| `HN_INCLUDE_COMMENTS` | `false` | Also monitor HN comments |
+| `HN_DB_PATH` | `./hn-intel.db` | SQLite cache file path |
+
+## CLI Flags
+
+| Flag | Purpose |
+|------|---------|
+| `--dry-run` | Preview matches without sending Slack alerts |
+| `--days=N` | Lookback window for the first run (default: 1) |
+| `--reset` | Clear the cache and start fresh |
+
+## GitHub Actions Note
+
+GitHub Actions does not persist files between workflow runs. The SQLite cache resets on each run, and the script re-fetches the last 1 day of posts every time. Posts from the previous run will be alerted again.
+
+To fix this, either:
+- Store `hn-intel.db` in an S3 bucket and download/upload it around the script run
+- Use a self-hosted runner with persistent storage
+- Use a cron job on your own machine instead
+
+## Project Structure
+
+```
+hackernews-intel/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── package.json
+├── evals/
+│   └── evals.json
+└── scripts/
+    └── monitor-hn.js
+```
+
+## License
+
+MIT

package/skills/human-tone/README.md

@@ -1,4 +1,4 @@
-<img width="1280" height="640" alt="human-tone-skill-cover-image" src="https://github.com/user-attachments/assets/aa2c99dc-87a6-490e-a989-21fd6a2bbc9a" />
+<img width="1280" height="640" alt="human-tone-skill-cover-image" src="https://github.com/user-attachments/assets/aa2c99dc-87a6-490e-a989-21fd6a2bbc9a" />
 
 # Human Tone
 
@@ -30,3 +30,45 @@ https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
 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 Fixes
+
+* Removes words like "streamline", "empower", and "revolutionize".
+* Stops the AI from starting emails with "I hope this finds you well".
+* Forces the AI to replace vague claims with specific numbers and outcomes.
+* Fixes the rigid sentence structures that make AI text obvious.
+
+## Installation
+
+You can install this skill directly into your AI agent environment using the OpenDirectory command line tool.
+
+### Option 1: Quick Install
+
+Run this command in your terminal to install it directly without downloading the whole directory:
+
+```bash
+npx "@opendirectory.dev/skills" install human-tone --target opencode
+```
+
+Note: You can change `--target opencode` to `--target claude` or `--target cursor` depending on which AI assistant you use.
+
+### Option 2: Global Install
+
+If you plan to browse and install multiple skills, you can install the tool globally on your computer:
+
+```bash
+npm install -g @opendirectory.dev/skills
+opendirectory install human-tone --target opencode
+```
+
+## How to Use It
+
+Once the skill is installed in your workspace, simply ask your AI to humanize your copy.
+
+**Basic usage:**
+> "Take this draft for a cold email and run it through the human-tone skill. Make it short and direct."
+
+**Advanced usage (Matching a specific voice):**
+> "Rewrite this landing page copy using the human-tone skill. Match the writing style in this sample: [paste a sample of your writing]."
+
+The AI will rewrite the text, provide a bulleted list of what it changed, and flag any placeholders where you need to insert real numbers or actual customer names.

package/skills/kill-the-standup/README.md

@@ -1,4 +1,4 @@
-# kill-the-standup
+# kill-the-standup
 
 <img width="1280" height="640" alt="kill-the-standup" src="https://github.com/user-attachments/assets/4fcf306d-7ef9-455a-b5f1-02532c292f65" />
 
@@ -28,3 +28,81 @@ https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
 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 yesterday's Linear issues assigned to you (completed and in-progress)
+- Fetches yesterday's GitHub commits from your configured repo
+- Formats a three-section standup: Done, Doing, Blockers
+- Posts to your Slack channel via Incoming Webhook
+
+## Requirements
+
+| Requirement | Purpose | How to Set Up |
+|------------|---------|--------------|
+| Linear API key | Fetching your issues | Linear, Settings, API, Personal API keys |
+| Slack Incoming Webhook | Posting the standup | api.slack.com/apps, Your App, Incoming Webhooks |
+| `gh` CLI (optional) | Fetching GitHub commits | https://cli.github.com, then run `gh auth login` |
+
+No LLM API key needed. The agent reads your activity directly.
+
+## Setup
+
+```bash
+cp .env.example .env
+```
+
+Edit `.env` and fill in:
+- `LINEAR_API_KEY` (required)
+- `SLACK_WEBHOOK_URL` (required)
+- `GITHUB_REPO` (optional, format: `owner/repo`)
+- `GITHUB_USERNAME` (optional, defaults to your gh auth username)
+
+## How to Use
+
+Write and post standup:
+
+```
+"Write my standup"
+"Post my standup to Slack"
+"Generate standup update"
+```
+
+Output only, no Slack post:
+
+```
+"Write my standup but don't post it"
+"What did I do yesterday?"
+"Give me my standup text"
+```
+
+## Output Format
+
+```
+Done
+- [ENG-123] Fix session timeout bug
+- fix: remove duplicate middleware registration
+
+Doing
+- [ENG-124] Migrate auth to OAuth2
+
+Blockers
+No blockers.
+```
+
+## Project Structure
+
+```
+kill-the-standup/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── evals/
+│   └── evals.json
+└── references/
+    └── standup-format.md
+```
+
+## License
+
+MIT

package/skills/linkedin-job-post-to-buyer-pain-map/README.md

@@ -1,4 +1,4 @@
-# linkedin-job-post-to-buyer-pain-map
+# linkedin-job-post-to-buyer-pain-map
 
 <img src="cover.png" width="100%" alt="LinkedIn Job Post to Buyer Pain Map — Signal Decoder for GTM Teams" />
 
@@ -123,7 +123,7 @@ linkedin-job-post-to-buyer-pain-map/
 
 MIT
 
-## Install
+## Installation in Claude Desktop App
 
 ### Video Tutorial
 Watch this quick video to see how it's done:
@@ -141,4 +141,4 @@ https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
 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!
+> **Note:** Always make sure you are uploading the specific folder that contains the `SKILL.md` file!

package/skills/linkedin-post-generator/README.md

@@ -1,4 +1,4 @@
-# linkedin-post-generator
+# linkedin-post-generator
 
 <img width="1376" height="768" alt="LinkedIn_post_generator" src="https://github.com/user-attachments/assets/dc71e06b-8b3c-486a-adbf-d56a7b22cdc1" />
 
@@ -27,3 +27,105 @@ https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
 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!
+
+## Post Styles
+
+| Style | Use When | Example Input |
+|-------|----------|---------------|
+| Founder/Ship | Personal story of building or shipping | "We merged our streaming SDK after 3 weeks" |
+| Insight | Educational observation or lesson | Blog article, pattern you noticed, lesson learned |
+| Product Launch | Announcing a new tool or feature | PR description, launch brief, feature going GA |
+| Tutorial Summary | Distilling a long technical post | Tutorial URL, deep-dive article, step-by-step guide |
+
+The agent auto-detects the right style. You override it by asking for a specific one.
+
+## Requirements
+
+No LLM API key needed. The agent writes the post.
+
+Composio is optional. Add it to post directly to LinkedIn.
+
+## Setup
+
+### Composio (Optional)
+
+Without Composio, the agent outputs formatted text for copy-paste. No configuration needed.
+
+To enable direct posting:
+1. Get your API key at https://app.composio.dev/settings
+2. Connect your LinkedIn account at https://app.composio.dev/app/linkedin
+3. Complete the OAuth flow
+4. Add the key to your .env file:
+
+```bash
+cp .env.example .env
+# Edit .env and add your COMPOSIO_API_KEY
+```
+
+## How to Use
+
+From a URL:
+```
+"Turn this into a LinkedIn post: https://yourblog.com/my-post"
+"Write a LinkedIn post about this article: [URL]"
+```
+
+From pasted text:
+```
+"Here's a case study, turn it into a LinkedIn post: [paste text]"
+"Convert this to a LinkedIn post: [paste article]"
+```
+
+From a PR or shipped feature:
+```
+"Write a LinkedIn post about this PR we merged: [paste PR description]"
+"Announce our new feature on LinkedIn: [describe the feature]"
+```
+
+With a style override:
+```
+"Write a LinkedIn post in Tutorial Summary style about: [topic]"
+"Use the Product Launch style for this: [description]"
+```
+
+With direct posting:
+```
+"Post this to LinkedIn: [paste content]"
+"Generate and post a LinkedIn update about [topic]"
+```
+
+## Output
+
+| Output | Description |
+|--------|-------------|
+| LinkedIn post | Formatted text, 900-1,300 characters, ready to publish |
+| First comment | Text with source links. Post this immediately after publishing. |
+| Hook alternatives | 2 additional hook lines in different formats |
+| Posted confirmation | If Composio is configured and you confirm posting |
+
+## How Posts Are Formatted
+
+Four rules drive every post the agent writes:
+
+- Hook first. The first line is all most people see. It works standalone.
+- Short paragraphs. 1-3 lines, then a blank line. LinkedIn is mobile-first.
+- Links in the first comment. URLs in the post body reduce LinkedIn's distribution.
+- Question or CTA at the end. One or the other, not both.
+
+## Project Structure
+
+```
+linkedin-post-generator/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── evals/
+│   └── evals.json
+└── references/
+    ├── linkedin-format.md
+    └── output-template.md
+```
+
+## License
+
+MIT

package/skills/llms-txt-generator/README.md

@@ -1,4 +1,4 @@
-# llms-txt-generator
+# llms-txt-generator
 
 <img width="1376" height="768" alt="llms-txt-generator" src="https://github.com/user-attachments/assets/7f549d0b-4d55-40a8-97c6-59510cc40b54" />
 
@@ -27,3 +27,140 @@ https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
 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
+
+The skill crawls your website using Chrome DevTools, reads your actual pages, and produces a clean `llms.txt` file in the format specified by [Jeremy Howard's llms.txt standard](https://llmstxt.org). When AI agents (Claude, ChatGPT, Gemini) visit your site, they read `llms.txt` first to understand what you are and where to find authoritative content.
+
+**Without llms.txt:** AI agents guess, hallucinate, or cite competitors instead.  
+**With llms.txt:** AI agents cite your product correctly and know exactly where your docs, blog, and key pages live.
+
+## Two Modes
+
+### Codebase Mode (no Chrome needed)
+If you're inside a website's repo, the skill reads your source files directly pages, routes, blog posts, frontmatter, site config. It writes `llms.txt` straight to `public/` when you approve. No browser required.
+
+Supported frameworks: **Next.js** (pages + app router), **Astro**, **Nuxt**, **Gatsby**, **SvelteKit**, **Hugo**, **Jekyll**
+
+### Live Site Mode (Chrome or fetch fallback)
+If you only have the URL, the skill crawls the live site using Chrome DevTools MCP. Falls back to standard web fetch if Chrome isn't available.
+
+---
+
+## Requirements
+
+**Codebase Mode:** No extra setup. Just be inside the repo directory.
+
+**Live Site Mode:**
+- Chrome with remote debugging enabled (or any live URL skill will fall back to web fetch)
+- Chrome DevTools MCP server configured in your agent (optional, improves JS-rendered sites)
+
+## Setup
+
+### For Live Site Mode: Start Chrome with Remote Debugging
+
+**Mac:**
+```bash
+open -a "Google Chrome" --args --remote-debugging-port=9222
+```
+
+**Linux:**
+```bash
+google-chrome --remote-debugging-port=9222
+```
+
+**Windows:**
+```bash
+chrome.exe --remote-debugging-port=9222
+```
+
+### 2. Install Chrome DevTools MCP Server
+
+Follow the setup at: https://github.com/ChromeDevTools/chrome-devtools-mcp
+
+Add to your agent's MCP configuration:
+```json
+{
+  "mcpServers": {
+    "chrome-devtools": {
+      "command": "npx",
+      "args": ["-y", "@chrome-devtools/mcp-server"],
+      "env": {
+        "CHROME_DEBUGGING_PORT": "9222"
+      }
+    }
+  }
+}
+```
+
+### 3. Configure Environment (Optional)
+
+Copy `.env.example` to `.env` and fill in:
+```bash
+cp .env.example .env
+```
+
+`GITHUB_TOKEN` and `GITHUB_REPO` are only needed if you want the agent to automatically open a GitHub PR with the generated file.
+
+## How to Use
+
+**Codebase Mode** just be inside your project and ask:
+```
+"Generate an llms.txt for this site"
+"Add llms.txt to this project"
+"Make this site readable by AI agents"
+```
+
+The agent will detect your framework, read your pages and blog posts from source, generate `llms.txt`, and write it to the right directory (e.g. `public/llms.txt`) after you confirm.
+
+**Live Site Mode** provide a URL:
+```
+"Generate an llms.txt for https://yoursite.com"
+"Does https://yoursite.com have an llms.txt? If not, create one."
+```
+
+The agent will:
+1. Check if `llms.txt` already exists at the domain
+2. Crawl homepage, docs, blog, about, pricing, and API pages
+3. Generate `llms.txt` following the official spec
+4. Optionally generate `llms-full.txt` with full page content
+5. Save the file locally and give you deployment instructions
+6. Optionally open a GitHub PR if configured
+
+## Where to Deploy the File
+
+Place `llms.txt` at your web root so it's accessible at `https://yourdomain.com/llms.txt`:
+
+| Platform | File Location |
+|----------|--------------|
+| Next.js / Vercel | `/public/llms.txt` |
+| Astro | `/public/llms.txt` |
+| Nuxt | `/public/llms.txt` |
+| GitHub Pages | Repository root |
+| Hugo | `/static/llms.txt` |
+| WordPress | Upload via FTP to web root |
+
+## Output Files
+
+| File | Description |
+|------|-------------|
+| `llms.txt` | Structured link map. LLMs follow links to find content |
+| `llms-full.txt` | Full prose content of key pages. LLMs ingest everything at once |
+
+## Project Structure
+
+```
+llms-txt-generator/
+├── SKILL.md                          # Agent instructions
+├── README.md                         # This file
+├── .env.example                      # Environment variables template
+├── evals/
+│   └── evals.json                    # Test prompts for skill evaluation
+└── references/
+    ├── llms-txt-spec.md              # The llms.txt format specification
+    └── output-template.md            # Exact output template with example
+```
+
+## License
+
+MIT