Agent skill

Technical Report

by ZimoLiao in ZimoLiao/scholaraio

A skill your agent uses when the user wants a technical report, topic report, research briefing, structured investigation, evidence synthesis, recommendations, or final report packaging.

MITAuto-check passedResearch & Science

Install Technical Report

skills CLI
$ npx skills add ZimoLiao/scholaraio --skill technical-report -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ZimoLiao/scholaraio technical-report --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ZimoLiao/scholaraio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/technical-report .claude/skills/technical-report && rm -rf skills-src

Use ~/.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/

Facts

Skill name
technical-report
GitHub stars
576
Token cost
~794 tokens
SKILL.md length
373 words
Files
1
Skills in repo
43
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when the user wants a technical report, topic report, research briefing, structured investigation, evidence synthesis, recommendations, or final report packaging.

  • Works in 4 steps: Clarify Report Goal → Choose The Analysis Backbone → Build A Report Structure → …
  • The user wants a technical report
  • SKILL.md covers Purpose, When To Use, Workflow and Output Pattern, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Technical Report is an agent skill from ZimoLiao/scholaraio. Use when the user wants a technical report, topic report, research briefing, structured investigation, evidence synthesis, recommendations, or final report packaging.

Its SKILL.md is about 790 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. The repository describes itself as: Scholar All-In-One: A research infrastructure for AI agents. The licence is MIT.

When your agent uses it

  • The user wants a technical report
  • Research briefing
  • Structured investigation
  • Evidence synthesis

Example prompts

  • “/technical-report”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Clarify Report Goal
  2. Choose The Analysis Backbone
  3. Build A Report Structure
  4. Package The Deliverable

What it can do on your machine

Read from SKILL.md and the folder at commit 777628b. 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 Report loads about 794 tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 373 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~46
When it runs · the whole SKILL.md, loaded when a task matches
~794

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 ZimoLiao/scholaraio at commit 777628b, republished under its MIT licence (© ZimoLiao). 373 words, ~794 tokens.

