opencode-skills-collection 3.0.47 → 3.0.49

package/bundled-skills/crossframe-teach/references/teaching-fidelity.md

@@ -0,0 +1,44 @@
+# 教学保真规则
+
+本文件只规定教学表达的保真方式。概念定义以 `../crossframe/` 下的 canonical 中文材料为准。
+
+## 四个硬闸
+
+1. **术语闸**：第一段删掉所有 CrossFrame 术语后仍然能懂；如果不能，重写。
+2. **长度闸**：解释可以短，但不能短到丢掉核心差异、误读边界或现实信号。
+3. **道德闸**：概念不能变成“你应该更好、更忍、更爱、更负责”的道德命令。
+4. **练习闸**：默认必须有练习或自测，帮助用户辨认概念边界。
+
+## 好解释的结构
+
+- 先讲一个普通人能遇到的场面。
+- 再说这个场面里谁在付成本、什么条件有没有改变。
+- 再把它映射到 CrossFrame 概念。
+- 最后给一个反例和一个练习，让用户知道边界。
+
+## 禁止的退化
+
+- 用术语堆叠替代解释。
+- 把概念当成现实诊断结论。
+- 把证据不足的开放判断说成强判断。
+- 把爱、承接、责任链讲成单方牺牲。
+- 把“态度变好”“说了抱歉”“写了报告”直接当作回流或修复。
+- 把练习题写成价值表态题，例如“你愿不愿意更有爱”。
+
+## 反例写法
+
+反例要短，并且指出为什么不算这个概念：
+
+- 不算承接/回流：只有口头感谢，没有规则、资源、角色或边界变化。
+- 不算开放断言：只说“不确定”，没有当前判断、替代解释和撤回条件。
+- 不算爱/开放行动：要求别人继续牺牲，却没有真实成本、边界和回流。
+
+## 练习写法
+
+练习优先使用三类：
+
+- **辨认题**：给一个小场景，让用户判断是否属于该概念。
+- **改写题**：把术语句改成人话。
+- **观察题**：让用户列出 2 个现实信号和 1 个撤回条件。
+
+练习答案要允许有边界感，不要求唯一价值立场。

package/bundled-skills/crossframe-teach/templates/concept-lesson.md

@@ -0,0 +1,38 @@
+# 概念教学模板
+
+用于输出完整的 CrossFrame 概念解释。按需删减，但不要改变主要顺序。
+
+## 先说人话
+
+用 2-5 句普通语言解释这个概念在现实里通常说的是什么。第一段不要把术语当结论。
+
+## 概念映射
+
+- 它在 CrossFrame 里关注：
+- 它通常牵涉的结构问题：
+- 它不能直接证明：
+
+## 反例与误读边界
+
+- 常见误读：
+- 一个坏例：
+- 为什么这个坏例不成立：
+
+## 现实中看什么
+
+- 信号 1：
+- 信号 2：
+- 信号 3：
+- 让判断撤回或降档的情况：
+
+## 小练习
+
+1. 辨认题：
+2. 改写题：
+3. 观察题：
+
+## 如果继续分析现实案例
+
+需要补充哪些事实：
+
+下一步应进入的 canonical protocol：

package/bundled-skills/crossframe-teach/templates/micro-exercises.md

@@ -0,0 +1,39 @@
+# 微练习模板
+
+用于用户只想练概念辨认、边界或表达。
+
+## 练习组
+
+### 1. 辨认题
+
+场景：
+
+问题：这算不算这个概念？为什么？
+
+判分点：
+
+- 是否指出现实行为，而不是只喊术语。
+- 是否区分事实和解释。
+- 是否写出一个不成立条件。
+
+### 2. 改写题
+
+术语句：
+
+请改成人话：
+
+参考方向：
+
+- 保留核心结构。
+- 去掉道德命令。
+- 写出可观察信号。
+
+### 3. 边界题
+
+问题：什么情况下这个概念不能用？
+
+参考方向：
+
+- 缺事实时不能强判断。
+- 只看态度不等于看结构变化。
+- 不能取消责任链或安全边界。

package/bundled-skills/docs/integrations/jetski-cortex.md

@@ -1,9 +1,9 @@
 ---
 title: Jetski/Cortex + Gemini Integration Guide
