add-source

Resolve URLs, derive metadata, and insert validated entries into the awesome-engineering-research INDEX.

8|1|Updated Apr 20, 2018
One-click install
npx skills add https://github.com/Executioner1939/awesome-engineering-research --skill add-source-executioner1939
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-source
Source: https://github.com/Executioner1939/awesome-engineering-research/tree/main/.claude/skills/add-source
Command: npx skills add https://github.com/Executioner1939/awesome-engineering-research --skill add-source-executioner1939

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It saves you from manually formatting and sanity-checking entries when adding new reading material or tools to the awesome-engineering-research corpus.

Core Features & Use Cases

  • URL resolution & liveness validation: Validates the target URL via a HEAD request with redirects and aborts if the link is dead.
  • Automatic metadata derivation: Extracts title, published/created dates, descriptions, language, and repo attributes from the page or GitHub API.
  • Taxonomy-aligned labeling: Generates a canonical, sorted set of domain and refinement labels derived from the URL and content.
  • Correct INDEX insertion with provenance: Appends a correctly-shaped row into INDEX/sources.md or INDEX/tools.md, ensuring stable IDs and required fields.

Quick Start

Tell the skill the URL and type of the item you want to add, optionally including labels and a one-line note, and it will validate and insert the new entry into the correct INDEX table.

Frequently Asked Questions about add-source

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

FAQPage Schema
How do I validate URL liveness and extract metadata before adding a source to an index?

URL liveness validation checks target links via HEAD requests with redirect handling, automatically aborting dead links. Metadata extraction then pulls titles, dates, descriptions, and language attributes directly from the page or API to ensure correct index insertion.

What's the best way to add GitHub repositories to a curated reading index with consistent frontmatter?

Adding GitHub repositories requires archive and state verification via the GitHub API to confirm repo validity. The process extracts repository attributes, assigns deterministic IDs with collision handling, and appends a correctly-shaped row with provenance metadata to the index.

How do I generate taxonomy-aligned labels for articles, videos, and papers in a research corpus?

Taxonomy-aligned labels are generated by deriving a canonical, sorted set of domain and refinement labels from the target URL and content. This ensures every article, video, talk, book, paper, RFC, podcast, course, or doc entry conforms to strict row-shape standards.

Can I use this to add podcasts and courses to a markdown index, or is it limited to articles and repos?

Adding podcasts and courses to the markdown index is fully supported alongside articles, videos, talks, books, papers, RFCs, and docs. The tool resolves URLs, derives required metadata, and inserts entries into either the sources or tools markdown file.

How do I handle ID collisions when inserting new entries into a sources or tools markdown file?

Deterministic ID assignment manages collisions automatically by applying strict row-shape conformance using repository templates. This ensures stable identifiers and required fields are maintained when appending new validated entries to the index.

Why does my URL validation fail when adding a source, and does it handle redirects?

URL validation fails when a HEAD request detects a dead link without valid redirects. The liveness check explicitly handles redirects during resolution, aborting the insertion process if the final target remains unreachable or returns an error.