@oriro/orirocli 0.1.11 → 0.1.12

package/skills/craft/uipm-ui-ux-pro-max/templates/platforms/roocode.json

@@ -1,21 +1,21 @@
-{
-  "platform": "roocode",
-  "displayName": "Roo Code",
-  "installType": "full",
-  "folderStructure": {
-    "root": ".roo",
-    "skillPath": "skills/ui-ux-pro-max",
-    "filename": "SKILL.md"
-  },
-  "scriptPath": "skills/ui-ux-pro-max/scripts/search.py",
-  "frontmatter": {
-    "name": "ui-ux-pro-max",
-    "description": "Comprehensive design guide for web and mobile applications. Contains 67 styles, 161 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 16 technology stacks."
-  },
-  "sections": {
-    "quickReference": false
-  },
-  "title": "ui-ux-pro-max",
-  "description": "Comprehensive design guide for web and mobile applications. Contains 67 styles, 161 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 16 technology stacks. Searchable database with priority-based recommendations.",
-  "skillOrWorkflow": "Workflow"
-}
+{
+  "platform": "roocode",
+  "displayName": "Roo Code",
+  "installType": "full",
+  "folderStructure": {
+    "root": ".roo",
+    "skillPath": "skills/ui-ux-pro-max",
+    "filename": "SKILL.md"
+  },
+  "scriptPath": "skills/ui-ux-pro-max/scripts/search.py",
+  "frontmatter": {
+    "name": "ui-ux-pro-max",
+    "description": "Comprehensive design guide for web and mobile applications. Contains 67 styles, 161 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 16 technology stacks."
+  },
+  "sections": {
+    "quickReference": false
+  },
+  "title": "ui-ux-pro-max",
+  "description": "Comprehensive design guide for web and mobile applications. Contains 67 styles, 161 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 16 technology stacks. Searchable database with priority-based recommendations.",
+  "skillOrWorkflow": "Workflow"
+}

package/skills/craft/uipm-ui-ux-pro-max/templates/platforms/trae.json

@@ -1,21 +1,21 @@
-{
-  "platform": "trae",
-  "displayName": "Trae",
-  "installType": "full",
-  "folderStructure": {
-    "root": ".trae",
-    "skillPath": "skills/ui-ux-pro-max",
-    "filename": "SKILL.md"
-  },
-  "scriptPath": "skills/ui-ux-pro-max/scripts/search.py",
-  "frontmatter": {
-    "name": "ui-ux-pro-max",
-    "description": "UI/UX design intelligence with searchable database"
-  },
-  "sections": {
-    "quickReference": false
-  },
-  "title": "ui-ux-pro-max",
-  "description": "Comprehensive design guide for web and mobile applications. Contains 67 styles, 161 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 16 technology stacks. Searchable database with priority-based recommendations.",
-  "skillOrWorkflow": "Skill"
-}
+{
+  "platform": "trae",
+  "displayName": "Trae",
+  "installType": "full",
+  "folderStructure": {
+    "root": ".trae",
+    "skillPath": "skills/ui-ux-pro-max",
+    "filename": "SKILL.md"
+  },
+  "scriptPath": "skills/ui-ux-pro-max/scripts/search.py",
+  "frontmatter": {
+    "name": "ui-ux-pro-max",
+    "description": "UI/UX design intelligence with searchable database"
+  },
+  "sections": {
+    "quickReference": false
+  },
+  "title": "ui-ux-pro-max",
+  "description": "Comprehensive design guide for web and mobile applications. Contains 67 styles, 161 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 16 technology stacks. Searchable database with priority-based recommendations.",
+  "skillOrWorkflow": "Skill"
+}

package/skills/craft/uipm-ui-ux-pro-max/templates/platforms/warp.json

