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.
Research-brief + claim-record discipline for delegated or AI-assisted research work.
Install Credible Claims
$ npx skills add pedrohcgs/claude-code-my-workflow --skill credible-claims -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pedrohcgs/claude-code-my-workflow credible-claims --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/pedrohcgs/claude-code-my-workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/credible-claims .claude/skills/credible-claims && 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 "credible-claims" agent skill from https://github.com/pedrohcgs/claude-code-my-workflow/tree/main/.claude/skills/credible-claims into .claude/skills/credible-claims/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "credible-claims", 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/pedrohcgs/claude-code-my-workflow/tree/main/.claude/skills/credible-claimsType 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 pedrohcgs/claude-code-my-workflow --skill credible-claims -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pedrohcgs/claude-code-my-workflow credible-claims --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pedrohcgs/claude-code-my-workflow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/credible-claims .agents/skills/credible-claims && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "credible-claims" agent skill from https://github.com/pedrohcgs/claude-code-my-workflow/tree/main/.claude/skills/credible-claims into .agents/skills/credible-claims/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "credible-claims", 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 pedrohcgs/claude-code-my-workflow --skill credible-claims -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pedrohcgs/claude-code-my-workflow credible-claims --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pedrohcgs/claude-code-my-workflow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/credible-claims .cursor/skills/credible-claims && 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 "credible-claims" agent skill from https://github.com/pedrohcgs/claude-code-my-workflow/tree/main/.claude/skills/credible-claims into .cursor/skills/credible-claims/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "credible-claims", 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/pedrohcgs/claude-code-my-workflow.git --path .claude/skills/credible-claims--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 pedrohcgs/claude-code-my-workflow --skill credible-claims -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pedrohcgs/claude-code-my-workflow credible-claims --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pedrohcgs/claude-code-my-workflow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/credible-claims .gemini/skills/credible-claims && 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 "credible-claims" agent skill from https://github.com/pedrohcgs/claude-code-my-workflow/tree/main/.claude/skills/credible-claims into .gemini/skills/credible-claims/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "credible-claims", 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 pedrohcgs/claude-code-my-workflow credible-claimsInstalls 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 pedrohcgs/claude-code-my-workflow --skill credible-claims -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pedrohcgs/claude-code-my-workflow.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/credible-claims .github/skills/credible-claims && 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 "credible-claims" agent skill from https://github.com/pedrohcgs/claude-code-my-workflow/tree/main/.claude/skills/credible-claims into .github/skills/credible-claims/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "credible-claims", 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 pedrohcgs/claude-code-my-workflow --skill credible-claims -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pedrohcgs/claude-code-my-workflow credible-claims --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pedrohcgs/claude-code-my-workflow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/credible-claims .opencode/skills/credible-claims && 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 "credible-claims" agent skill from https://github.com/pedrohcgs/claude-code-my-workflow/tree/main/.claude/skills/credible-claims into .opencode/skills/credible-claims/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "credible-claims", 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
credible-claims- GitHub stars
- 1.7k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 495 words
- Files
- 1
- Skills in repo
- 59
- Repo updated
- First seen
- Licence
- MIT
At a glance
Research-brief + claim-record discipline for delegated or AI-assisted research work.
- Works in 3 steps: Delegate only after inputs, boundaries,… → Require evidence, not confident… → Escalate anything that changes the…
- Starting any substantive research task
- SKILL.md covers Three standing rules, The research brief (before…, The claim record (during/after… and Reporting language, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Credible Claims is an agent skill from pedrohcgs/claude-code-my-workflow. Research-brief + claim-record discipline for delegated or AI-assisted research work. Use when starting any substantive research task or long autonomous run (write the brief first), and when reporting results that will support a claim in a paper or decision (produce the claim record). Keeps faster execution from being confused with credible evidence.
Its SKILL.md is about 1.1k 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. The repository describes itself as: A ready-to-fork Claude Code template for academics using LaTeX/Beamer + R. Multi-agent review, quality gates, adversarial QA, and replication protocols. The licence is MIT.
When your agent uses it
- Starting any substantive research task
- Long autonomous run (write the brief first)
- When reporting results that will support a claim in a paper
- Decision (produce the claim record)
Example prompts
- “/credible-claims”
Requirements
- Pre-approved tools (allowed-tools): Read, Grep, Glob, Write
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Delegate only after inputs, boundaries, and completion criteria are clear. No open-ended "make it better" runs.
- Require evidence, not confident conclusions. Every delegated task returns inspectable evidence: locations, diffs, diagnostics, counts…
- Escalate anything that changes the economic object, the identifying assumptions, the inferential procedure, or the reporting language…
What it can do on your machine
Read from SKILL.md and the folder at commit ae72617. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepGlobWrite
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
Credible Claims loads about 1.1k tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 495 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
The full file from pedrohcgs/claude-code-my-workflow at commit ae72617, republished under its MIT licence (© pedrohcgs). 495 words, ~1,087 tokens.
Download SKILL.mdSave it as
.claude/skills/credible-claims/SKILL.md (or your agent's skills folder).- name
- credible-claims
- description
- Research-brief + claim-record discipline for delegated or AI-assisted research work. Use when starting any substantive research task or long autonomous run (write the brief first), and when reporting results that will support a claim in a paper or decision (produce the claim record). Keeps faster execution from being confused with credible evidence.
- allowed-tools
- Read, Grep, Glob, Write
- metadata.protocol
- bounded-delegation
Credible claims: the brief before, the record after
Cheaper generation increases demand for scarce validation. The fix is two lightweight artifacts: a research brief that constrains what the system may do, and a claim record that constrains what may be reported. Applies to agents, workflows, sims, proof patches, data construction — anything delegated.
Three standing rules
- Delegate only after inputs, boundaries, and completion criteria are clear. No open-ended "make it better" runs.
- Require evidence, not confident conclusions. Every delegated task returns inspectable evidence: locations, diffs, diagnostics, counts, failing cases, logs — never just "done/looks fine."
- Escalate anything that changes the economic object, the identifying assumptions, the inferential procedure, or the reporting language. Those decisions return to the researcher (the user), always. A standing user ruling counts as a returned decision; record it.
The research brief (before execution)
One short block, written before launching the work:
- Question / target: what exactly is being estimated, proved, built.
- Completion: what counts as done; what results would not answer the question.
- Prohibited substitutions: what the system may not silently change (estimand, sample, assumptions, statement of a theorem, benchmark spec).
- Known failure modes: what tends to go wrong here; the checks matched to each.
- Required evidence: what must come back (numbers, locations, diffs, diagnostics).
- Escalation triggers: which findings/decisions must return to the user before proceeding.
- Blocked-route rule: a route that depends on unavailable data, an unsupported assumption, or an unproved result is marked blocked — a scientific outcome, not an instruction to search until a favorable answer appears.
The claim record (during/after execution)
For each claim the work will support:
- Support: which data/analysis/proof supports it (with locations).
- Changes after seeing results: anything modified after outcomes were visible, and why (diagnostic-triggered fix vs favorable switch — keep these distinguishable).
- Unresolved: checks that remain open, and how they constrain the language.
- Decision: who decided what could be reported (user ruling vs assistant default).
Proportionality: a routine task needs one short paragraph; heavier records only when branching is extensive, outputs will be reused, errors are consequential, or correction is costly.
Show full SKILL.md (155 more words)Show less
Reporting language
The final decision is never "all checks green" — it is whether the evidence supports the proposed language. The options are: repair; narrower language; additional review; an exploratory/descriptive label; or decline to report. Never upgrade language beyond the evidence (associational ≠ causal; pointwise ≠ uniform; illustrated ≠ validated; imposed ≠ derived).
Keep credibility questions separate
Reproducibility, implementation correctness, statistical performance, measurement validity, and identification/scope are different questions; evidence on one cannot answer another. Reproducible code may implement the wrong estimator; favorable simulations cannot establish an assumption; a correct estimate may answer the wrong question.
Learn forward
Every diagnosed failure becomes a durable artifact: a reusable test, a documented warning, or a memory entry stating the failure, why it happened, and the check that now prevents it. Preserve failed approaches and the reason they failed — a blocked route re-attempted without a new mechanism is waste.
Cross-references
verification-ladder.md— rung 5 (the ledger).claude/rules/orchestrator-protocol.md— RUN_CONFIG is the brief for a fan-out
© pedrohcgs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/credible-claims of pedrohcgs/claude-code-my-workflow.
Open the folder on GitHubat commit ae72617
Compare with similar skills
Credible Claims 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 |
|---|---|---|---|---|---|---|
| Credible Claims this skillpedrohcgs/claude-code-my-workflow | 1.7k | — | ~1.1k | Automated safety check: Pass | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Deep Research WorkflowTokenRhythm/opensquilla | 7.1k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Deep Researchsanjay3290/ai-skills | 432 | 9 repos | ~683 | Automated safety check: Notes | Apache-2.0 | |
| Horizontal-Vertical Deep ResearchKKKKhazix/khazix-skills | 21k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Academic Research PipelineImbad0202/academic-research-skills | 51k | — | ~15k | Automated safety check: Pass | Custom licence |
Similar skills
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.
Deep Research
sanjay3290/ai-skills
Execute autonomous multi-step research using Google Gemini Deep Research Agent.
Horizontal-Vertical Deep Research
KKKKhazix/khazix-skills
Runs a two-axis deep research method on a product, company, concept or person: its full history over time, compared with peers today, delivered as a typeset PDF report.
Academic Research Pipeline
Imbad0202/academic-research-skills
Orchestrates a ten-stage academic workflow from research to finished manuscript, including integrity checks, two rounds of peer review and revision.
Academic Research Suite for Codex
Imbad0202/academic-research-skills-codex
A router skill that sends academic work such as literature reviews, drafting, citation checks, peer review and revision to the right workflow in the ARS suite.
More from pedrohcgs/claude-code-my-workflow
All 59 skills in this repoDevils Advocate
pedrohcgs/claude-code-my-workflow
Adversarial 5-7 question challenge to a deck's pedagogical choices — ordering, prerequisites, cognitive load, motivation.
Vaccinate
pedrohcgs/claude-code-my-workflow
Qualify a check before it is allowed to clear anything — prove it can detect the failure it is meant to catch.
Compile Latex
pedrohcgs/claude-code-my-workflow
Compile a Beamer LaTeX slide deck with XeLaTeX (3 passes + bibtex).
Context Status
pedrohcgs/claude-code-my-workflow
Show current context status and session health. An agent skill from pedrohcgs/claude-code-my-workflow.
Capture Environment
pedrohcgs/claude-code-my-workflow
Snapshot the computational environment for a replication package — detects the analysis stack (R / Stata / Python) and emits the right lockfiles (renv.lock + sessionInfo.txt, requirements.txt /…
Checkpoint
pedrohcgs/claude-code-my-workflow
Save a structured state snapshot before stopping or handing off.
Related
Categories
Questions about Credible Claims
What does Credible Claims do?
Research-brief + claim-record discipline for delegated or AI-assisted research work. Credible Claims is an agent skill from pedrohcgs/claude-code-my-workflow. Research-brief + claim-record discipline for delegated or AI-assisted research work.
When should I use Credible Claims?
Credible Claims fits situations like: starting any substantive research task; long autonomous run (write the brief first); when reporting results that will support a claim in a paper; decision (produce the claim record).
How do I install Credible Claims in Claude Code?
Run `npx skills add pedrohcgs/claude-code-my-workflow --skill credible-claims -a claude-code`. Or copy the skill folder (.claude/skills/credible-claims in pedrohcgs/claude-code-my-workflow) into .claude/skills/credible-claims in your project. Claude Code loads it when a task matches its description.
How do I install Credible Claims in Codex?
Run `npx skills add pedrohcgs/claude-code-my-workflow --skill credible-claims -a codex`. Or copy the skill folder (.claude/skills/credible-claims in pedrohcgs/claude-code-my-workflow) into .agents/skills/credible-claims in your project. Codex loads it when a task matches its description.
Can I use Credible Claims 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 pedrohcgs/claude-code-my-workflow --skill credible-claims -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/credible-claims, .gemini/skills/credible-claims, .github/skills/credible-claims and .opencode/skills/credible-claims in your project.
What does Credible Claims need to run?
SKILL.md names no scripts, command-line tools or credentials: Credible Claims is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Glob, Write.
Does Credible Claims 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 Credible Claims 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 Credible Claims use?
Credible Claims is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Credible Claims use?
About 1.1k tokens (SKILL.md is roughly 4.3k 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 Credible Claims?
Skills that share tags, products or a category with Credible Claims: GitHub Deep Research (bytedance/deer-flow, 84k stars), Deep Research Workflow (TokenRhythm/opensquilla, 7.1k stars), Deep Research (sanjay3290/ai-skills, 432 stars) and Horizontal-Vertical Deep Research (KKKKhazix/khazix-skills, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Credible Claims?
pedrohcgs (a GitHub user) maintains it in pedrohcgs/claude-code-my-workflow, which has 1,655 GitHub stars. The repository holds 59 skills in this directory. The repository was last updated on September 27, 2026.
Source: pedrohcgs/claude-code-my-workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.