-description: "Use antigravity-awesome-skills with Jetski/Cortex without hitting context-window overflow with 1,550+ skills."
+description: "Use antigravity-awesome-skills with Jetski/Cortex without hitting context-window overflow with 1,569+ skills."
 ---
 
-# Jetski/Cortex + Gemini: safe integration with 1,550+ skills
+# Jetski/Cortex + Gemini: safe integration with 1,569+ skills
 
 This guide shows how to integrate the `antigravity-awesome-skills` repository with an agent based on **Jetski/Cortex + Gemini** (or similar frameworks) **without exceeding the model context window**.
 
@@ -23,7 +23,7 @@ Never do:
 - concatenate all `SKILL.md` content into a single system prompt;
 - re-inject the entire library for **every** request.
 
-With 1,550+ skills, this approach fills the context window before user messages are even added, causing truncation.
+With 1,569+ skills, this approach fills the context window before user messages are even added, causing truncation.
 
 ---
 

package/bundled-skills/docs/integrations/jetski-gemini-loader/README.md

@@ -21,7 +21,7 @@ This example shows one way to integrate **antigravity-awesome-skills** with a Je
 - How to enforce a **maximum number of skills per turn** via `maxSkillsPerTurn`.
 - How to choose whether to **truncate or error** when too many skills are requested via `overflowBehavior`.
 
-This pattern avoids context overflow when you have 1,550+ skills installed.
+This pattern avoids context overflow when you have 1,569+ skills installed.
 
 Manifest contract references:
 

package/bundled-skills/docs/maintainers/repo-growth-seo.md

@@ -6,7 +6,7 @@ This document keeps the repository's GitHub-facing discovery copy aligned with t
 
 Preferred positioning:
 
-> Installable GitHub library of 1,550+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and other AI coding assistants.
+> Installable GitHub library of 1,569+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and other AI coding assistants.
 
 Key framing:
 
@@ -20,7 +20,7 @@ Key framing:
 
 Preferred description:
 
-> Installable GitHub library of 1,550+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and more. Includes installer CLI, bundles, workflows, and official/community skill collections.
+> Installable GitHub library of 1,569+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and more. Includes installer CLI, bundles, workflows, and official/community skill collections.
 
 Preferred homepage:
 
@@ -28,7 +28,7 @@ Preferred homepage:
 
 Preferred social preview:
 
-- use a clean preview image that says `1,550+ Agentic Skills`;
+- use a clean preview image that says `1,569+ Agentic Skills`;
 - mention Claude Code, Cursor, Codex CLI, and Gemini CLI;
 - avoid dense text and tiny logos that disappear in social cards.
 

package/bundled-skills/docs/maintainers/skills-update-guide.md

@@ -72,7 +72,7 @@ The update process refreshes:
 - Canonical skills index (`skills_index.json`)
 - Compatibility mirror (`data/skills_index.json`)
 - Web app skills data (`apps\web-app\public\skills.json`)
-- All 1,550+ skills from the skills directory
+- All 1,569+ skills from the skills directory
 
 ## When to Update
 

package/bundled-skills/docs/users/bundles.md

