Imaging Data Commons
K-Dense-AI/scientific-agent-skills
Queries and downloads public cancer imaging data from NCI Imaging Data Commons.
Investigate application or repository source code with searchfile and readfile to explain behavior, trace root causes of runtime or query errors, and answer with precise file citations.
Install Source Code Inspection
$ npx skills add FrankChen021/datastoria --skill source-code-inspection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install FrankChen021/datastoria source-code-inspection --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/FrankChen021/datastoria.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/skills/source-code-inspection .claude/skills/source-code-inspection && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "source-code-inspection" agent skill from https://github.com/FrankChen021/datastoria/tree/master/resources/skills/source-code-inspection into .claude/skills/source-code-inspection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "source-code-inspection", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/FrankChen021/datastoria/tree/master/resources/skills/source-code-inspectionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add FrankChen021/datastoria --skill source-code-inspection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install FrankChen021/datastoria source-code-inspection --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FrankChen021/datastoria.git skills-src && mkdir -p .agents/skills && cp -r skills-src/resources/skills/source-code-inspection .agents/skills/source-code-inspection && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "source-code-inspection" agent skill from https://github.com/FrankChen021/datastoria/tree/master/resources/skills/source-code-inspection into .agents/skills/source-code-inspection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "source-code-inspection", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FrankChen021/datastoria --skill source-code-inspection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install FrankChen021/datastoria source-code-inspection --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FrankChen021/datastoria.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/resources/skills/source-code-inspection .cursor/skills/source-code-inspection && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "source-code-inspection" agent skill from https://github.com/FrankChen021/datastoria/tree/master/resources/skills/source-code-inspection into .cursor/skills/source-code-inspection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "source-code-inspection", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/FrankChen021/datastoria.git --path resources/skills/source-code-inspection--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add FrankChen021/datastoria --skill source-code-inspection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install FrankChen021/datastoria source-code-inspection --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FrankChen021/datastoria.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/resources/skills/source-code-inspection .gemini/skills/source-code-inspection && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "source-code-inspection" agent skill from https://github.com/FrankChen021/datastoria/tree/master/resources/skills/source-code-inspection into .gemini/skills/source-code-inspection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "source-code-inspection", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install FrankChen021/datastoria source-code-inspectionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add FrankChen021/datastoria --skill source-code-inspection -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/FrankChen021/datastoria.git skills-src && mkdir -p .github/skills && cp -r skills-src/resources/skills/source-code-inspection .github/skills/source-code-inspection && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "source-code-inspection" agent skill from https://github.com/FrankChen021/datastoria/tree/master/resources/skills/source-code-inspection into .github/skills/source-code-inspection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "source-code-inspection", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FrankChen021/datastoria --skill source-code-inspection -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install FrankChen021/datastoria source-code-inspection --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FrankChen021/datastoria.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/resources/skills/source-code-inspection .opencode/skills/source-code-inspection && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "source-code-inspection" agent skill from https://github.com/FrankChen021/datastoria/tree/master/resources/skills/source-code-inspection into .opencode/skills/source-code-inspection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "source-code-inspection", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
source-code-inspection- GitHub stars
- 327
- Token cost
- ~453 tokens
- SKILL.md length
- 225 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Investigate application or repository source code with searchfile and readfile to explain behavior, trace root causes of runtime or query errors, and answer with precise file citations.
- Works in 5 steps: Use search_file first to locate relevant… → Use read_file only for targeted… → Prefer narrow, iterative reads: search… → …
- Tasks that involve Citation management
- SKILL.md covers When To Use, Workflow, Citation Format and Response Style
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Source Code Inspection is an agent skill from FrankChen021/datastoria. Investigate application or repository source code with searchfile and readfile to explain behavior, trace root causes of runtime or query errors, and answer with precise file citations.
Its SKILL.md is about 450 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Databases, covering Citation management and Root cause analysis. It works with SQL. The repository describes itself as: AI-native ClickHouse console for your cluster diagnostics and query generation, optimization and data visualization.
When your agent uses it
- Tasks that involve Citation management
- Tasks that involve Root cause analysis
Example prompts
- “/source-code-inspection”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Use search_file first to locate relevant files and line numbers before reading content.
- Use read_file only for targeted sections; do not read entire files or large ranges.
- Prefer narrow, iterative reads: search identifiers, function names, or error strings, then expand only when necessary.
- Do not claim to have reviewed code that was not loaded with tools in this conversation.
- If no matches found, refine the search and retry before giving up.
What it can do on your machine
Read from SKILL.md and the folder at commit d0859a2. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Source Code Inspection loads about 453 tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 225 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 225 words (~453 tokens).
“Use this skill when the user wants to:”
- name
- source-code-inspection
- metadata.author
- DataStoria
- metadata.tools
- search_file, read_file
Files
Just SKILL.md in resources/skills/source-code-inspection of FrankChen021/datastoria.
Open the folder on GitHubat commit d0859a2
Compare with similar skills
Source Code Inspection next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Source Code Inspection this skillFrankChen021/datastoria | 327 | — | ~453 | Automated safety check: Pass | Custom licence | |
| Imaging Data CommonsK-Dense-AI/scientific-agent-skills | 48k | 1 repos | ~7.8k | Automated safety check: Pass | MIT | |
| Analyze Issueapache/shardingsphere | 21k | — | ~6.5k | Automated safety check: Pass | Apache-2.0 | |
| Logfire Querypydantic/skills | 140 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Bigquery Troubleshootinggoogle/skills | 21k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| Impact TracePrismer-AI/PrismerCloud | 1.6k | — | ~1.5k | Automated safety check: Notes | MIT |
Similar skills
Analyze Issue
apache/shardingsphere
Used to analyze Apache ShardingSphere community issues. An agent skill from apache/shardingsphere.
- Official
Logfire Query
pydantic/skills
Query and analyze Logfire telemetry data — traces, logs, spans, metrics, summaries, and SQL results.
- Official
Bigquery Troubleshooting
google/skills
Provides diagnostic workflows and step-by-step root-cause analysis procedures for actively broken, failing, or slow BigQuery jobs, execution graph and query plan stage bottlenecks, system…
Impact Trace
Prismer-AI/PrismerCloud
For a change point (function / type / endpoint / SQL column), enumerate its real blast radius across six dimensions with a grep citation per row, then derive the regression test scope.
- Official
Investigating Logs
PostHog/posthog
Investigate logs in a PostHog project: verify a service or deployment is healthy, explain an error spike, triage an incident, or understand what a log stream is saying.
More from FrankChen021/datastoria
Clickhouse System Queries
FrankChen021/datastoria
Query ClickHouse system tables to inspect query logs, monitor cluster health, check replication status, and analyze slow queries.
Visualization
FrankChen021/datastoria
Rules for charts and visualization. An agent skill from FrankChen021/datastoria.
Diagnose Clickhouse Errors
FrankChen021/datastoria
Diagnose ClickHouse runtime query failures when the user wants database-level cause and fix guidance from an error or numeric error code, not source-code root cause analysis.
SQL Expert
FrankChen021/datastoria
Expert system for generating, validating, and optimizing ClickHouse SQL.
Diagnose Clickhouse Clusters
FrankChen021/datastoria
Diagnose ClickHouse cluster health and provide concrete remediation.
Optimize Clickhouse SQL
FrankChen021/datastoria
Optimize slow queries, analyze SQL performance, and collect evidence for expensive workloads.
Related
Works with
Questions about Source Code Inspection
What does Source Code Inspection do?
Investigate application or repository source code with searchfile and readfile to explain behavior, trace root causes of runtime or query errors, and answer with precise file citations. Source Code Inspection is an agent skill from FrankChen021/datastoria. Investigate application or repository source code with searchfile and readfile to explain behavior, trace root causes of runtime or query errors, and answer with precise file citations.
When should I use Source Code Inspection?
Source Code Inspection fits situations like: tasks that involve Citation management; tasks that involve Root cause analysis.
How do I install Source Code Inspection in Claude Code?
Run `npx skills add FrankChen021/datastoria --skill source-code-inspection -a claude-code`. Or copy the skill folder (resources/skills/source-code-inspection in FrankChen021/datastoria) into .claude/skills/source-code-inspection in your project. Claude Code loads it when a task matches its description.
How do I install Source Code Inspection in Codex?
Run `npx skills add FrankChen021/datastoria --skill source-code-inspection -a codex`. Or copy the skill folder (resources/skills/source-code-inspection in FrankChen021/datastoria) into .agents/skills/source-code-inspection in your project. Codex loads it when a task matches its description.
Can I use Source Code Inspection in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FrankChen021/datastoria --skill source-code-inspection -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/source-code-inspection, .gemini/skills/source-code-inspection, .github/skills/source-code-inspection and .opencode/skills/source-code-inspection in your project.
What does Source Code Inspection need to run?
SKILL.md names no scripts, command-line tools or credentials: Source Code Inspection is instructions for the agent only.
Does Source Code Inspection access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Source Code Inspection safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Source Code Inspection use?
Source Code Inspection has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Source Code Inspection use?
About 453 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Source Code Inspection?
Skills that share tags, products or a category with Source Code Inspection: Imaging Data Commons (K-Dense-AI/scientific-agent-skills, 48k stars), Analyze Issue (apache/shardingsphere, 21k stars), Logfire Query (pydantic/skills, 140 stars) and Bigquery Troubleshooting (google/skills, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Source Code Inspection?
FrankChen021 (a GitHub user) maintains it in FrankChen021/datastoria, which has 327 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on July 21, 2026.
Source: FrankChen021/datastoria on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.