@@ -1,18 +1,18 @@
-{
-  "platform": "warp",
-  "displayName": "Warp",
-  "installType": "full",
-  "folderStructure": {
-    "root": ".warp",
-    "skillPath": "skills/ui-ux-pro-max",
-    "filename": "SKILL.md"
-  },
-  "scriptPath": "skills/ui-ux-pro-max/scripts/search.py",
-  "frontmatter": null,
-  "sections": {
-    "quickReference": false
-  },
-  "title": "ui-ux-pro-max",
-  "description": "Comprehensive design guide for web and mobile applications. Contains 67 styles, 161 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 16 technology stacks. Searchable database with priority-based recommendations.",
-  "skillOrWorkflow": "Skill"
-}
+{
+  "platform": "warp",
+  "displayName": "Warp",
+  "installType": "full",
+  "folderStructure": {
+    "root": ".warp",
+    "skillPath": "skills/ui-ux-pro-max",
+    "filename": "SKILL.md"
+  },
+  "scriptPath": "skills/ui-ux-pro-max/scripts/search.py",
+  "frontmatter": null,
+  "sections": {
+    "quickReference": false
+  },
+  "title": "ui-ux-pro-max",
+  "description": "Comprehensive design guide for web and mobile applications. Contains 67 styles, 161 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 16 technology stacks. Searchable database with priority-based recommendations.",
+  "skillOrWorkflow": "Skill"
+}

package/skills/craft/uipm-ui-ux-pro-max/templates/platforms/windsurf.json

@@ -1,21 +1,21 @@
-{
-  "platform": "windsurf",
-  "displayName": "Windsurf",
-  "installType": "full",
-  "folderStructure": {
-    "root": ".windsurf",
-    "skillPath": "skills/ui-ux-pro-max",
-    "filename": "SKILL.md"
-  },
-  "scriptPath": "skills/ui-ux-pro-max/scripts/search.py",
-  "frontmatter": {
-    "name": "ui-ux-pro-max",
-    "description": "Comprehensive design guide for web and mobile applications. Contains 67 styles, 161 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 16 technology stacks."
-  },
-  "sections": {
-    "quickReference": false
-  },
-  "title": "ui-ux-pro-max",
-  "description": "Comprehensive design guide for web and mobile applications. Contains 67 styles, 161 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 16 technology stacks. Searchable database with priority-based recommendations.",
-  "skillOrWorkflow": "Skill"
-}
+{
+  "platform": "windsurf",
+  "displayName": "Windsurf",
+  "installType": "full",
+  "folderStructure": {
+    "root": ".windsurf",
+    "skillPath": "skills/ui-ux-pro-max",
+    "filename": "SKILL.md"
+  },
+  "scriptPath": "skills/ui-ux-pro-max/scripts/search.py",
+  "frontmatter": {
+    "name": "ui-ux-pro-max",
+    "description": "Comprehensive design guide for web and mobile applications. Contains 67 styles, 161 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 16 technology stacks."
+  },
+  "sections": {
+    "quickReference": false
+  },
+  "title": "ui-ux-pro-max",
+  "description": "Comprehensive design guide for web and mobile applications. Contains 67 styles, 161 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 16 technology stacks. Searchable database with priority-based recommendations.",
+  "skillOrWorkflow": "Skill"
+}

package/skills/craft/vercel-optimize/AGENTS.md

