resource-management

Maintains the resources.json registry that drives the plugin-dev-sync discovery pipeline.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/karimStekelenburg/k3m-marketplace --skill resource-management-karimstekelenburg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resource-management
Source: https://github.com/karimStekelenburg/k3m-marketplace/tree/main/plugins/plugin-dev-sync/skills/resource-management
Command: npx skills add https://github.com/karimStekelenburg/k3m-marketplace --skill resource-management-karimstekelenburg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a plugin's discovery pipeline fed with accurate, reachable content sources requires a consistent registry. This Skill guides you through adding, updating, validating, and deactivating entries in the master resources.json file so the sync pipeline always crawls the right URLs. ## Core Features & Use Cases - Structured Resource Schema: Enforces a consistent entry format with id, url, name, category, type, notes, and status fields. - Add and Validate Workflow: Walks through verifying URL reachability with curl, assigning kebab-case ids, and testing fetches via the fetch-resources.py script. - Safe Deactivation: Prefers marking resources inactive over deletion to preserve history. - Use Case: You want the pipeline to start tracking a new Anthropic documentation page. Add an entry with category official-docs and type page, then run the fetch script filtered by id to confirm the cached content is useful. ## Quick Start Ask the assistant to add a new documentation source to the plugin-dev-sync resource list and verify it fetches correctly.

Frequently Asked Questions about resource-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new resource to the resources.json file?▼

Read the current data/resources.json, verify the URL is reachable with curl -sI, assign a kebab-case id following the category-short-name pattern, and append the entry to the resources array. Then test it with the fetch script using the --id flag.

What fields are required for each resource entry?▼

Each entry requires id, url, name, category, type, and status. The notes field is optional and provides context for crawlers about what to look for on the page.

What categories and types does the resource schema support?▼

Categories are official-docs, github, social, and community. Types include page, sitemap-root, repo, releases, directory, twitter, rss, and api, covering documentation sites, repositories, and social accounts.

Should I delete a resource that no longer works?▼

Prefer setting the status field to inactive rather than deleting, which preserves history. Only delete entries that were added by mistake, and check data/fetch-report.json to diagnose why fetches fail.

How do I validate that all resources are still reachable?▼

Run uv run scripts/fetch-resources.py to fetch every registered resource. Review the generated data/fetch-report.json for failures such as changed URLs, removed pages, or rate limiting.