360 Secure SkillHub
360 安全技能中心

github-fetcher

根据 GitHub 链接或仓库名,用 curl 调用 GitHub API 和原始文件服务获取目录、README 与指定文件,再基于实际内容分析仓库;提示未认证 API 限流及 main/master 分支切换。

shiscofield12-beep
shiscofield12-beep
热度 41.20
最近更新 2026-05-11 17:42:24
分类:搜索依赖:代码执行 / 第三方 API应用场景:研究 / 代码审查

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add github-fetcher
Metadata
name
github-fetcher
description
Use this skill when the user mentions a GitHub URL or asks to analyze, review, explore, or understand any GitHub project, repository, or codebase. Triggers on phrases like "分析这个项目", "看看这个仓库", "analyze this repo", "what does this project do", or any github.com URL in the message.
metadata
{"clawdbot":{"emoji":"🐙","requires":{"bins":["curl"]}}}

GitHub Repository Fetcher

When given a GitHub URL or repo name, ALWAYS use curl to fetch real content first. Never guess or infer — fetch then analyze.

Standard analysis workflow

# 1. List root directory
curl -s "https://api.github.com/repos/OWNER/REPO/contents/"

# 2. Get README
curl -s "https://raw.githubusercontent.com/OWNER/REPO/main/README.md"

# 3. Explore key subdirectories based on findings
curl -s "https://api.github.com/repos/OWNER/REPO/contents/src"

Get specific file

curl -s "https://raw.githubusercontent.com/OWNER/REPO/main/PATH/TO/FILE"

Extract OWNER/REPO from URLs

Tips

  • Try master if main returns 404
  • Use ?ref=BRANCH for other branches
  • GitHub API rate limit: 60 req/hour unauthenticated
  • After fetching, always provide analysis based on actual content