GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
A skill your agent uses when the my-pi-agent monorepo needs exploratory technical comparison or recommendation: 技术调研、方案对比、选型、tradeoff、research、deepresearch、deep research、深度调研、深度分析、可行性评估、next step 建议。
Install Technical Research
$ npx skills add skuramatata/my-pi-agent --skill technical-research -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install skuramatata/my-pi-agent technical-research --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/skuramatata/my-pi-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.opencode/skills/technical-research .claude/skills/technical-research && 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 "technical-research" agent skill from https://github.com/skuramatata/my-pi-agent/tree/main/.opencode/skills/technical-research into .claude/skills/technical-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-research", 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/skuramatata/my-pi-agent/tree/main/.opencode/skills/technical-researchType 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 skuramatata/my-pi-agent --skill technical-research -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install skuramatata/my-pi-agent technical-research --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/skuramatata/my-pi-agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.opencode/skills/technical-research .agents/skills/technical-research && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "technical-research" agent skill from https://github.com/skuramatata/my-pi-agent/tree/main/.opencode/skills/technical-research into .agents/skills/technical-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-research", 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 skuramatata/my-pi-agent --skill technical-research -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install skuramatata/my-pi-agent technical-research --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/skuramatata/my-pi-agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.opencode/skills/technical-research .cursor/skills/technical-research && 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 "technical-research" agent skill from https://github.com/skuramatata/my-pi-agent/tree/main/.opencode/skills/technical-research into .cursor/skills/technical-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-research", 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/skuramatata/my-pi-agent.git --path .opencode/skills/technical-research--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 skuramatata/my-pi-agent --skill technical-research -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install skuramatata/my-pi-agent technical-research --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/skuramatata/my-pi-agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.opencode/skills/technical-research .gemini/skills/technical-research && 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 "technical-research" agent skill from https://github.com/skuramatata/my-pi-agent/tree/main/.opencode/skills/technical-research into .gemini/skills/technical-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-research", 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 skuramatata/my-pi-agent technical-researchInstalls 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 skuramatata/my-pi-agent --skill technical-research -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/skuramatata/my-pi-agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/.opencode/skills/technical-research .github/skills/technical-research && 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 "technical-research" agent skill from https://github.com/skuramatata/my-pi-agent/tree/main/.opencode/skills/technical-research into .github/skills/technical-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-research", 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 skuramatata/my-pi-agent --skill technical-research -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install skuramatata/my-pi-agent technical-research --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/skuramatata/my-pi-agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.opencode/skills/technical-research .opencode/skills/technical-research && 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 "technical-research" agent skill from https://github.com/skuramatata/my-pi-agent/tree/main/.opencode/skills/technical-research into .opencode/skills/technical-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-research", 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
technical-research- GitHub stars
- 114
- Token cost
- ~932 tokens
- SKILL.md length
- 458 words
- Files
- 1
- Skills in repo
- 24
- Repo updated
- First seen
- Licence
- None found
At a glance
A skill your agent uses when the my-pi-agent monorepo needs exploratory technical comparison or recommendation: 技术调研、方案对比、选型、tradeoff、research、deepresearch、deep research、深度调研、深度分析、可行性评估、next step 建议。
- Works in 4 steps: Frame the decision. → Gather evidence. → Compare 2-4 real options. → …
- The my-pi-agent monorepo needs exploratory technical comparison
- SKILL.md covers Workflow, Output Contract, Deepresearch Contract and Guardrails
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Technical Research is an agent skill from skuramatata/my-pi-agent. Use when the my-pi-agent monorepo needs exploratory technical comparison or recommendation: 技术调研、方案对比、选型、tradeoff、research、deepresearch、deep research、深度调研、深度分析、可行性评估、next step 建议。
Its SKILL.md is about 930 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 Research & Science, covering Deep research and Monorepo tooling.
When your agent uses it
- The my-pi-agent monorepo needs exploratory technical comparison
- Recommendation: 技术调研、方案对比、选型、tradeoff、research、deepresearch、deep research、深度调研、深度分析、可行性评估、next step 建议
Example prompts
- “/technical-research”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Frame the decision.
- Gather evidence.
- Compare 2-4 real options.
- Recommend one path.
What it can do on your machine
Read from SKILL.md and the folder at commit ed83ff1. 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
Technical Research loads about 932 tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 458 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 458 words (~932 tokens).
“Use this skill when the task needs a decision between options, not just a description of one tool or library.”
- name
- technical-research
Files
Just SKILL.md in .opencode/skills/technical-research of skuramatata/my-pi-agent.
Open the folder on GitHubat commit ed83ff1
Compare with similar skills
Technical Research 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 |
|---|---|---|---|---|---|---|
| Technical Research this skillskuramatata/my-pi-agent | 114 | — | ~932 | Automated safety check: Pass | None | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Tbdjlevy/strif | 131 | — | ~3.5k | Automated safety check: Pass | MIT | |
| Sdd Researchmadebyaris/spec-kit-command-cursor | 198 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Inno Code SurveyLigphiDonk/Oh-my--paper | 738 | — | ~3.6k | Automated safety check: Pass | MIT | |
| Best Practicessd0xdev/sd0x-harness | 192 | — | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
Tbd
jlevy/strif
Git-native issue tracking (beads), coding guidelines, knowledge injection, and spec-driven planning for AI agents.
Sdd Research
madebyaris/spec-kit-command-cursor
Pattern investigation and technical research before specification.
Inno Code Survey
LigphiDonk/Oh-my--paper
Finds and clones missing code repositories for a chosen research idea, then writes a survey that maps academic concepts to their implementations.
Best Practices
sd0xdev/sd0x-harness
Industry best practices conformance audit with mandatory adversarial debate.
Deep Research Workflow
TokenRhythm/opensquilla
Runs multi-round research in three stages with a persisted state file, evidence tracking and a long-form report with per-claim citations.
More from skuramatata/my-pi-agent
All 24 skills in this repoDocumentation And Adrs
skuramatata/my-pi-agent
A skill your agent uses when my-pi-agent changes architecture, runtime/workflow/executor behavior, prompt-engine contracts, memory/state, channel behavior, MCP/OpenCode config, README content, or…
Documentation And Adrs
skuramatata/my-pi-agent
A skill your agent uses when my-pi-agent changes architecture, orchestration, execution, prompt-engine, memory, Feishu/channel behavior, skill scope, verifier semantics, public commands, or…
Openspec Apply Change
skuramatata/my-pi-agent
A skill your agent uses when the user wants to implement, continue, or work through tasks from an existing OpenSpec change.
Openspec Propose
skuramatata/my-pi-agent
A skill your agent uses when the user wants to propose a new OpenSpec change and generate proposal, design, specs, and tasks before implementation.
Code Review
skuramatata/my-pi-agent
A skill your agent uses when reviewing a my-pi-agent change before merge or handoff: 代码审查、review、PR review、改动盘点、merge readiness、风险找漏、提交前质量检查。
Code Review And Quality
skuramatata/my-pi-agent
A skill your agent uses when reviewing my-pi-agent changes, PRs, worker output, verifier repair results, prompt/skill edits, Feishu channel changes, or shared runtime refactors.
Related
Categories
Questions about Technical Research
What does Technical Research do?
A skill your agent uses when the my-pi-agent monorepo needs exploratory technical comparison or recommendation: 技术调研、方案对比、选型、tradeoff、research、deepresearch、deep research、深度调研、深度分析、可行性评估、next step 建议。. Technical Research is an agent skill from skuramatata/my-pi-agent.
When should I use Technical Research?
Technical Research fits situations like: the my-pi-agent monorepo needs exploratory technical comparison; recommendation: 技术调研、方案对比、选型、tradeoff、research、deepresearch、deep research、深度调研、深度分析、可行性评估、next step 建议.
How do I install Technical Research in Claude Code?
Run `npx skills add skuramatata/my-pi-agent --skill technical-research -a claude-code`. Or copy the skill folder (.opencode/skills/technical-research in skuramatata/my-pi-agent) into .claude/skills/technical-research in your project. Claude Code loads it when a task matches its description.
How do I install Technical Research in Codex?
Run `npx skills add skuramatata/my-pi-agent --skill technical-research -a codex`. Or copy the skill folder (.opencode/skills/technical-research in skuramatata/my-pi-agent) into .agents/skills/technical-research in your project. Codex loads it when a task matches its description.
Can I use Technical Research 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 skuramatata/my-pi-agent --skill technical-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/technical-research, .gemini/skills/technical-research, .github/skills/technical-research and .opencode/skills/technical-research in your project.
What does Technical Research need to run?
SKILL.md names no scripts, command-line tools or credentials: Technical Research is instructions for the agent only.
Does Technical Research 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 Technical Research 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 Technical Research use?
No licence was found for Technical Research or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Technical Research use?
About 932 tokens (SKILL.md is roughly 3.7k 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 Technical Research?
Skills that share tags, products or a category with Technical Research: GitHub Deep Research (bytedance/deer-flow, 84k stars), Tbd (jlevy/strif, 131 stars), Sdd Research (madebyaris/spec-kit-command-cursor, 198 stars) and Inno Code Survey (LigphiDonk/Oh-my--paper, 738 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Technical Research?
skuramatata (a GitHub user) maintains it in skuramatata/my-pi-agent, which has 114 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on July 10, 2026.
Source: skuramatata/my-pi-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.