@@ -1,48 +1,48 @@
-# vercel-optimize
-
-Cross-agent entry point for the Vercel Optimize skill. The full procedure is in [SKILL.md](./SKILL.md).
-
-Use this skill when the user asks to optimize a Vercel project, reduce a Vercel bill, investigate slow or expensive routes, find caching opportunities, reduce function invocations, or produce a Vercel cost/performance report.
-
-Do not use it for projects that are not deployed on Vercel, greenfield projects with no traffic, or general code review.
-
-## Requirements
-
-- Node.js 20+
-- Vercel CLI with `vercel metrics`, `vercel usage`, `vercel contract`, and `vercel api` support; v53+ is this skill's compatibility floor
-- Authenticated Vercel CLI session
-- Linked Vercel project directory (`vercel link`) for route metrics. `VERCEL_PROJECT_ID` can help resolve project config, but it does not replace directory linkage for `vercel metrics`. The project must resolve to a CLI-safe team or personal scope so `vercel metrics`, `vercel usage`, and `vercel contract` all run against the same account.
-- Observability Plus for per-route metric analysis
-
-## Procedure
-
-1. Read [SKILL.md](./SKILL.md).
-2. Collect Vercel signals before reading source files.
-3. Gate candidates with deterministic scripts.
-4. Investigate only files named by launched candidates.
-5. Verify recommendations mechanically before rendering the report.
-
-The hard rules are in [references/doctrine.md](./references/doctrine.md): observability first, deterministic gates, candidate-bound scope, and version-aware citations.
-
-## Install
-
-Preferred:
-
-```bash
-npx skills add vercel-labs/agent-skills --skill vercel-optimize
-```
-
-Manual project install:
-
-```bash
-mkdir -p .agents/skills
-cp -R <agent-skills-repo>/skills/vercel-optimize .agents/skills/
-```
-
-Then add this to the project `AGENTS.md`:
-
-```md
-When optimizing Vercel cost or performance, follow
-`.agents/skills/vercel-optimize/SKILL.md` before proposing changes.
-Collect Vercel metrics before reading source files.
-```
+# vercel-optimize
+
+Cross-agent entry point for the Vercel Optimize skill. The full procedure is in [SKILL.md](./SKILL.md).
+
+Use this skill when the user asks to optimize a Vercel project, reduce a Vercel bill, investigate slow or expensive routes, find caching opportunities, reduce function invocations, or produce a Vercel cost/performance report.
+
+Do not use it for projects that are not deployed on Vercel, greenfield projects with no traffic, or general code review.
+
+## Requirements
+
+- Node.js 20+
+- Vercel CLI with `vercel metrics`, `vercel usage`, `vercel contract`, and `vercel api` support; v53+ is this skill's compatibility floor
+- Authenticated Vercel CLI session
+- Linked Vercel project directory (`vercel link`) for route metrics. `VERCEL_PROJECT_ID` can help resolve project config, but it does not replace directory linkage for `vercel metrics`. The project must resolve to a CLI-safe team or personal scope so `vercel metrics`, `vercel usage`, and `vercel contract` all run against the same account.
+- Observability Plus for per-route metric analysis
+
+## Procedure
+
+1. Read [SKILL.md](./SKILL.md).
+2. Collect Vercel signals before reading source files.
+3. Gate candidates with deterministic scripts.
+4. Investigate only files named by launched candidates.
+5. Verify recommendations mechanically before rendering the report.
+
+The hard rules are in [references/doctrine.md](./references/doctrine.md): observability first, deterministic gates, candidate-bound scope, and version-aware citations.
+
+## Install
+
+Preferred:
+
+```bash
+npx skills add vercel-labs/agent-skills --skill vercel-optimize
+```
+
+Manual project install:
+
+```bash
+mkdir -p .agents/skills
+cp -R <agent-skills-repo>/skills/vercel-optimize .agents/skills/
+```
+
+Then add this to the project `AGENTS.md`:
+
+```md
+When optimizing Vercel cost or performance, follow
+`.agents/skills/vercel-optimize/SKILL.md` before proposing changes.
+Collect Vercel metrics before reading source files.
+```

package/skills/craft/vercel-optimize/CONTRIBUTING.md

