@opendirectory.dev/skills 0.1.65 → 0.1.66

package/skills/newsletter-digest/README.md

@@ -14,7 +14,7 @@ npx "@opendirectory.dev/skills" install newsletter-digest --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
+https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
 
 ### Step 1: Download the skill from GitHub
 1. Copy the URL of this specific skill folder from your browser's address bar.
@@ -28,3 +28,144 @@ 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
+
+- Reads your RSS/Atom feed list from `feeds.json`
+- Fetches all articles published in the last 7 days (configurable)
+- Deduplicates across feeds and sorts by date
+- Uses Gemini to synthesize a digest in your chosen format
+- Publishes to Ghost as a draft or live post
+- Outputs formatted Markdown for Substack, Notion, or any other platform
+
+## Digest Formats
+
+| Format | Use When | Target Length |
+|--------|----------|---------------|
+| Weekly Roundup | General digest covering top stories across all feeds | 350-500 words |
+| Topic Deep Dive | Focused issue on a single topic (AI, security, etc.) | 450-650 words |
+| Curated Picks | 5 selected articles with editorial context | 250-350 words |
+
+## Requirements
+
+| Requirement | Purpose | Where to Get It |
+|------------|---------|-----------------|
+| GEMINI_API_KEY | Digest synthesis | https://ai.google.dev |
+| GHOST_URL + GHOST_ADMIN_KEY | Ghost publishing (optional) | Ghost Admin, Settings, Integrations |
+| Node.js 20+ | Running scripts | https://nodejs.org |
+
+Tavily is not required. The skill uses article excerpts from RSS feeds directly.
+
+## Setup
+
+### 1. Install dependencies
+
+```bash
+cd /path/to/newsletter-digest
+npm install
+```
+
+### 2. Configure environment variables
+
+```bash
+cp .env.example .env
+# Edit .env with your keys
+```
+
+### 3. Configure your feeds
+
+Edit `feeds.json` with the RSS feeds you want to monitor:
+
+```json
+[
+  { "url": "https://hnrss.org/frontpage", "name": "Hacker News" },
+  { "url": "https://feeds.feedburner.com/TheHackersNews", "name": "The Hacker News" },
+  { "url": "https://changelog.com/feed", "name": "Changelog" }
+]
+```
+
+The file ships with 5 example feeds. Replace them with your own.
+
+### 4. Set up Ghost publishing (optional)
+
+1. Go to Ghost Admin, Settings, Integrations
+2. Click "Add custom integration"
+3. Name it "newsletter-digest"
+4. Copy the Admin API Key (format: `key_id:secret`)
+5. Set `GHOST_ADMIN_KEY=key_id:secret` in `.env`
+6. Set `GHOST_URL=https://your-ghost-site.com` in `.env`
+
+## How to Use
+
+Generate a weekly digest:
+
+```
+"Generate a weekly digest from my RSS feeds"
+"Create this week's newsletter"
+"Summarize my feeds from the last 7 days"
+```
+
+Choose a specific format:
+
+```
+"Create a topic deep dive about AI agents from this week's news"
+"Generate a curated picks digest for this week"
+"Write a weekly roundup newsletter"
+```
+
+Extend the date window:
+
+```
+"Generate a digest from the last 14 days"
+"Not many articles this week, extend the window to 2 weeks"
+```
+
+Publish to Ghost:
+
+```
+"Generate this week's digest and publish it to Ghost as a draft"
+"Create the newsletter and publish it to Ghost"
+```
+
+Output for Substack:
+
+```
+"Generate a newsletter digest for Substack"
+"Create the digest and give me the Markdown version"
+```
+
+## Output
+
+| Output | Description |
+|--------|-------------|
+| HTML | Ready to paste into any CMS |
+| Markdown | For Substack, Notion, Hashnode |
+| Plain text | For email clients |
+| Ghost draft | Published automatically if configured |
+
+## Substack Note
+
+Substack has no public API. The skill outputs a Markdown version of the digest for you to paste directly into the Substack editor.
+
+## Project Structure
+
+```
+newsletter-digest/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── package.json
+├── feeds.json            (your RSS feed list, edit this)
+├── evals/
+│   └── evals.json
+├── references/
+│   ├── digest-format.md  (format rules, length targets, attribution)
+│   └── output-template.md (HTML templates for all 3 formats)
+└── scripts/
+    ├── fetch-feeds.js    (RSS fetching, dedup, date filtering)
+    └── ghost-publish.js  (Ghost Admin API posting)
+```
+
+## License
+
+MIT

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