@@ -917,4 +917,4 @@ Found a skill that should be in a bundle? Or want to create a new bundle? [Open
 
 ---
 
-_Last updated: March 2026 | Total Skills: 1,550+ | Total Bundles: 52_
+_Last updated: March 2026 | Total Skills: 1,569+ | Total Bundles: 52_

package/bundled-skills/docs/users/claude-code-skills.md

@@ -12,7 +12,7 @@ Install the library into Claude Code, then invoke focused skills directly in the
 
 ## Why use this repo for Claude Code
 
-- It includes 1,550+ skills instead of a narrow single-domain starter pack.
+- It includes 1,569+ skills instead of a narrow single-domain starter pack.
 - It supports the standard `.claude/skills/` path and the Claude Code plugin marketplace flow.
 - It also ships generated bundle plugins so teams can install focused packs like `Essentials` or `Security Developer` from the marketplace metadata.
 - It includes onboarding docs, bundles, and workflows so new users do not need to guess where to begin.

package/bundled-skills/docs/users/gemini-cli-skills.md

@@ -12,7 +12,7 @@ Install into the Gemini skills path, then ask Gemini to apply one skill at a tim
 
 - It installs directly into the expected Gemini skills path.
 - It includes both core software engineering skills and deeper agent/LLM-oriented skills.
-- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,550+ files.
+- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,569+ files.
 - It is useful whether you want a broad internal skill library or a single repo to test many workflows quickly.
 
 ## Install Gemini CLI Skills

package/bundled-skills/docs/users/getting-started.md

@@ -1,4 +1,4 @@
-# Getting Started with Antigravity Awesome Skills (V12.5.0)
+# Getting Started with Antigravity Awesome Skills (V12.7.0)
 
 **New here? This guide will help you supercharge your AI Agent in 5 minutes.**
 

package/bundled-skills/docs/users/kiro-integration.md

@@ -18,7 +18,7 @@ Kiro is AWS's agentic AI IDE that combines:
 
 Kiro's agentic capabilities are enhanced by skills that provide:
 
-- **Domain expertise** across 1,550+ specialized areas
+- **Domain expertise** across 1,569+ specialized areas
 - **Best practices** from Anthropic, OpenAI, Google, Microsoft, and AWS
 - **Workflow automation** for common development tasks
 - **AWS-specific patterns** for serverless, infrastructure, and cloud architecture

package/bundled-skills/docs/users/usage.md

@@ -14,7 +14,7 @@ If you came in through a **Claude Code** or **Codex** plugin instead of a full l
 
 When you ran `npx antigravity-awesome-skills` or cloned the repository, you:
 
-✅ **Downloaded 1,550+ skill files** to your computer (default: `~/.agents/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)
+✅ **Downloaded 1,569+ skill files** to your computer (default: `~/.agents/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)
 ✅ **Made them available** to your AI assistant  
 ❌ **Did NOT enable them all automatically** (they're just sitting there, waiting)
 
@@ -34,7 +34,7 @@ Bundles are **curated groups** of skills organized by role. They help you decide
 
 **Analogy:**
 
-- You installed a toolbox with 1,550+ tools (✅ done)
+- You installed a toolbox with 1,569+ tools (✅ done)
 - Bundles are like **labeled organizer trays** saying: "If you're a carpenter, start with these 10 tools"
 - You can either **pick skills from the tray** or install that tray as a focused marketplace bundle plugin
 
@@ -212,7 +212,7 @@ Let's actually use a skill right now. Follow these steps:
 
 ## Step 5: Picking Your First Skills (Practical Advice)
 
-Don't try to use all 1,550+ skills at once. Here's a sensible approach:
+Don't try to use all 1,569+ skills at once. Here's a sensible approach:
 
 If you want a tool-specific starting point before choosing skills, use:
 
@@ -343,7 +343,7 @@ Usually no, but if your AI doesn't recognize a skill:
 
 ### "Can I load all skills into the model at once?"
 
-No. Even though you have 1,550+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
+No. Even though you have 1,569+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
 
 The intended pattern is:
 

package/bundled-skills/docs/users/visual-guide.md

@@ -34,7 +34,7 @@ antigravity-awesome-skills/
 ├── 📄 CONTRIBUTING.md                  ← Contributor workflow
 ├── 📄 CATALOG.md                       ← Full generated catalog
 │
-├── 📁 skills/                          ← 1,550+ skills live here
+├── 📁 skills/                          ← 1,569+ skills live here
 │   │
 │   ├── 📁 brainstorming/
 │   │   └── 📄 SKILL.md                 ← Skill definition
@@ -47,7 +47,7 @@ antigravity-awesome-skills/
 │   │   └── 📁 2d-games/
 │   │       └── 📄 SKILL.md             ← Nested skills also supported
 │   │
-│   └── ... (1,550+ total)
+│   └── ... (1,569+ total)
 │
 ├── 📁 apps/
 │   └── 📁 web-app/                     ← Interactive browser
@@ -100,7 +100,7 @@ antigravity-awesome-skills/
 
 ```
                     ┌─────────────────────────┐
-                    │  1,550+ SKILLS          │
+                    │  1,569+ SKILLS          │
                     └────────────┬────────────┘
                                  │
         ┌────────────────────────┼────────────────────────┐
@@ -201,7 +201,7 @@ If you want a workspace-style manual install instead, cloning into `.agent/skill
 │   ├── 📁 brainstorming/                 │
 │   ├── 📁 stripe-integration/            │
 │   ├── 📁 react-best-practices/          │
-│   └── ... (1,550+ total)                │
+│   └── ... (1,569+ total)                │
 └─────────────────────────────────────────┘
 ```
 

package/bundled-skills/efficient-web-research/SKILL.md

@@ -0,0 +1,320 @@
+---
+name: efficient-web-research
+risk: safe
+description: >
+  Protocol for token-efficient web research. Use when accessing URLs, GitHub repos, or running search queries. Prevents full-page fetching waste.
+---
+
+# Efficient Web Research Skill
+
+A protocol for accessing web content in the most token-efficient, accurate, and structured way —
+using the right tool at the right depth, and stopping as soon as the question is answerable.
+
+---
+
+## Core Principle
+
+> **Fetch the minimum needed to answer. Skim before you dive. Stop when you can answer.**
+
+Every unnecessary fetch wastes tokens and adds noise. This skill enforces a layered approach
+where you escalate fetch depth only when shallower layers fail.
+
+---
+
+## Step 1 — Classify the Input
+
+Before fetching anything, identify what kind of input you received:
+
+| Input Type | Example | Go To |
+|---|---|---|
+| GitHub repo URL | `github.com/user/repo` | [GitHub Protocol](#github-protocol) |
+| Specific page URL | `docs.python.org/3/library/os` | [URL Protocol](#url-protocol) |
+| Topic / query (no URL) | "how does RAFT consensus work" | [Search Protocol](#search-protocol) |
+| Multiple URLs | List of links | [Multi-URL Protocol](#multi-url-protocol) |
+| PDF / file link | `.pdf`, `.txt`, `.md` URL | [File Protocol](#file-protocol) |
+
+---
+
+## GitHub Protocol
+
+Use when input is a GitHub URL (repo, file, PR, issue, etc.)
+
+### Step 1 — Parse the URL
+
+```
+github.com/{owner}/{repo}                → Repo root
+github.com/{owner}/{repo}/tree/{branch}  → Directory
+github.com/{owner}/{repo}/blob/{branch}/{path} → Single file
+github.com/{owner}/{repo}/issues/{n}     → Issue
+github.com/{owner}/{repo}/pull/{n}       → Pull request
+```
+
+### Step 2 — Use GitHub API (preferred over scraping)
+
+Always prefer the GitHub API. It returns clean JSON — no HTML parsing needed.
+
+```
+# Repo metadata (name, description, language, stars, topics)
+GET https://api.github.com/repos/{owner}/{repo}
+
+# File tree (see what files exist — very cheap)
+GET https://api.github.com/repos/{owner}/{repo}/git/trees/{ref}?recursive=1
+
+# Single file content (base64 encoded)
+GET https://api.github.com/repos/{owner}/{repo}/contents/{path}?ref={ref}
+
+# README only (usually enough to understand the repo)
+GET https://api.github.com/repos/{owner}/{repo}/readme
+```
+
+### Step 3 — Layered Fetch for Repos
+
+```
+Layer 1 (always do first):
+  → Fetch repo metadata + README only
+  → Can you answer the user's question now? YES → STOP. NO → continue.
+
+Layer 2 (only if needed):
+  → Fetch file tree to understand structure
+  → Identify the 1-3 most relevant files based on the question
+  → Can you answer now? YES → STOP. NO → continue.
+
+Layer 3 (last resort):
+  → Fetch specific relevant files only (never fetch all files)
+  → Prioritize: main entry point, config files, key modules
+```
+
+### Token Rules for GitHub
+
+- README alone answers ~70% of "what does this repo do" questions — always try it first
+- Never fetch more than 3 files in a single research turn
+- If a file exceeds ~300 lines, read only the top (imports + class/function signatures)
+- Decode base64 content from API before passing to context
+
+---
+
+## URL Protocol
+
+Use when the user gives a specific non-GitHub URL (docs, articles, blogs, etc.)
+
+### Step 1 — Assess the URL type
+
+| Site type | Likely works with | Notes |
+|---|---|---|
+| Static docs / MDN / ReadTheDocs | `read_url_content` | Fast, clean, cheap |
+| News articles / blogs | `read_url_content` | Usually fine |
+| SPAs / React/Next.js apps | `browser_subagent` | JS-rendered |
+| Auth-gated pages | `browser_subagent` | Needs login |
+| Raw GitHub files (raw.githubusercontent) | `read_url_content` | Direct text |
+
+### Step 2 — Layered Fetch
+
+```
+Layer 1 — Skim
+  → Fetch the URL with read_url_content
+  → Read only headings (H1, H2, H3) and first paragraph
+  → Does this page contain what the user needs? NO → try a different URL or search. YES → continue.
+
+Layer 2 — Targeted Extract
+  → If the page has anchor links (e.g. /docs/page#section), fetch with the anchor
+  → Extract only the relevant section (200–500 tokens max)
+  → Can you answer? YES → STOP.
+
+Layer 3 — Full Fetch
+  → Fetch full page, strip boilerplate (nav, footer, ads, cookie banners, sidebars)
+  → Cap at 2000 tokens. Summarize before passing to answer.
+
+Layer 4 — Browser Subagent (last resort only)
+  → Use ONLY if read_url_content returns empty, garbled, or JS-placeholder content
+  → Instruct subagent: "Navigate to [URL], wait for content to load, extract [specific section]"
+  → Do NOT use browser_subagent for static pages — it's expensive
+```
+
+### What to Strip from Fetched Pages
+
+Always remove before using fetched content:
+- Navigation menus and breadcrumbs
+- Cookie banners and GDPR notices
+- "Related articles" / "You might also like" blocks
+- Footer content (copyright, links)
+- Social share buttons
+- Ads and sponsored content
+
+Extract and keep:
+- Main article / documentation body
+- Code blocks
+- Tables with data
+- Numbered steps or procedures
+
+---
+
+## Search Protocol
+
+Use when the user gives a topic, question, or query — not a specific URL.
+
+### Step 1 — Sharpen the Query Before Searching
+
+Do NOT search the raw user query. Transform it first:
+
+```
+Raw: "how to deploy fastapi on aws"
+Sharpened: "fastapi AWS deployment tutorial 2024"
+
+Raw: "python async vs threads"
+Sharpened: "Python asyncio vs threading performance comparison"
+
+Raw: "best way to structure react project"
+Sharpened: "React project folder structure best practices"
+```
+
+**Query sharpening rules:**
+- Add specificity: version numbers, technology names, "tutorial" / "guide" / "comparison"
+- Add recency if relevant: current year
+- Remove filler words: "how do I", "what is the", "can you explain"
+- For code questions: add the language + framework name explicitly
+
+### Step 2 — Search and Select
+
+```
+1. Run search_web with the sharpened query
+2. Get results (titles + snippets)
+3. Scan titles + snippets ONLY — do not fetch yet
+4. Pick the TOP 1-2 most relevant results (max 3 in complex cases)
+5. Skip results from: forums (if docs exist), aggregator blogs, paywalled sites
+6. Prefer: official docs, GitHub repos, well-known tech blogs, academic sources
+```
+
+### Step 3 — Fetch Selected Results
+
+Apply the URL Protocol (above) to each selected URL.
+Process results one at a time — only fetch the second URL if the first didn't answer the question.
+
+### Token Rules for Search
+
+- Never read more than 3 URLs per search query
+- If the snippet already contains the answer → do NOT fetch the full page, use the snippet
+- For factual questions (dates, names, simple facts) → snippet is usually enough
+- For procedural questions (how to do X) → fetch 1 relevant page, targeted section only
+
+---
+
+## Multi-URL Protocol
+
+Use when the user provides a list of URLs to compare or summarize.
+
+```
+1. Skim all URLs first (Layer 1 fetch for each)
+2. Group by relevance to the user's question
+3. Deep-fetch only the most relevant 1-3 URLs
+4. Summarize each in 3-5 sentences before combining
+5. Never dump raw content from multiple pages — always summarize per-source first
+```
+
+---
+
+## File Protocol
+
+Use when URL points directly to a file (PDF, .txt, .md, .csv, etc.)
+
+- `.md` / `.txt` / `.csv` → `read_url_content` works directly, read full content
+- `.pdf` → Use browser_subagent or a PDF extraction tool; extract text only
+- `.json` / `.yaml` → `read_url_content`, parse structure, summarize schema + key values
+- Large files (>500 lines) → Read first 100 lines + last 20 lines + search for relevant sections
+
+---
+
+## Anti-Patterns (Never Do These)
+
+| Anti-pattern | Why it's bad | Do this instead |
+|---|---|---|
+| Fetching full page for a simple fact | Wastes 1000s of tokens | Use snippet or targeted anchor |
+| Using browser_subagent for static sites | Very expensive | Use read_url_content first |
+| Searching with the raw user query | Vague results | Sharpen query first |
+| Fetching 5+ search results | Token explosion | Max 3, stop when answered |
+| Dumping raw HTML into context | Noisy, wasteful | Always strip to Markdown |
+| Fetching "just in case" | Unnecessary tokens | Only fetch what's needed to answer |
+| Re-fetching the same URL | Redundant | Cache result in context, reuse |
+| Fetching entire GitHub repo | Extremely wasteful | README + targeted files only |
+
+---
+
+## Decision Flowchart (Quick Reference)
+
+```
+Input received
+│
+├─ GitHub URL?
+│   ├─ Fetch README + metadata via API
+│   ├─ Answered? → STOP
+│   ├─ Need more? → Fetch file tree, pick 1-3 files
+│   └─ Still need more? → Fetch specific files only
+│
+├─ Specific URL?
+│   ├─ Try read_url_content → skim headings
+│   ├─ Answered? → STOP
+│   ├─ Need more? → Targeted section fetch
+│   ├─ Still need more? → Full fetch, stripped
+│   └─ JS-rendered / broken? → browser_subagent (last resort)
+│
+├─ Topic/query?
+│   ├─ Sharpen query
+│   ├─ search_web → scan snippets
+│   ├─ Snippet enough? → Answer from snippet, STOP
+│   ├─ Need more? → Fetch top 1 result (targeted)
+│   └─ Still need more? → Fetch top 2nd result (targeted)
+│
+└─ List of URLs?
+    ├─ Skim all (Layer 1 each)
+    ├─ Deep fetch top 1-3 relevant ones
+    └─ Summarize per-source, then combine
+```
+
+---
+
+## Output Format Rules
+
+After fetching, structure your response as:
+
+```
+Source: [URL or "Web search for: query"]
+Summary: [2-5 sentences of what was found]
+Answer: [Direct answer to user's question]
+Confidence: [High / Medium / Low — based on source quality]
+```
+
+For multiple sources:
+```
+Source 1: ...
+Source 2: ...
+Combined Answer: ...
+```
+
+Never output:
+- Raw HTML fragments
+- Full page dumps
+- Unattributed information
+- More than needed to answer the question
+
+---
+
+## Token Budget Guide
+
+| Operation | Approximate token cost | When to use |
+|---|---|---|
+| GitHub README fetch | ~300–800 tokens | Always first for repos |
+| GitHub API metadata | ~200 tokens | Always for repos |
+| Skim (headings only) | ~100–200 tokens | Always first for URLs |
+| Targeted section fetch | ~300–600 tokens | When skim isn't enough |
+| Full page fetch (stripped) | ~1000–2000 tokens | Only when targeted fails |
+| browser_subagent | ~2000–5000 tokens | Last resort only |
+| Search snippet scan | ~300–500 tokens | Always before fetching |
+
+**Rule of thumb:** If you're about to spend >2000 tokens on a fetch, ask yourself if there's a cheaper path first.
+
+---
+
+## Limitations
+
+- **JavaScript Reliance**: Standard fetching may not fully render Single Page Applications (SPAs). You must fallback to `browser_subagent` for these, which is slower and more expensive.
+- **Paywalls & Protections**: This skill cannot bypass CAPTCHAs, bot protections (e.g., strict Cloudflare rules), or hard paywalls.
+- **GitHub API Limits**: Frequent GitHub API requests without authentication may hit rate limits.