npm - opencode-skills-collection - Versions diffs - 4.0.64 → 4.0.66 - Mend

opencode-skills-collection 4.0.64 → 4.0.66

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (25) hide show

package/bundled-skills/seo-aeo-schema-generator/SKILL.md CHANGED Viewed

@@ -1,108 +1,342 @@
 ---
 name: seo-aeo-schema-generator
-description: "Generates valid JSON-LD structured data for 10 schema types with rich result eligibility validation and implementation-ready script blocks. Activate when the user wants to generate schema markup, JSON-LD, or structured data for any page."
+description: "Generates and validates implementation-ready JSON-LD structured data for relevant page types and rich-result eligibility."
 risk: safe
 source: community
 date_added: "2026-04-01"
 ---
-# SEO-AEO Schema Generator
+# Schema Generator Skill
-## Overview
+## Description
+Activate this skill when the user wants to generate, write,
+or validate structured data markup for any page.
+Trigger phrases include: "generate schema", "create JSON-LD",
+"schema markup for", "structured data for",
+"FAQ schema", "product schema", "article schema",
+"help Google understand my page", "rich results schema",
+"schema generator: [type]", "add schema to [page]".
-Generates implementation-ready JSON-LD schema markup for 10 schema types including FAQPage, Article, Product, HowTo, and BreadcrumbList. Validates all required fields against Google rich result eligibility rules, flags missing fields with exact fix instructions, and outputs one clean `<script>` block per schema type ready to paste into the page `<head>`.
+---
+## Input Format
+````json
+{
+  "page_type": "landing-page | blog-post | pillar-page |
+                product-page | homepage | faq-page |
+                how-to-page",
+  "schema_types": ["string — list all types needed for
+                    this page, see Schema Type Menu below"],
+  "page_data": {
+    "url": "string — canonical URL of the page",
+    "title": "string — page title",
+    "description": "string — page meta description
+                    or content summary",
+    "primary_keyword": "string",
+    "date_published": "string — ISO format: YYYY-MM-DD",
+    "date_modified": "string — ISO format: YYYY-MM-DD",
+    "author_name": "string — for Article schema",
+    "brand_name": "string",
+    "brand_url": "string — homepage URL",
+    "logo_url": "string — absolute URL to brand logo",
+    "product": {
+      "name": "string",
+      "description": "string",
+      "image_url": "string",
+      "price": "decimal",
+      "currency": "string — ISO 4217, e.g. USD, GBP",
+      "availability": "InStock | OutOfStock | PreOrder",
+      "sku": "string — optional"
+    },
+    "reviews": [
+      {
+        "author": "string",
+        "rating": "integer — 1 to 5",
+        "review_body": "string",
+        "date": "string — YYYY-MM-DD"
+      }
+    ],
+    "aggregate_rating": {
+      "rating_value": "decimal — e.g. 4.7",
+      "review_count": "integer",
+      "best_rating": "integer — usually 5",
+      "worst_rating": "integer — usually 1"
+    },
+    "faqs": [
+      {
+        "question": "string",
+        "answer": "string"
+      }
+    ],
+    "how_to": {
+      "name": "string — title of the how-to",
+      "description": "string",
+      "total_time": "string — ISO 8601 duration, e.g. PT30M",
+      "steps": [
+        {
+          "name": "string — step title",
+          "text": "string — step instructions"
+        }
+      ]
+    },
+    "breadcrumbs": [
+      {
+        "position": "integer — 1, 2, 3...",
+        "name": "string — label",
+        "url": "string — absolute URL"
+      }
+    ]
+  }
+}
+````
+---
+## Schema Type Menu
+This skill supports the following schema types.
+Multiple types can be requested for a single page:
+| Schema Type          | Best For                                    | Rich Result Unlocked                    |
+|----------------------|---------------------------------------------|-----------------------------------------|
+| `Article`            | Blog posts, pillar pages, news              | Article rich result, Top Stories        |
+| `FAQPage`            | FAQ sections on any page                    | FAQ accordion in SERP — AEO critical    |
+| `HowTo`              | Step-by-step guides                         | Step-by-step rich result                |
+| `Product`            | Product or pricing pages                    | Price, availability, rating in SERP     |
+| `Review`             | Individual product or service reviews       | Star rating in SERP                     |
+| `AggregateRating`    | Pages with multiple reviews                 | Star rating with review count           |
+| `BreadcrumbList`     | Any page with a navigation hierarchy        | Breadcrumb path shown in SERP URL       |
+| `Organization`       | Homepage or About page                      | Brand knowledge panel signals           |
+| `WebPage`            | Any page needing basic structured identity  | Enhances page understanding by crawlers |
+| `WebSite`            | Homepage only                               | Sitelinks Searchbox in SERP             |
+**AEO Priority:** `FAQPage` and `HowTo` are the two schema
+types most directly responsible for AI engine extraction.
+Always include `FAQPage` on landing pages and blog posts
+that contain a FAQ section.
-Part of the [SEO-AEO Engine](https://github.com/mrprewsh/seo-aeo-engine).
+---
+## Rich Result Eligibility Rules
-## When to Use This Skill
+Google requires specific fields to be present for each
+schema type to qualify for rich results.
+Missing required fields disqualifies the page entirely.
-- Use when adding structured data to a new landing page or blog post
-- Use when a page needs FAQ rich results or product star ratings in search
-- Use when validating existing schema for Google rich result eligibility
-- Use after the content-quality-auditor flags missing schema
+### FAQPage
+| Field          | Status      | Notes                                    |
+|----------------|-------------|------------------------------------------|
+| `@type`        | Required    | Must be `FAQPage`                        |
+| `mainEntity`   | Required    | Array of `Question` objects              |
+| `name`         | Required    | The question text                        |
+| `acceptedAnswer` | Required  | `Answer` object containing `text`        |
+| Minimum Qs     | Required    | At least 2 question-answer pairs         |
+| Answer length  | Recommended | Under 300 words per answer               |
-## Supported Schema Types
+### Article
+| Field              | Status      | Notes                                |
+|--------------------|-------------|--------------------------------------|
+| `headline`         | Required    | Under 110 characters                 |
+| `image`            | Required    | At least one image URL               |
+| `datePublished`    | Required    | ISO 8601 format                      |
+| `dateModified`     | Recommended | ISO 8601 format                      |
+| `author`           | Required    | `Person` or `Organization` object    |
+| `publisher`        | Required    | `Organization` with `logo`           |
-| Type | Rich Result Unlocked |
-|------|---------------------|
-| FAQPage | FAQ accordion in SERP — AEO critical |
-| Article | Article rich result, Top Stories |
-| Product | Price, availability, rating in SERP |
-| HowTo | Step-by-step rich result |
-| Review | Star rating in SERP |
-| AggregateRating | Star rating with review count |
-| BreadcrumbList | Breadcrumb path in SERP URL |
-| Organization | Brand knowledge panel signals |
-| WebPage | Enhanced page understanding |
-| WebSite | Sitelinks Searchbox |
+### Product
+| Field              | Status      | Notes                                |
+|--------------------|-------------|--------------------------------------|
+| `name`             | Required    | Product name                         |
+| `image`            | Required    | Absolute URL                         |
+| `description`      | Recommended |                                      |
+| `offers`           | Required    | `Offer` object with price + currency |
+| `price`            | Required    | Numeric value                        |
+| `priceCurrency`    | Required    | ISO 4217 currency code               |
+| `availability`     | Recommended | Schema.org availability URL          |
+| `aggregateRating`  | Recommended | Unlocks star rating display          |
-## How It Works
+### HowTo
+| Field              | Status      | Notes                                |
+|--------------------|-------------|--------------------------------------|
+| `name`             | Required    | Title of the how-to                  |
+| `step`             | Required    | Array of `HowToStep` objects         |
+| `text`             | Required    | Instructions for each step           |
+| `totalTime`        | Recommended | ISO 8601 duration                    |
+| `image`            | Recommended | Image per step if available          |
-### Step 1: Recommend Schema Types
-If schema types are not specified, recommend the appropriate types based on the page type. Landing pages get FAQPage + Product + BreadcrumbList. Blog posts get Article + FAQPage + BreadcrumbList.
+### BreadcrumbList
+| Field              | Status      | Notes                                |
+|--------------------|-------------|--------------------------------------|
+| `itemListElement`  | Required    | Array of `ListItem` objects          |
+| `position`         | Required    | Integer, starts at 1                 |
+| `name`             | Required    | Breadcrumb label                     |
+| `item`             | Required    | Absolute URL for each crumb          |
+---
-### Step 2: Use Built-In Schema Templates
-Using your knowledge of schema.org and Google's rich result requirements, construct the JSON-LD template for each requested schema type. Use the required and recommended fields listed in the Google Rich Results documentation for that type.
+## Output Structure
-### Step 3: Populate Fields
-Map all page data to template placeholders. Check every required field against the rich result eligibility rules.
+The skill must always produce output in this exact format:
+````markdown
+# Schema Markup Output
+**Page:** [page title]
+**URL:** [url]
+**Schema Types Generated:** [list all types]
+**Rich Results Unlocked:** [list eligible rich results]
+**AEO Signals Added:** [list AEO-relevant schema types]
+---
-### Step 4: Validate
-Flag any missing required field as a Critical issue. Flag missing recommended fields as warnings. Do not output schema with missing required fields.
+## Validation Summary
-### Step 5: Output Script Blocks
-Write one `<script type="application/ld+json">` block per schema type. Include implementation instructions and testing tool links.
+| Schema Type       | Required Fields Complete | Rich Result Eligible | Issues Found |
+|-------------------|--------------------------|----------------------|--------------|
+| [type]            | ✅ / ❌                  | ✅ / ❌              | [n or none]  |
+| [type]            | ✅ / ❌                  | ✅ / ❌              | [n or none]  |
-## Examples
+---
+## Issues Found
+[If no issues: ✅ All schema types passed validation.]
+**Issue:** [Specific field missing or incorrect]
+**Schema Type:** [type]
+**Severity:** Required / Recommended
+**Fix:** [Exact instruction — what to add or change]
+---
-### Example: FAQPage Schema Output
+## JSON-LD Output
+Place all script blocks inside the `<head>` of your HTML.
+Use one `<script>` block per schema type.
+### [Schema Type 1]
 ```html
 <script type="application/ld+json">
 {
   "@context": "https://schema.org",
-  "@type": "FAQPage",
-  "mainEntity": [
-    {
-      "@type": "Question",
-      "name": "What is Syncro?",
-      "acceptedAnswer": {
-        "@type": "Answer",
-        "text": "Syncro is a remote-first project management platform for distributed engineering teams. It centralises task tracking, async communication, and sprint planning in one tool."
-      }
-    }
-  ]
+  "@type": "[type]",
+  [all populated fields from references/ template]
 }
 </script>
 ```
-## Best Practices
+### [Schema Type 2]
+```html
+<script type="application/ld+json">
+{
+  "@context": "https://schema.org",
+  "@type": "[type]",
+  [all populated fields]
+}
+</script>
+```
-- ✅ **Do:** Always include FAQPage schema on any page with a FAQ section — it is the strongest AEO signal
-- ✅ **Do:** Use one `<script>` block per schema type — never combine multiple types
-- ✅ **Do:** Test every output in Google's Rich Results Test before deploying
-- ❌ **Don't:** Use relative URLs anywhere in schema — all URLs must start with `https://`
-- ❌ **Don't:** Leave placeholder text in any field before deploying
-- ❌ **Don't:** Use HTML tags inside JSON-LD string values
+---
-## Common Pitfalls
+## Implementation Instructions
-- **Problem:** Schema passes validation but rich result doesn't appear in search
-  **Solution:** Rich results can take weeks to appear after deployment. Request re-indexing in Google Search Console immediately after adding schema.
+1. Copy each `<script>` block above
+2. Paste inside the `<head>` tag of your HTML —
+   after the `<title>` tag, before `</head>`
+3. One script block per schema type —
+   do not combine multiple types in one block
+4. Test immediately using Google's Rich Results
+   Test: https://search.google.com/test/rich-results
+5. Test using Schema.org Validator:
+   https://validator.schema.org
+6. After deploying, request re-indexing in
+   Google Search Console
-- **Problem:** Product schema missing star rating display
-  **Solution:** Add AggregateRating object with ratingValue, reviewCount, bestRating, and worstRating — all four fields required.
+---
-## Related Skills
+## Testing Checklist
-- `@seo-aeo-landing-page-writer` — provides the FAQ and product data for schema population
-- `@seo-aeo-content-quality-auditor` — flags schema gaps during the audit
+- [ ] All required fields populated for each schema type
+- [ ] No placeholder text left in any field
+- [ ] All URLs are absolute (https://...) not relative (/page)
+- [ ] Date fields use ISO 8601 format (YYYY-MM-DD)
+- [ ] Price uses decimal format (e.g. 49.00 not $49)
+- [ ] Currency uses ISO 4217 code (USD not $)
+- [ ] FAQPage has minimum 2 question-answer pairs
+- [ ] No HTML tags inside JSON-LD string values
+- [ ] Each schema type in its own `<script>` block
+- [ ] Tested in Google Rich Results Test ✅
+- [ ] Tested in Schema.org Validator ✅
+````
-## Additional Resources
+---
-- [SEO-AEO Engine Repository](https://github.com/mrprewsh/seo-aeo-engine)
-- [Full Schema Generator SKILL.md](https://github.com/mrprewsh/seo-aeo-engine/blob/main/.agent/skills/schema-generator/SKILL.md)
+## References Folder
+The `references/` folder contains pre-validated
+JSON-LD templates for all supported schema types.
+The script uses these as base structures and
+populates them with page data.
+````
+references/
+├── faq-schema.json
+├── article-schema.json
+├── product-schema.json
+├── review-schema.json
+├── aggregate-rating-schema.json
+├── howto-schema.json
+├── breadcrumb-schema.json
+├── organization-schema.json
+├── webpage-schema.json
+└── website-schema.json
+````
+Each template contains all required and recommended
+fields with placeholder values in this format:
+`"{{field_name}}"`. The `schema_builder.py` script
+replaces all placeholders with the values from `page_data`.
+---
+## Execution Steps
+1. Read `page_type` and `schema_types` —
+   if `schema_types` is empty, recommend the
+   appropriate types based on `page_type` using
+   the Schema Type Menu before proceeding
+2. For each requested schema type, load the
+   corresponding template from `references/`
+3. Map all fields from `page_data` to the
+   template placeholders
+4. Check every required field against the
+   Rich Result Eligibility Rules —
+   flag any missing required field as an issue
+   before outputting
+5. Check every recommended field — flag as
+   a warning if missing but do not block output
+6. Validate all URLs are absolute,
+   all dates are ISO 8601,
+   all prices are decimal format
+7. Generate one clean `<script>` block
+   per schema type
+8. Build the Validation Summary table
+9. List all issues with severity and exact fix instructions
+10. Write Implementation Instructions
+    and Testing Checklist
+11. Populate the selected reference template from supplied page data, validate required fields, and show unresolved placeholders as blocking issues. Use a project-provided schema helper only as a supplementary check; never emit fabricated review, rating, or product claims.
+---
+## Connected Skills
+- Receives output from: `seo-aeo-landing-page-writer`,
+  `seo-aeo-blog-writer`, `seo-aeo-content-quality-auditor`,
+  `seo-aeo-internal-linking`
+- Feeds output to: orchestrator workflow —
+  final step before publish checklist
+## When to Use
+Use when adding or validating JSON-LD structured data for a page and the supplied visible content supports the selected schema type.
 ## Limitations
-- Use this skill only when the task clearly matches the scope described above.
-- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
-- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
+- Structured data must match visible, truthful page content; valid JSON-LD does not guarantee rich results, indexing, or display.

package/bundled-skills/seo-aeo-schema-generator/references/aggregate-rating-schema.json ADDED Viewed

@@ -0,0 +1,8 @@
+{
+  "@context": "https://schema.org",
+  "@type": "AggregateRating",
+  "itemReviewed": {"@type": "Product", "name": "{{item_name}}"},
+  "ratingValue": "{{rating_value}}",
+  "bestRating": "{{best_rating}}",
+  "ratingCount": "{{rating_count}}"
+}

package/bundled-skills/seo-aeo-schema-generator/references/article-schema.json ADDED Viewed

@@ -0,0 +1,10 @@
+{
+  "@context": "https://schema.org",
+  "@type": "Article",
+  "headline": "{{headline}}",
+  "description": "{{description}}",
+  "author": {"@type": "Person", "name": "{{author_name}}"},
+  "datePublished": "{{date_published}}",
+  "dateModified": "{{date_modified}}",
+  "mainEntityOfPage": "{{url}}"
+}

package/bundled-skills/seo-aeo-schema-generator/references/breadcrumb-schema.json ADDED Viewed

@@ -0,0 +1,5 @@
+{
+  "@context": "https://schema.org",
+  "@type": "BreadcrumbList",
+  "itemListElement": "{{item_list_element}}"
+}

package/bundled-skills/seo-aeo-schema-generator/references/faq-schema.json ADDED Viewed

@@ -0,0 +1,5 @@
+{
+  "@context": "https://schema.org",
+  "@type": "FAQPage",
+  "mainEntity": "{{main_entity}}"
+}

package/bundled-skills/seo-aeo-schema-generator/references/howto-schema.json ADDED Viewed

@@ -0,0 +1,7 @@
+{
+  "@context": "https://schema.org",
+  "@type": "HowTo",
+  "name": "{{name}}",
+  "description": "{{description}}",
+  "step": "{{step}}"
+}

package/bundled-skills/seo-aeo-schema-generator/references/organization-schema.json ADDED Viewed

@@ -0,0 +1,7 @@
+{
+  "@context": "https://schema.org",
+  "@type": "Organization",
+  "name": "{{name}}",
+  "url": "{{url}}",
+  "logo": "{{logo}}"
+}

package/bundled-skills/seo-aeo-schema-generator/references/product-schema.json ADDED Viewed

@@ -0,0 +1,8 @@
+{
+  "@context": "https://schema.org",
+  "@type": "Product",
+  "name": "{{name}}",
+  "description": "{{description}}",
+  "brand": {"@type": "Brand", "name": "{{brand_name}}"},
+  "offers": {"@type": "Offer", "url": "{{url}}", "priceCurrency": "{{price_currency}}", "price": "{{price}}", "availability": "{{availability}}"}
+}

package/bundled-skills/seo-aeo-schema-generator/references/review-schema.json ADDED Viewed

@@ -0,0 +1,8 @@
+{
+  "@context": "https://schema.org",
+  "@type": "Review",
+  "itemReviewed": {"@type": "Product", "name": "{{item_name}}"},
+  "reviewRating": {"@type": "Rating", "ratingValue": "{{rating_value}}", "bestRating": "{{best_rating}}"},
+  "author": {"@type": "Person", "name": "{{author_name}}"},
+  "reviewBody": "{{review_body}}"
+}

package/bundled-skills/seo-aeo-schema-generator/references/webpage-schema.json ADDED Viewed

@@ -0,0 +1,7 @@
+{
+  "@context": "https://schema.org",
+  "@type": "WebPage",
+  "name": "{{name}}",
+  "description": "{{description}}",
+  "url": "{{url}}"
+}

package/bundled-skills/seo-aeo-schema-generator/references/website-schema.json ADDED Viewed

@@ -0,0 +1,7 @@
+{
+  "@context": "https://schema.org",
+  "@type": "WebSite",
+  "name": "{{name}}",
+  "url": "{{url}}",
+  "description": "{{description}}"
+}

package/bundled-skills/youtube-transcript-skills/SKILL.md ADDED Viewed

@@ -0,0 +1,110 @@
+---
+name: youtube-transcript-skills
+description: "Fetch YouTube video transcripts, search videos/channels, browse channels, and extract playlists via the getyoutubetranscript.com API - free tier, no card required."
+category: api-integration
+risk: safe
+source: community
+source_repo: tubeagentkit/youtube-transcript-skills
+source_type: community
+date_added: "2026-09-13"
+author: tubeagentkit
+tags: [youtube, transcripts, video-search, channels, playlists, api]
+tools: [claude, cursor, codex, gemini]
+license: "MIT"
+license_source: "https://github.com/tubeagentkit/youtube-transcript-skills/blob/main/LICENSE"
+upstream: "https://github.com/tubeagentkit/youtube-transcript-skills"
+---
+# YouTube Transcript
+## Overview
+Fetches transcripts, search results, and playlist/channel data from YouTube
+via the [getyoutubetranscript.com](https://getyoutubetranscript.com) REST
+API, so an agent can summarize, quote, search, or analyze a video's actual
+spoken content without the user copy-pasting it in by hand. No `yt-dlp` and
+no Google API key required.
+- `source_repo: tubeagentkit/youtube-transcript-skills`
+- `source_type: community`
+## When to Use This Skill
+- Use when the user wants a YouTube video's transcript fetched, summarized, quoted, or analyzed.
+- Use when the user wants to search YouTube (globally, or within one channel by handle).
+- Use when the user wants a channel handle resolved to a channel ID, or wants a channel's info and upload history.
+- Use when the user wants the videos in a YouTube playlist.
+## How It Works
+### Step 1: Get an API key
+Every call needs an API key: the `YOUTUBE_TRANSCRIPT_API_KEY` environment
+variable, or one the user has already provided. If neither exists, the skill
+can sign the user up for a free account (100 credits, no card required) via a
+two-step email + verification-code flow against the API - only after the
+user has explicitly given consent and an email address to use.
+### Step 2: Call the API
+Base URL: `https://getyoutubetranscript.com/api/v1`. Send the key as
+`Authorization: Bearer <API_KEY>` or `x-api-key: <API_KEY>`.
+- `GET /transcript?v=<VIDEO_ID_OR_URL>&language=en` - fetch a transcript.
+- `GET /search?q=<query>&type=video|channel` - search YouTube.
+- `GET /resolve?handle=@name` - resolve a channel handle to a channel ID (free).
+- `GET /channel/latest?channel=@name` - channel info and latest videos (free).
+- `GET /channel/videos?channel=@name` - a channel's full upload history (paginated).
+- `GET /channel/search?channel=@name&q=<query>` - search within a channel (paginated).
+- `GET /playlist?list=<playlist ID or URL>` - playlist videos (paginated).
+### Step 3: Handle errors and pagination
+Every error is JSON with a stable `code` (e.g. `TRANSCRIPT_NOT_FOUND`,
+`PAYMENT_REQUIRED`, `RATE_LIMITED`) and a matching HTTP status - relay the
+`message` field to the user rather than guessing at a fix. Paginated
+endpoints return an opaque `data.continuation_token`; pass it back verbatim
+as `continuation` to get the next page, `null` means no more pages.
+## Examples
+### Example 1: Summarize a video
+```bash
+curl -s "https://getyoutubetranscript.com/api/v1/transcript?v=jNQXAC9IVRw&language=en" \
+  -H "Authorization: Bearer $YOUTUBE_TRANSCRIPT_API_KEY"
+```
+### Example 2: Browse a channel's uploads
+```bash
+curl -s "https://getyoutubetranscript.com/api/v1/channel/videos?channel=@mkbhd" \
+  -H "Authorization: Bearer $YOUTUBE_TRANSCRIPT_API_KEY"
+```
+## Best Practices
+- Do reuse an existing `YOUTUBE_TRANSCRIPT_API_KEY` before offering to create a new account.
+- Do ask explicit consent before sending an email address anywhere during signup.
+- Don't retry a `402 PAYMENT_REQUIRED` response - direct the user to top up instead.
+- Don't hammer a `429 RATE_LIMITED` response in a retry loop - back off.
+## Limitations
+- The transcript endpoint returns the full spoken text as one string; there is no per-line timestamp breakdown.
+- This skill does not replace environment-specific validation, testing, or expert review.
+- Stop and ask for clarification if required inputs, permissions, or safety boundaries are missing.
+## Security & Safety Notes
+- This skill only makes outbound HTTPS requests to `getyoutubetranscript.com` endpoints, plus - during first-time setup - an email address the user explicitly provides. It runs no other shell commands and installs nothing.
+- Never persist a newly issued API key to a shell profile or other file without the user's explicit confirmation first.
+## Common Pitfalls
+- **Problem:** Assuming the transcript response includes timestamps.
+  **Solution:** Tell the user timestamps aren't available from this endpoint rather than inventing them.
+## Related Skills
+- `@youtube-full` - an alternative YouTube transcript/search/channel/playlist skill backed by a different upstream API.

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "opencode-skills-collection",
-  "version": "4.0.64",
+  "version": "4.0.66",
   "description": "OpenCode CLI plugin that automatically downloads and keeps skills up to date.",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",