@@ -79,24 +79,3 @@ Unlike simple text generators, this skill operates as a structured workflow:
 ## Contributing
 
 Pull requests to refine hook patterns, add new slide structures, or include helper scripts that refine raw transcripts are welcome.
-
-
-## Install
-
-### 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!

package/skills/noise2blog/README.md

@@ -14,7 +14,7 @@ npx "@opendirectory.dev/skills" install noise2blog --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
+https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
 
 ### Step 1: Download the skill from GitHub
 1. Copy the URL of this specific skill folder from your browser's address bar.
@@ -28,3 +28,104 @@ 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
+
+- Accepts any rough input: bullet points, rough notes, voice transcripts, tweet dumps, short drafts, or a URL
+- Detects the right blog post style automatically (Technical Tutorial, Case Study, Thought Leadership, Explainer)
+- Enriches claims with Tavily research when you set an API key (supporting data, verification)
+- Generates a Markdown post with no AI slop, no em dashes, no banned words
+- Formats frontmatter for Ghost, dev.to, Substack, or Hashnode on request
+
+## Requirements
+
+| Requirement | Purpose | How to Set Up |
+|------------|---------|--------------|
+| Google Gemini API key | Generates the blog post | aistudio.google.com, Get API key |
+| Tavily API key (optional) | Enriches claims with research | app.tavily.com, API Keys |
+
+No LLM backend to run. The agent calls the Gemini API directly.
+
+## Setup
+
+```bash
+cp .env.example .env
+```
+
+Edit `.env` and fill in:
+- `GEMINI_API_KEY` (required)
+- `TAVILY_API_KEY` (optional, enables research enrichment)
+
+## Blog Post Styles
+
+| Style | Use When | Signals in Your Input |
+|-------|----------|----------------------|
+| Technical Tutorial | Step-by-step guide, code walkthrough | Numbered steps, commands, "how to" |
+| Case Study | Build log, before/after story, lessons learned | Specific results, journey narrative |
+| Thought Leadership | Opinion piece, counterintuitive argument | Strong claim, debate framing |
+| Explainer | Explaining a concept or tool to newcomers | Definition-first, comparisons |
+
+The agent detects the style automatically. Override it with: "Use Thought Leadership style" or "Make this a tutorial".
+
+## How to Use
+
+From pasted notes:
+
+```
+"Write a blog post from these notes: [paste your content]"
+"Turn these bullet points into a blog post"
+"Expand this into an article"
+```
+
+From a voice transcript:
+
+```
+"Turn this transcript into a blog post: [paste transcript]"
+"Clean up this voice note and make it publishable"
+```
+
+From a tweet thread:
+
+```
+"Turn this tweet thread into a blog: [paste tweets]"
+"Expand this thread into a full article"
+```
+
+With style override:
+
+```
+"Write a thought leadership post from these notes"
+"Make this a technical tutorial"
+```
+
+With platform formatting:
+
+```
+"Write the post and format it for dev.to"
+"Give me Ghost frontmatter too"
+```
+
+## Output
+
+- Full blog post in Markdown (800-1,800 words)
+- Meta description (1-2 sentences)
+- Alternative title option
+- Platform-specific frontmatter on request
+
+## Project Structure
+
+```
+noise2blog/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── evals/
+│   └── evals.json
+└── references/
+    ├── blog-format.md
+    └── output-template.md
+```
+
+## License
+
+MIT

package/skills/npm-downloads-to-leads/README.md

@@ -9,19 +9,138 @@ npx "@opendirectory.dev/skills" install npm-downloads-to-leads --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
+https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
 
-### 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 1: Download from GitHub
+1. Click the **Code** button on this repo's GitHub page.
+2. Select **Download ZIP**.
+3. Extract the ZIP on your computer.
 
-### 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).
+### Step 2: Install in Claude
+1. Open the **Claude desktop app**.
+2. Go to **Customize** in the sidebar.
+3. Click the **Skills** tab, then the **+** button.
+4. Choose **Upload a skill** and drop the folder or ZIP file.
 
