skills.rest
aws-samples
aws-samplesOFFICIAL
Explore all skills by this author →
WebsiteGitHub

Check Examples GitHub Links

Validate GitHub raw content URLs in examples-metadata.json for HTTP 200 and accessibility.

84|32|Updated Jun 9, 2025
Search Tags:#github#validation#metadata#http#urls#check
One-click install
npx skills add https://github.com/aws-samples/review-and-assessment-powered-by-intelligent-documentation --skill check-examples-github-links
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Check Examples GitHub Links
Source: https://github.com/aws-samples/review-and-assessment-powered-by-intelligent-documentation/tree/main/.claude/skills/check-examples-links
Command: npx skills add https://github.com/aws-samples/review-and-assessment-powered-by-intelligent-documentation --skill check-examples-github-links

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams ensure that every GitHub raw content URL referenced in examples-metadata.json is reachable, preventing broken assets in documentation and demos.

Core Features & Use Cases

  • URL discovery: scans frontend/src/features/examples/data/examples-metadata.json for all English and Japanese entries and extracts every https://raw.githubusercontent.com/... URL.
  • Validation & reporting: performs HTTP 200 checks, confirms content accessibility, and generates a concise report of working vs broken links for audit trails.
  • Use Case: QA engineers and documentation teams can run this before release to guarantee all example assets remain accessible.

Quick Start

Run the skill against the repository's examples-metadata.json to validate all listed GitHub URLs and produce an accessibility report.

Frequently Asked Questions about Check Examples GitHub Links

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

FAQPage Schema
How do I validate GitHub raw content URLs in a metadata JSON file?▼

To validate GitHub raw content URLs, scan the examples-metadata.json file to extract all raw.githubusercontent.com links and perform HTTP 200 accessibility checks for both English and Japanese entries.

What is the best way to check for broken GitHub links before a documentation release?▼

Checking for broken GitHub links requires scanning your metadata JSON for raw content URLs and generating an accessibility report that distinguishes working links from broken ones for audit trails.

Can I validate both English and Japanese GitHub URLs in the same metadata file?▼

Yes, you can validate both English and Japanese GitHub URLs by scanning the en and ja data sections within examples-metadata.json to ensure all referenced raw content is reachable.

How does HTTP 200 validation work for raw GitHubusercontent URLs?▼

HTTP 200 validation for raw GitHubusercontent URLs works by sending requests to each extracted link and confirming the server returns a successful response, ensuring the content is accessible.

What should I do if my examples-metadata.json contains unreachable GitHub assets?▼

If your examples-metadata.json contains unreachable GitHub assets, run a comprehensive broken-link report to identify failing URLs and replace them to prevent broken assets in demos.

Related Skills

Explore More Software Engineering Skills→
pinion05pinion05
3

github-gist

Publish files or stdin input as public or secret GitHub Gists.

Community
Intermediate
simplefarmer69simplefarmer69
2

devops-bridge

Integrate GitHub, CI/CD, messaging platforms, and issue trackers to automate developer operations.

Community
Advanced
DalomeveDalomeve
3

evidence-link-auditor

Scan markdown files to validate internal and external evidence links with PASS/FAIL reports.

Community
Advanced
fcakyonfcakyon
1.0k

tavily-usage

Search the web and extract content from URLs via Tavily APIs.

Community
Intermediate