菜单
Determines whether a challenge provides pre-existing artifacts (repos, starter code, APIs, designs) or is greenfield. Use when analyzing a challenge specification to identify starting-point artifacts, their types, URLs, and existing technology present in provided code.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/topcoder-platform/tc-ai-api --skill codebase-detection命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | codebase-detection |
| description | Determines whether a challenge provides pre-existing artifacts (repos, starter code, APIs, designs) or is greenfield. Use when analyzing a challenge specification to identify starting-point artifacts, their types, URLs, and existing technology present in provided code. |
| metadata | {"author":"topcoder","version":"1.0","concern":"artifact-detection","priority":"high"} |
Determine whether the challenge provides ANY pre-existing artifacts that serve as a starting point for submitters.
Look for references to:
Set isGreenfield to true when the challenge requires building the
submission from scratch and provides no code artifacts to build upon.
Set isGreenfield to false ONLY when the challenge provides actual
code, templates, or starter projects that the submitter must fork, clone,
extend, or modify.
URLs and references in the spec often point to external resources the submission must consume or interact with, not code to build upon:
https://api.example.com/v5)
are external dependencies, NOT starter code.| Spec language | isGreenfield | Reasoning |
|---|---|---|
| "build a CLI app that calls https://api.example.com" | true | External API to consume, no code given |
| "see https://github.com/org/repo for API docs" | true | Reference link, not code to extend |
| "fork https://github.com/org/repo and add features" | false | Explicit instruction to extend code |
| "use the provided starter template in the attachment" | false | Starter code artifact provided |
| "extend the existing NestJS API in the repository" | false | Building on existing code |
Key rule: If no spec language tells the submitter to fork, clone,
extend, or modify a specific codebase, default to isGreenfield = true.
For each artifact found, identify its type:
| Type | Description |
|---|---|
repository | Full Git repository to fork/clone |
starter_code | Partial code that submitters extend |
boilerplate | Project scaffold / template |
documentation | Written specs, architecture docs |
api_spec | Swagger/OpenAPI/Postman definitions |
design | Figma, Zeplin, wireframes, mockups |
dataset | CSV, JSON, database dumps, sample data |
database_dump | SQL dump or migration files |
config | Environment templates, Docker configs |
library | Required packages or internal libraries |
other | Anything not fitting above categories |
Note which programming languages and frameworks are ALREADY present in the existing codebase. These may differ from what the challenge requirements ask for.
Example: The repo is a NestJS project, but the challenge asks to add a React
frontend. Existing tech = ["TypeScript", "NestJS", "Prisma"].
Write a concise summary of the starting-point status:
Good examples:
Bad examples: