菜单
Explains a repository's purpose, structure, setup and run commands, key scripts, and the first files worth opening. Use when the user wants to understand a new repo or codebase — "what does this project do", "how do I get started", "give me a codebase overview", "onboard me to this repo".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Answers a question grounded in the selected text or visible page, researching further when the page falls short, always evidence-backed and never invented. Use when the user highlights a passage or is on a page and asks "what does this mean", "answer this", "where does it say", or any who/what/why/how question about that content.
Turns REST API documentation into a runnable curl, fetch, or code example with required headers, request body, and placeholders for secrets. Use when the user wants to generate a request from API docs, an endpoint, or a Swagger/OpenAPI spec — "give me a curl for this", "show a fetch example", "how do I call this API".
Translates selected text and explains the idioms, cultural nuance, key terms, and phrasing that should not be read literally. Use when the user says "translate this", "in Spanish/French/Japanese/etc.", "what does this mean", "explain this phrase", or wants foreign-language text rendered with the context behind it.
Turns an event page, calendar invite, email, or notes into key details, an agenda, a preparation checklist, and follow-up reminders. Use when the user wants to prepare for a meeting, event, or appointment, or asks for meeting prep, an agenda, or a prep checklist before an upcoming event.
Writes captions, accessibility alt text, and short image or page descriptions tailored to the visible content and audience. Use when the user asks to "describe this image", "write alt text", "caption this", or needs screen reader text, a11y descriptions, image descriptions, or social captions.
Explains a visible chart by identifying axes, trends, outliers, and the practical takeaway while flagging missing context. Use when the user shares a chart, graph, plot, or data visualization — bar, line, pie, scatter — and asks what it shows, means, or whether the data supports a decision.
| name | repo-onboarder |
| description | Explains a repository's purpose, structure, setup and run commands, key scripts, and the first files worth opening. Use when the user wants to understand a new repo or codebase — "what does this project do", "how do I get started", "give me a codebase overview", "onboard me to this repo". |
| author | surfmind |
| metadata | {"icon":"Code","tags":["code","learning"]} |
Read a repository's page, README, file tree, and package metadata to explain what it does and how to get it running — purpose, architecture, setup and run commands, key scripts, environment needs, and the first files worth opening. Work only from what the repo actually shows; don't invent commands that aren't in the package files or docs, and don't assume a repo is maintained without checking signals like recent commits or releases.
package.json, Makefile, pyproject.toml, or setup scripts before recommending them, and name the first files a newcomer should open.Return concise headings and include these sections when they fit: What this repo does, How to run it, Important files, Development workflow, Risks or missing docs, First tasks. Separate supported facts from assumptions and recommendations. Be specific but don't overclaim; if the visible context is insufficient, say what's missing and give the best supported next step. Respond in the same language as the user's request.
Repo (a small Node.js CLI):
Root has
package.json,src/index.js,src/parse.js,README.md(a one-line description andnpm install), and atest/folder.package.jsonscripts:"start": "node src/index.js","test": "vitest".
Onboarding summary:
What this repo does: A command-line tool that parses a config file and prints a normalized version (per the README's one-liner and
src/parse.js).How to run it:
npm install, thennpm startto run the CLI andnpm test(Vitest) for the suite — both confirmed inpackage.jsonscripts.Important files:
src/index.js(CLI entry and arg handling),src/parse.js(the core parsing logic),test/(behavior examples worth reading first).Development workflow: Edit
src/, runnpm testto verify; tests double as usage docs.Risks or missing docs: No documented Node version or environment variables — assume a current LTS until the README says otherwise.
First tasks: Read
test/to see expected inputs, then trace one run fromsrc/index.jsintosrc/parse.js.