@@ -1,41 +1,41 @@
-# Contributing to `vercel-optimize`
-
-Keep changes small, metric-grounded, and fixture-tested. Runtime code lives in `skills/vercel-optimize`; tests and fixtures live in `packages/vercel-optimize-tests` so installed skills stay small.
-
-## Common changes
-
-| Change               | Edit                                                                                | Test                                                                                                                                       |
-| -------------------- | ----------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
-| Gate                 | `lib/gates/<id>.mjs`, `lib/gates/index.mjs`                                         | `node --test packages/vercel-optimize-tests/test/*gate*.test.mjs`                                                                          |
-| Scanner              | `lib/scanners/<id>.mjs`, `lib/scanners/index.mjs`                                   | Scanner-specific test in `packages/vercel-optimize-tests/test/`                                                                            |
-| Citation             | `references/docs-library.json`                                                      | `node skills/vercel-optimize/scripts/check-citations.mjs`                                                                                  |
-| Support topic        | `references/support-topics/<id>.md`                                                 | `node --test packages/vercel-optimize-tests/test/support-topics.test.mjs`                                                                  |
-| Playbook             | `references/playbooks/<profile>.md` and selection matrix in `references/scoring.md` | `node --test packages/vercel-optimize-tests/test/support-topics.test.mjs packages/vercel-optimize-tests/test/investigation-brief.test.mjs` |
-| Renderer or verifier | `lib/render-report.mjs`, `lib/verify-claim.mjs`, or related module                  | Focused test plus full test suite                                                                                                          |
-
-Generated docs:
-
-```bash
-node skills/vercel-optimize/scripts/build-docs.mjs
-node skills/vercel-optimize/scripts/check-docs-fresh.mjs
-```
-
-Full test loop:
-
-```bash
-node --test packages/vercel-optimize-tests/test/*.test.mjs
-node skills/vercel-optimize/scripts/check-docs-fresh.mjs
-node skills/vercel-optimize/scripts/check-citations.mjs
-```
-
-## Rules
-
-- No runtime dependencies. Scripts use Node.js 20+ built-ins and the Vercel CLI.
-- No recommendation without a Vercel metric signal, code evidence when code changes are proposed, and an allow-listed citation.
-- No invented URLs, exact savings projections, or version-mismatched framework APIs.
-- No internal repo paths, service names, customer names, or captured private output in fixtures.
-- Keep generated report copy customer-facing. Put debug details behind `--debug-out`.
-
-## Output contracts
-
-Every JSON-emitting script must be deterministic: stable key order, stable sort order, 2-space indentation, trailing newline. If a consumed schema changes, update the schema version and the fixture tests in the same PR.
+# Contributing to `vercel-optimize`
+
+Keep changes small, metric-grounded, and fixture-tested. Runtime code lives in `skills/vercel-optimize`; tests and fixtures live in `packages/vercel-optimize-tests` so installed skills stay small.
+
+## Common changes
+
+| Change               | Edit                                                                                | Test                                                                                                                                       |
+| -------------------- | ----------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
+| Gate                 | `lib/gates/<id>.mjs`, `lib/gates/index.mjs`                                         | `node --test packages/vercel-optimize-tests/test/*gate*.test.mjs`                                                                          |
+| Scanner              | `lib/scanners/<id>.mjs`, `lib/scanners/index.mjs`                                   | Scanner-specific test in `packages/vercel-optimize-tests/test/`                                                                            |
+| Citation             | `references/docs-library.json`                                                      | `node skills/vercel-optimize/scripts/check-citations.mjs`                                                                                  |
+| Support topic        | `references/support-topics/<id>.md`                                                 | `node --test packages/vercel-optimize-tests/test/support-topics.test.mjs`                                                                  |
+| Playbook             | `references/playbooks/<profile>.md` and selection matrix in `references/scoring.md` | `node --test packages/vercel-optimize-tests/test/support-topics.test.mjs packages/vercel-optimize-tests/test/investigation-brief.test.mjs` |
+| Renderer or verifier | `lib/render-report.mjs`, `lib/verify-claim.mjs`, or related module                  | Focused test plus full test suite                                                                                                          |
+
+Generated docs:
+
+```bash
+node skills/vercel-optimize/scripts/build-docs.mjs
+node skills/vercel-optimize/scripts/check-docs-fresh.mjs
+```
+
+Full test loop:
+
+```bash
+node --test packages/vercel-optimize-tests/test/*.test.mjs
+node skills/vercel-optimize/scripts/check-docs-fresh.mjs
+node skills/vercel-optimize/scripts/check-citations.mjs
+```
+
+## Rules
+
+- No runtime dependencies. Scripts use Node.js 20+ built-ins and the Vercel CLI.
+- No recommendation without a Vercel metric signal, code evidence when code changes are proposed, and an allow-listed citation.
+- No invented URLs, exact savings projections, or version-mismatched framework APIs.
+- No internal repo paths, service names, customer names, or captured private output in fixtures.
+- Keep generated report copy customer-facing. Put debug details behind `--debug-out`.
+
+## Output contracts
+
+Every JSON-emitting script must be deterministic: stable key order, stable sort order, 2-space indentation, trailing newline. If a consumed schema changes, update the schema version and the fixture tests in the same PR.

package/skills/craft/vercel-optimize/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 ORIRO.ai
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2026 ORIRO.ai
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/craft/vercel-optimize/README.md

