Borrowing it
Nothing to install: this file belongs to ZimoLiao/scholaraio. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ZimoLiao/scholaraio/main/.claude/skills/technical-report/SKILL.mdgit clone --depth 1 https://github.com/ZimoLiao/scholaraioWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/zimoliao/scholaraio/technical-report)<a href="https://agentmods.dev/skills/zimoliao/scholaraio/technical-report"><img src="https://agentmods.dev/badge/skills/zimoliao/scholaraio/technical-report/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/zimoliao/scholaraio/technical-report"><img src="https://agentmods.dev/badge/skills/zimoliao/scholaraio/technical-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00031 | $0.00694 |
| Opus 5 | $0.00015 | $0.00347 |
| Sonnet 5 | $0.00006 | $0.00139 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
technical-report scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 type | Route |
|---|---|
| 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:
- Executive summary
- Scope and question definition
- Evidence base or literature coverage
- Comparative analysis
- Risks, limitations, or disagreements
- Recommendations / next steps
- 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
4. Package The Deliverable
- Use
/documentwhen the report should be turned into a formalDOCXor presentation. - Use
/citation-checkbefore final delivery if the report contains generated author-year citations. - Use
/exportif the user wants a bibliography bundle alongside the report.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 93 lines · 31 tokens per session scan A dd43b138aa53
technical-report is a skill published in the GitHub repository ZimoLiao/scholaraio (570 stars, last pushed 9d ago), licensed MIT. It adds 31 tokens to every session and 694 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
thoughtdag
Open the current Codex session in ThoughtDAG (desktop app direct; local bridge fallback — data never leaves this machine), or query local session history with why / find / recall.
research-workflow
This skill should be used when the user asks research questions, needs information lookup, wants comparisons, asks "what is", "how does", "explain", "compare", "best practices", "latest developments", or any query requiring web search, documentation lookup, or synthesis of multiple sources. Provides optimal routing…
gigaxity-deep-research
Deep research MCP server wrapping Qwen3-30B-A3B-Thinking via OpenRouter. Use when an agent needs cross-source synthesis with citations, exploratory expansion of an unfamiliar topic, chain-of-thought reasoning over evidence, or fast conversational lookups grounded in live web search. Exposes six MCP tools — two…
template-agentic-use
Agentic-use and skill-routing workflow for the Research Project Template. USE WHEN discovering relevant skills, making template easier for agents to navigate, auditing docs/prompts skill coverage, checking .cursor/skillmanifest.json, evaluating external skills, reviewing external agentic operating models such as…
infrastructure-overview
Top-level skill for the research template infrastructure layer. Use in Cursor, Claude Code, or similar agents when editing or importing anything under infrastructure/, understanding the two-layer architecture, or wiring build/validation/rendering/publishing. Covers module discovery, import patterns, thin…
infrastructure-search
Discovery utilities. Hosts subpackages — literature for Paperclip-style multi-source academic search; exa for Exa-backed web search, contents, answers, and find-similar; monid for the Monid gateway (discover/inspect/run) plus offline USD-per-1k search API pricing; and deepresearch for provider-neutral long-running…