-> **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: Upload the folder that contains the `SKILL.md` file.
+
+## What It Does
+
+- Fetches 12 weeks of daily download data per package from the npm Downloads API
+- Aggregates to weekly buckets and computes a velocity score: recent growth x acceleration x sweet-spot multiplier
+- Classifies each package as BREAKOUT, WATCHING, steady, established, or too early
+- Fetches maintainer profiles from the npm registry and GitHub API
+- Extracts GitHub followers, Twitter handle, bio, and company from each maintainer's GitHub profile
+- Generates a lead brief per breakout package: growth story, contact signals, why to reach out now, and a suggested first message
+- Saves output to `docs/npm-leads/[date].md`
+
+## Requirements
+
+| Requirement | Purpose | How to Set Up |
+|---|---|---|
+| GitHub token | Raises rate limit from 60/hr to 5000/hr for maintainer profile lookups | github.com/settings/tokens (no scopes needed for public user profiles) |
+
+No external AI API key needed. The npm and npm registry APIs are fully public with no auth. GitHub token is optional but recommended for lists larger than 10 packages.
+
+## Setup
+
+```bash
+cp .env.example .env
+# Add GITHUB_TOKEN (optional, recommended for larger package lists)
+```
+
+## How to Use
+
+```
+"Find leads from these npm packages: esbuild, vite, @hono/hono, zod"
+"Track download trends for competitor packages: turbo, nx, lerna"
+"Who maintains these breakout npm packages? bun, oxc-parser, biome"
+"Find evangelists before they are famous: @effect-ts/core, fp-ts, zod"
+"Analyze npm momentum for my space: my-package, competitor-a, competitor-b"
+"Map npm maintainers to Twitter for these packages: ..."
+```
+
+Include a short description of your product and the skill will tailor the outreach message to your context.
+
+## Why Velocity Score, Not Raw Downloads
+
+React gets 50 million downloads a week. Its maintainers are already famous, already inundated with outreach, and already aligned with a framework you are likely building on.
+
+The velocity score finds the package going from 1K to 8K weekly downloads over 8 weeks. That maintainer just crossed a growth inflection. They are building an audience, they are not yet overwhelmed, and they are in a phase where your product makes a difference to their workflow.
+
+The formula: `velocity_score = growth_ratio x acceleration x sweet_spot_multiplier`
+
+- `growth_ratio`: recent 4-week average divided by prior 4-week average
+- `acceleration`: last 2 weeks vs mid 2 weeks (is growth speeding up?)
+- `sweet_spot_multiplier`: 1.0 for 500 to 500K weekly downloads, lower for noise floor or established giants
+
+Breakout threshold: velocity score above 80 AND 500 to 500K weekly downloads.
+
+## The Lead Brief
+
+For each breakout and watching package:
+
+- **Growth story**: exact download numbers, 8-week comparison, weekly trend
+- **Maintainer profile**: GitHub handle, Twitter, bio, company, follower count
+- **Why reach out now**: specific to this package's growth inflection point
+- **Suggested first message**: names the package, its growth, and connects to your product context
+
+## Cost Per Run
+
+- npm Downloads API: free, no auth, no rate limit concerns
+- npm Registry API: free, no auth
+- GitHub API: free (60 req/hr unauthenticated, 5000/hr with token)
+- AI analysis: uses the model already running the skill; no additional cost
+- Total: free
+
+## Standalone Script
+
+Run the data fetching step directly from the terminal without Claude. Useful for scheduled jobs, CI pipelines, or exploring data before generating lead briefs.
+
+```bash
+# Basic usage
+python3 scripts/fetch.py esbuild zod @hono/hono
+
+# With product context
+python3 scripts/fetch.py esbuild zod --context "We build a TypeScript DX platform"
+
+# From a file (one package per line)
+python3 scripts/fetch.py --file packages.txt --output results.json
+
+# Print to stdout
+python3 scripts/fetch.py esbuild zod --stdout | jq '.summary'
+```
+
+The script handles Steps 3 to 5 (download fetch, velocity scoring, maintainer enrichment) and writes a JSON file. Open that file with Claude and ask: "Generate lead briefs from this npm data."
+
+```bash
+GITHUB_TOKEN=your_token python3 scripts/fetch.py esbuild zod @hono/hono
+```
+
+Script output fields per package:
+
+- `velocity_score`, `growth_pct`, `recent_4_avg`, `prior_4_avg`, `tier`
+- `weeks`: array of 12 weekly download counts, oldest to newest
+- `profile.description`, `profile.keywords`, `profile.npm_maintainers`
+- `profile.github_users`: array with `username`, `twitter_username`, `followers`, `bio`, `company`
+
+## Project Structure
+
+```
+npm-downloads-to-leads/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── scripts/
+│   └── fetch.py           standalone data fetcher (Steps 3 to 5, no Claude needed)
+├── evals/
+│   └── evals.json
+└── references/
+    ├── velocity-scoring.md
+    └── outreach-timing.md
+```
+
+## License
+
+MIT

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