Download SKILL.mdSave it as .claude/skills/technical-report/SKILL.md (or your agent's skills folder).
name
technical-report
description
Use when the user wants a technical report, topic report, research briefing, structured investigation, evidence synthesis, recommendations, or final report packaging.

Technical Report Workflow

Create a report-oriented workflow for investigation, synthesis, and recommendation.

Purpose

This skill handles the cases that are not quite a paper and not just raw notes:

  • technical survey reports
  • topic briefings
  • special-topic investigations
  • advisor or team-facing research reports

It does not replace the deeper analysis skills. Instead, it decides which analysis path to use and then shapes the result into a report.

When To Use

Use this skill when the user wants:

  • a technical report
  • a topic or special-subject report
  • a research briefing for a team, supervisor, or project
  • a recommendation memo grounded in literature

If the user mainly wants:

  • a literature review article: use /literature-review
  • an open-problem analysis: use /research-gap
  • a slide deck: use /document

Workflow

1. Clarify Report Goal

Identify:

  • who the report is for
  • whether the report is explanatory, comparative, or decision-support
  • whether the user wants conclusions only or also recommendations
  • whether the report is meant to stay as Markdown or become a formal DOCX/PPTX deliverable
2. Choose The Analysis Backbone

Use one primary path:

Report typeRoute
State-of-the-art / what is known/literature-review
Open questions / what is missing/research-gap
User's own project update or method summary/paper-writing
3. Build A Report Structure

Recommended default structure:

  1. Executive summary
  2. Scope and question definition
  3. Evidence base or literature coverage
  4. Comparative analysis
  5. Risks, limitations, or disagreements
  6. Recommendations / next steps
  7. References

Adjust by audience:

  • supervisor or PI: prioritize takeaways and decisions
  • technical team: prioritize trade-offs, methods, constraints
  • self-study memo: prioritize structure and evidence trail
Show full SKILL.md (121 more words)Show less
4. Package The Deliverable
  • Use /document when the report should be turned into a formal DOCX or presentation.
  • Use /citation-check before final delivery if the report contains generated author-year citations.
  • Use /export if the user wants a bibliography bundle alongside the report.

Output Pattern

Recommended outputs inside workspace/<name>/:

  • technical-report-outline.md
  • technical-report.md
  • references.bib
  • packaged deliverable from /document if requested

Principles

  • Decision-oriented structure: reports should help someone act, not only read.
  • Separation of layers: analysis comes from existing writing/research skills; this skill organizes it into a report.
  • Audience-aware emphasis: same evidence, different structure for different readers.
  • Honest scope: packaging is currently routed through /document; do not imply a separate report generator backend.

Example

用户说:"帮我写一个这个方向的技术调研报告,给组会用" → 用本 skill 先明确 audience 和结构,再转 /literature-review 或 /research-gap 形成分析主体,最后接 /document

© ZimoLiao, 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/technical-report of ZimoLiao/scholaraio.

Open the folder on GitHubat commit 777628b

Compare with similar skills

Technical Report 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.

Technical Report compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Technical Report this skillZimoLiao/scholaraio576—~794Automated safety check: PassMIT
Academic Paper Writing PipelineImbad0202/academic-research-skills51k—~16kAutomated safety check: PassCustom licence
Scientific Venue Templatesdavila7/claude-code-templates32k9 repos~5.1kAutomated safety check: NotesMIT
Horizontal-Vertical Deep ResearchKKKKhazix/khazix-skills21k—~2.1kAutomated safety check: PassMIT
Econ Writehanlulong/econ-writing-skill6462 repos~14kAutomated safety check: PassMIT
NSFC Budget Justification Writerhuangwb8/ChineseResearchLaTeX2.9k2 repos~1.4kAutomated safety check: PassMIT

Similar skills

  • Academic Paper Writing Pipeline

    Imbad0202/academic-research-skills

    Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.

    51k GitHub stars~16k tokensUpdated 5 days ago
    Research & ScienceAuto-check passed
  • Scientific Venue Templates

    davila7/claude-code-templates

    Supplies LaTeX templates and formatting rules for journals, conferences, posters, and grant proposals, then can check a draft against them.

    32k GitHub starsUsed in 9 repos~5.1k tokens
    Research & ScienceAuto-check: notes
  • 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.

    21k GitHub stars~2.1k tokensUpdated 7 days ago
    Research & ScienceAuto-check passed
  • Econ Write

    hanlulong/econ-writing-skill

    Expert economics paper writing assistant synthesizing advice from 50+ top guides by Cochrane, McCloskey, Shapiro, Head, Bellemare, Goldin, Glaeser, Kremer, and other leading economists.

    646 GitHub starsUsed in 2 repos~14k tokens
    Research & ScienceAuto-check passed
  • NSFC Budget Justification Writer

    huangwb8/ChineseResearchLaTeX

    Writes a submission-ready NSFC budget justification as a LaTeX project and renders budget.pdf from your grant proposal text and supporting materials.

    2.9k GitHub starsUsed in 2 repos~1.4k tokens
    Research & ScienceAuto-check passed
  • Study

    alaliqing/claude-paper

    A skill your agent uses when the user wants to read, study, analyze, or deeply understand a research paper (PDF).

    344 GitHub starsUsed in 1 repo~2.5k tokens
    Research & ScienceAuto-check: notes

More from ZimoLiao/scholaraio

All 43 skills in this repo
  • Document

    ZimoLiao/scholaraio

    A skill your agent uses when the user wants to create or inspect DOCX, PPTX, or XLSX files, generate a downloadable Office deliverable, or verify its structure and layout warnings with scholaraio…

    576 GitHub stars~674 tokensUpdated 13 days ago
    Auto-check passed
  • Academic Writing

    ZimoLiao/scholaraio

    A skill your agent uses when the user needs help choosing or organizing an academic-writing workflow by deliverable, stage, or format, including review articles, guided reading, paper sections, PPT…

    576 GitHub stars~827 tokensUpdated 13 days ago
    Auto-check passed
  • Arxiv

    ZimoLiao/scholaraio

    A skill your agent uses when the user wants to browse arXiv preprints, search arXiv directly, fetch a PDF by arXiv ID or URL, or send a preprint into the ScholarAIO ingest pipeline.

    576 GitHub stars~799 tokensUpdated 13 days ago
    Auto-check passed
  • Bioinformatics

    ZimoLiao/scholaraio

    A skill your agent uses when working on bioinformatics workflows such as alignment, variant calling, phylogenetics, or protein-structure analysis, especially across BLAST, minimap2, samtools…

    576 GitHub stars~1.4k tokensUpdated 13 days ago
    Auto-check passed
  • Citation Check

    ZimoLiao/scholaraio

    A skill your agent uses when the user wants to verify citations in AI-generated or human-written text against the local knowledge base and catch hallucinated, wrong, or missing references.

    576 GitHub stars~454 tokensUpdated 13 days ago
    Auto-check passed
  • Draw

    ZimoLiao/scholaraio

    A skill your agent uses when the user wants diagrams, flowcharts, architecture visuals, data relationships, timelines, concept maps, Mermaid, Graphviz, drawio, or polished paper figures generated…

    576 GitHub stars~1.3k tokensUpdated 13 days ago
    Auto-check: notes

Questions about Technical Report

What does Technical Report do?

A skill your agent uses when the user wants a technical report, topic report, research briefing, structured investigation, evidence synthesis, recommendations, or final report packaging. Technical Report is an agent skill from ZimoLiao/scholaraio. Use when the user wants a technical report, topic report, research briefing, structured investigation, evidence synthesis, recommendations, or final report packaging.

When should I use Technical Report?

Technical Report fits situations like: the user wants a technical report; research briefing; structured investigation; evidence synthesis.

How do I install Technical Report in Claude Code?

Run `npx skills add ZimoLiao/scholaraio --skill technical-report -a claude-code`. Or copy the skill folder (.claude/skills/technical-report in ZimoLiao/scholaraio) into .claude/skills/technical-report in your project. Claude Code loads it when a task matches its description.

How do I install Technical Report in Codex?

Run `npx skills add ZimoLiao/scholaraio --skill technical-report -a codex`. Or copy the skill folder (.claude/skills/technical-report in ZimoLiao/scholaraio) into .agents/skills/technical-report in your project. Codex loads it when a task matches its description.

Can I use Technical Report 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 ZimoLiao/scholaraio --skill technical-report -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-report, .gemini/skills/technical-report, .github/skills/technical-report and .opencode/skills/technical-report in your project.

What does Technical Report need to run?

SKILL.md names no scripts, command-line tools or credentials: Technical Report is instructions for the agent only.

Does Technical Report 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 Report 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 Report use?

Technical Report 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 Technical Report use?

About 794 tokens (SKILL.md is roughly 3.2k 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 Report?

Skills that share tags, products or a category with Technical Report: Academic Paper Writing Pipeline (Imbad0202/academic-research-skills, 51k stars), Scientific Venue Templates (davila7/claude-code-templates, 32k stars), Horizontal-Vertical Deep Research (KKKKhazix/khazix-skills, 21k stars) and Econ Write (hanlulong/econ-writing-skill, 646 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Technical Report?

ZimoLiao (a GitHub user) maintains it in ZimoLiao/scholaraio, which has 576 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on September 25, 2026.

Source: ZimoLiao/scholaraio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.