@@ -1,91 +1,91 @@
-# vercel-optimize
-
-Optimize cost and performance for supported projects on Vercel.
-
-This skill uses Vercel metrics to find high-impact improvements in your app. Every recommendation is backed by observed data, scoped code evidence, and version-aware docs.
-
-[![skills.sh](https://skills.sh/b/vercel-labs/agent-skills)](https://skills.sh/vercel-labs/agent-skills)
-
-## Install
-
-Install just this skill:
-
-```bash
-npx skills add vercel-labs/agent-skills --skill vercel-optimize
-```
-
-Manual install: copy `skills/vercel-optimize` into `.agents/skills/vercel-optimize` and reference `SKILL.md` from your project `AGENTS.md`.
-
-## Requirements
-
-- Node.js 20+
-- Vercel CLI with `vercel metrics`, `vercel usage`, `vercel contract`, and `vercel api` support (`npm i -g vercel@latest`). The skill enforces v53+ as its compatibility floor.
-- Authenticated Vercel CLI session (`vercel login`)
-- Linked Vercel project directory (`vercel link`) for route metrics. `VERCEL_PROJECT_ID` can resolve project config, but it does not replace directory linkage for `vercel metrics`. The project must resolve to a CLI-safe team or personal scope so `vercel metrics`, `vercel usage`, and `vercel contract` all run against the same account.
-- Observability Plus for metric-backed route ranking
-- Code-backed recommendation coverage is strongest for Next.js and SvelteKit, supported for Nuxt route mapping with generic checks, and limited for Astro. Hono, Remix, and unknown frameworks pause up front.
-
-If route-level metrics are unavailable, the skill pauses before scanner-only mode. Scanner-only can catch traffic-independent code issues, but it cannot rank hot routes or prove cost impact.
-
-## Use
-
-From the Vercel project directory, ask your coding agent:
-
-```text
-optimize this Vercel project
-```
-
-The agent should collect metrics first. If it starts by reading source files or guessing from `vercel.json`, the skill was not loaded correctly.
-
-## Roadmap
-
-| Attribute                                                                                         | Status    |
-| ------------------------------------------------------------------------------------------------- | --------- |
-| Route-level Vercel Function invocations, duration, TTFB, and cold starts                          | Supported |
-| Vercel Function CPU, memory, and GB-hours                                                         | Supported |
-| Request volume, cache hit rate, HTTP status, and method distribution                              | Supported |
-| Fast Data Transfer and bot traffic patterns                                                       | Supported |
-| ISR reads, writes, and over-revalidation                                                          | Supported |
-| Routing Middleware volume and duration                                                            | Supported |
-| External API latency, volume, and transfer bytes                                                  | Supported |
-| Core Web Vitals from Speed Insights                                                               | Supported |
-| Image Optimization usage, source hosts, and source bytes                                          | Supported |
-| Build Minutes fan-out                                                                             | Supported |
-| Usage spikes by billing service                                                                   | Supported |
-| Bot Protection and BotID configuration                                                            | Supported |
-| Fluid Compute configuration and compute signals                                                   | Supported |
-| Region pinning and project configuration mismatches                                               | Supported |
-| Observability Events cost attribution                                                             | Supported |
-| Route-to-file recommendations for Next.js and SvelteKit                                           | Supported |
-| Nuxt route mapping with generic/platform checks                                                   | Supported |
-| Generic route mapping and platform checks for Astro                                               | Supported |
-| Hono route-to-file mapping                                                                        | Planned   |
-| Remix route-to-file mapping                                                                       | Planned   |
-| AI Gateway usage and cost optimization                                                            | Planned   |
-| Sandbox usage and cost optimization                                                               | Planned   |
-| Blob, Edge Config, Runtime Cache, Workflows, Queues, Flags, and Microfrontends billing dimensions | Planned   |
-
-## What You Get
-
-- Ranked recommendations tied to observed Vercel metrics
-- Specific route and file references when source changes are justified
-- Before/after code for ready recommendations
-- Citations from a curated, version-aware documentation allow-list
-- Held-back findings when evidence is real but not strong enough for a recommendation
-- A concise final message plus a full Markdown report
-
-## Trust Model
-
-- Metrics come first. Code investigation starts only after signals are collected.
-- Gates are deterministic JavaScript thresholds. No LLM decides whether a metric qualifies.
-- Citations are allow-listed. Unknown URLs and version-mismatched framework docs are stripped.
-- Project config contradictions are rejected. For example, the verifier blocks "enable Fluid Compute" when Fluid Compute is already on.
-- Cost impact uses magnitude framing, not invented exact savings.
-
-## Contributing
-
-See [CONTRIBUTING.md](./CONTRIBUTING.md). New gates, scanners, playbooks, citations, and sanitizers need fixture coverage in `packages/vercel-optimize-tests`.
-
-## License
-
-MIT
+# vercel-optimize
+
+Optimize cost and performance for supported projects on Vercel.
+
+This skill uses Vercel metrics to find high-impact improvements in your app. Every recommendation is backed by observed data, scoped code evidence, and version-aware docs.
+
+[![skills.sh](https://skills.sh/b/vercel-labs/agent-skills)](https://skills.sh/vercel-labs/agent-skills)
+
+## Install
+
+Install just this skill:
+
+```bash
+npx skills add vercel-labs/agent-skills --skill vercel-optimize
+```
+
+Manual install: copy `skills/vercel-optimize` into `.agents/skills/vercel-optimize` and reference `SKILL.md` from your project `AGENTS.md`.
+
+## Requirements
+
+- Node.js 20+
+- Vercel CLI with `vercel metrics`, `vercel usage`, `vercel contract`, and `vercel api` support (`npm i -g vercel@latest`). The skill enforces v53+ as its compatibility floor.
+- Authenticated Vercel CLI session (`vercel login`)
+- Linked Vercel project directory (`vercel link`) for route metrics. `VERCEL_PROJECT_ID` can resolve project config, but it does not replace directory linkage for `vercel metrics`. The project must resolve to a CLI-safe team or personal scope so `vercel metrics`, `vercel usage`, and `vercel contract` all run against the same account.
+- Observability Plus for metric-backed route ranking
+- Code-backed recommendation coverage is strongest for Next.js and SvelteKit, supported for Nuxt route mapping with generic checks, and limited for Astro. Hono, Remix, and unknown frameworks pause up front.
+
+If route-level metrics are unavailable, the skill pauses before scanner-only mode. Scanner-only can catch traffic-independent code issues, but it cannot rank hot routes or prove cost impact.
+
+## Use
+
+From the Vercel project directory, ask your coding agent:
+
+```text
+optimize this Vercel project
+```
+
+The agent should collect metrics first. If it starts by reading source files or guessing from `vercel.json`, the skill was not loaded correctly.
+
+## Roadmap
+
+| Attribute                                                                                         | Status    |
+| ------------------------------------------------------------------------------------------------- | --------- |
+| Route-level Vercel Function invocations, duration, TTFB, and cold starts                          | Supported |
+| Vercel Function CPU, memory, and GB-hours                                                         | Supported |
+| Request volume, cache hit rate, HTTP status, and method distribution                              | Supported |
+| Fast Data Transfer and bot traffic patterns                                                       | Supported |
+| ISR reads, writes, and over-revalidation                                                          | Supported |
+| Routing Middleware volume and duration                                                            | Supported |
+| External API latency, volume, and transfer bytes                                                  | Supported |
+| Core Web Vitals from Speed Insights                                                               | Supported |
+| Image Optimization usage, source hosts, and source bytes                                          | Supported |
+| Build Minutes fan-out                                                                             | Supported |
+| Usage spikes by billing service                                                                   | Supported |
+| Bot Protection and BotID configuration                                                            | Supported |
+| Fluid Compute configuration and compute signals                                                   | Supported |
+| Region pinning and project configuration mismatches                                               | Supported |
+| Observability Events cost attribution                                                             | Supported |
+| Route-to-file recommendations for Next.js and SvelteKit                                           | Supported |
+| Nuxt route mapping with generic/platform checks                                                   | Supported |
+| Generic route mapping and platform checks for Astro                                               | Supported |
+| Hono route-to-file mapping                                                                        | Planned   |
+| Remix route-to-file mapping                                                                       | Planned   |
+| AI Gateway usage and cost optimization                                                            | Planned   |
+| Sandbox usage and cost optimization                                                               | Planned   |
+| Blob, Edge Config, Runtime Cache, Workflows, Queues, Flags, and Microfrontends billing dimensions | Planned   |
+
+## What You Get
+
+- Ranked recommendations tied to observed Vercel metrics
+- Specific route and file references when source changes are justified
+- Before/after code for ready recommendations
+- Citations from a curated, version-aware documentation allow-list
+- Held-back findings when evidence is real but not strong enough for a recommendation
+- A concise final message plus a full Markdown report
+
+## Trust Model
+
+- Metrics come first. Code investigation starts only after signals are collected.
+- Gates are deterministic JavaScript thresholds. No LLM decides whether a metric qualifies.
+- Citations are allow-listed. Unknown URLs and version-mismatched framework docs are stripped.
+- Project config contradictions are rejected. For example, the verifier blocks "enable Fluid Compute" when Fluid Compute is already on.
+- Cost impact uses magnitude framing, not invented exact savings.
+
+## Contributing
+
+See [CONTRIBUTING.md](./CONTRIBUTING.md). New gates, scanners, playbooks, citations, and sanitizers need fixture coverage in `packages/vercel-optimize-tests`.
+
+## License
+
+MIT