@@ -25,24 +25,3 @@ Unlike single-channel generators, `oss-launch-kit` acts as the **Root Strategy L
 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.
-
-
-## Install
-
-### 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!

package/skills/outreach-sequence-builder/README.md

@@ -14,7 +14,7 @@ npx "@opendirectory.dev/skills" install outreach-sequence-builder --target claud
 ### Video Tutorial
 Watch this quick video to see how it's done:
 
-https://github.com/user-attachments/assets/cea8b565-2002-4a87-8857-d902bfcfdc1c
+https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
 
 ### Step 1: Download the skill from GitHub
 1. Copy the URL of this specific skill folder from your browser's address bar.
@@ -28,3 +28,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!
+
+## What It Does
+
+- Identifies the signal type from 7 categories: Post-Fundraise, Hiring Signal, Competitor Displacement, Product Launch, Content Engagement, Event Follow-up, Job Change
+- Loads your ICP from docs/icp.md or asks 4 questions to define target persona and pain points
+- Develops the Insight, Bridge, Opener, and Ask for the specific signal
+- Plans a 4-6 touchpoint channel sequence over 10-14 days
+- Generates all messages with Gemini, enforcing hard limits (100-word emails, 300-character LinkedIn notes, 20-word phone openers)
+- Pre-empts 2-4 objections woven into existing touchpoints
+- Runs a 13-point QA pass before presenting the sequence
+- Saves the sequence to docs/sequences/ and optionally drafts emails in Gmail via Composio
+
+## Requirements
+
+| Requirement | Purpose | How to Set Up |
+|------------|---------|--------------|
+| Gemini API key | Sequence generation | aistudio.google.com, Get API key |
+| Composio API key (optional) | Gmail draft creation | app.composio.dev, API Keys |
+
+## Setup
+
+```bash
+cp .env.example .env
+```
+
+Fill in:
+- `GEMINI_API_KEY` (required)
+- `COMPOSIO_API_KEY` (optional, for Gmail draft creation)
+
+Optional: create `docs/icp.md` with your target personas, company profile, pain points, and differentiators. If the file does not exist, the skill asks 4 questions before generating.
+
+## How to Use
+
+Basic sequence from a signal:
+
+```
+"Build an outreach sequence for a prospect who just raised a Series B"
+"They're hiring 8 engineers — write me a sequence"
+"Create outreach based on this signal: they just launched a new product"
+```
+
+With contact context:
+
+```
+"Build an outreach sequence for Sarah Chen, VP Sales at Momentum CRM — they just raised $22M Series B"
+"They switched from Salesforce and posted a frustrated LinkedIn comment. Write a competitor displacement sequence."
+```
+
+With Gmail drafting:
+
+```
+"Build a post-fundraise sequence and draft the emails in Gmail"
+```
+
+## Signal Types
+
+| Signal | Definition | Window |
+|--------|-----------|--------|
+| Post-Fundraise | Company raised a round in the last 30 days | 48 hours from announcement |
+| Hiring Signal | Company posted 5 or more roles in a function you serve | Within the week posts appear |
+| Competitor Displacement | Contact is using a competitor and showing frustration | Within 24 hours |
+| Product Launch | Company launched a new product or major feature | 2-4 weeks after launch |
+| Content Engagement | Contact liked, commented, or shared your content | Start on LinkedIn first |
+| Event Follow-up | You met at a conference or webinar | Within 48 hours of event |
+| Job Change | Contact moved to a new company in the last 60 days | Within 2 weeks of announcement |
+
+## Message Rules
+
+- Only `{{first_name}}` is allowed as a variable. All other details must be filled in from context.
+- Email bodies: 100 words maximum.
+- LinkedIn notes: 300 characters maximum.
+- Phone openers: 20 words maximum.
+- No placeholders like `[Company Name]` or `[INSERT PAIN POINT]`. If the information is not available, the skill asks before writing.
+
+## Output
+
+The sequence is saved to `docs/sequences/{signal-type}.md`. Each touchpoint includes:
+
+- Channel and day number
+- Two subject line variants (email)
+- Message body
+- Word count (email) or character count (LinkedIn)
+- Phone talk track with voicemail script
+
+## Project Structure
+
+```
+outreach-sequence-builder/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── evals/
+│   └── evals.json
+└── references/
+    ├── signal-playbook.md
+    ├── sequence-format.md
+    └── output-template.md
+```
+
+## License
+
+MIT

