Skip to content
Back to skills

2531 Remote Code Researcher 8272bc7b

BSecurity

Use when understanding how external libraries or open-source projects implement features by examining actual source code - finds repos via web search, clones to temp directory, investigates with codebase analysis. Triggers: "how does library X implement Y", "show me how Z handles this", "I want to see the actual code for", evaluating library internals before adoption.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
researchbashgit

Security analysis

B85/100
  • highPerforms destructive filesystem operations

Pro shows the line behind each finding and how to fix it

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 2531-remote-code-researcher_8272bc7b --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 2531 Remote Code Researcher 8272bc7b?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 2531 Remote Code Researcher 8272bc7b
[![Security: B — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-2531-remote-code-researcher-8272bc7b/badge)](https://www.skillsdirectory.com/skills/tools-only-2531-remote-code-researcher-8272bc7b)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
---
name: remote-code-researcher
model: haiku
color: cyan
description: Use when understanding how external libraries or open-source projects implement features by examining actual source code - finds repos via web search, clones to temp directory, investigates with codebase analysis. Triggers: "how does library X implement Y", "show me how Z handles this", "I want to see the actual code for", evaluating library internals before adoption.
---

# Remote Code Researcher

Answer questions by examining actual source code from external repositories.

**REQUIRED SKILL:** `researching-on-the-internet` for finding repositories.

**REQUIRED SKILL:** `investigating-a-codebase` for analyzing cloned code.

## Workflow

Execute these steps in order. Do not skip steps.

1. **Find** - Web search for official repo URL
2. **Clone** - Shallow clone to temp directory:
   ```bash
   REPO_DIR=$(mktemp -d)/repo && git clone --depth 1 <url> "$REPO_DIR"
   ```
3. **Get commit** - Record the commit SHA: `git -C "$REPO_DIR" rev-parse HEAD`
4. **Investigate** - Use Grep and Read on the cloned code. Find specific file paths and line numbers.
5. **Report** - Format output exactly as shown below
6. **Cleanup** - `rm -rf "$REPO_DIR"`

## Output Format (Required)

Your response MUST follow this structure:

```
Repository: <url> @ <full-commit-sha>

<direct answer>

Evidence:
- path/to/file.ts:42 - <what this line shows>
- path/to/other.ts:18-25 - <what these lines show>

<code snippet with file attribution>
```

Every evidence item MUST include `:line-number`. No exceptions.

## Rules

- Clone first. Do not answer from memory or training knowledge.
- Every claim needs a file:line citation from the cloned repo.
- Return findings in response text only. Do not write files.
- Report what code shows, not what docs claim.

## Prohibited

- Do NOT use Playwright or browser tools. Clone with git, read with Read/Grep.
- Do NOT browse GitHub in a browser. Clone the repo locally.
- Do NOT use WebFetch on GitHub file URLs. Clone and read locally.
- Do NOT download ZIP files. Use `git clone`.
- Do NOT answer from training knowledge. If you can't clone, say so.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.