package/skills/position-me/README.md

@@ -15,7 +15,7 @@ npx "@opendirectory.dev/skills" install position-me --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
+https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
 
 ### Step 1: Download the skill from GitHub
 1. Copy the URL of this specific skill folder from your browser's address bar.
@@ -29,3 +29,67 @@ 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!
+
+## Core Capabilities
+
+When invoked, the skill commands the AI agent to conduct an exhaustive teardown of the target website through a rigid protocol:
+
+* Autonomous Navigation: Crawl the homepage, about, pricing, and blog pages.
+* Visual Psychology: Take full page screenshots and analyze visual friction, layout flow, and cognitive load using the LIFT model.
+* Copywriting Critique: Rewrite generic text using the PAS (Problem, Agitation, Solution) framework.
+* Deep Content Audits: Read actual blog posts to identify fluff, grade technical depth, and offer new content strategies.
+* Technical Readiness: Verify the presence of llms.txt, sitemap.xml, and semantic JSON-LD Schema (FAQPage, SoftwareApplication, etc) for generative search optimization.
+
+## Requirements
+
+The host AI agent must have access to:
+1. A multimodal LLM capable of analyzing screenshots natively.
+2. Chrome DevTools MCP Server (https://github.com/ChromeDevTools/chrome-devtools-mcp).
+3. Chrome CDP Skill (https://github.com/pasky/chrome-cdp-skill).
+4. Terminal access to run fallback Python scripts if browser automation fails.
+
+To set up the required Chrome automation:
+* Install and configure the Chrome DevTools MCP server in the agent MCP settings.
+* Add the Chrome CDP skill to the agent skills directory.
+* Ensure Chrome is running with remote debugging enabled (e.g., `chrome --remote-debugging-port=9222`).
+
+## Installation Instructions
+
+### For Developers (Manual Setup)
+
+1. Clone or download the `position-me` repository.
+2. Copy the `position-me/` directory into the agent designated skills directory.
+3. Alternatively, extract the raw `SKILL.md` and `references/` folder into the agent custom prompt configuration.
+
+### For AI Agents (Automated Setup)
+
+1. Clone or download the `position-me` repository into the active project workspace.
+2. Read directly from the `position-me/` source folder.
+3. Add the `SKILL.md` file to the active context window or skill registry.
+4. Verify access to the `references/EVALUATION_SOP.md` and `references/REPORT_TEMPLATE.md` files.
+
+## Execution Protocol for Agents
+
+Once loaded, the AI agent must strictly follow this execution loop:
+
+1. Data Gathering: Prompt the user for the target URL.
+2. Connect to Browser: Use the Chrome DevTools MCP combined with the Chrome CDP skill.
+3. Multi-Page Crawl: Navigate to the homepage, pricing page, about page, and at least one blog post.
+4. Capture Vision Context: Take screenshots of every visited page and load them into memory.
+5. Extract DOM Context: Pull the accessibility tree, search for `llms.txt`, and verify JSON-LD schemas.
+6. Analyze: Apply the frameworks specified in `references/EVALUATION_SOP.md`.
+7. Report: Generate a scored, highly structured teardown using exactly the format in `references/REPORT_TEMPLATE.md`.
+
+## Project Structure
+
+```text
+position-me/
+├── README.md                        # Documentation
+└── position-me/                     # Raw skill source code
+    ├── SKILL.md                     # Master protocol
+    ├── scripts/
+    │   └── extract_links.py         # Fallback crawler script
+    └── references/
+        ├── EVALUATION_SOP.md        # Evaluation frameworks
+        └── REPORT_TEMPLATE.md       # Teardown report template
+```