SkillAgentSearch skills...

tech-paper-template

Structures a technical paper's full logical skeleton using a thinking-template table (research background, limitations, key idea or goal, challenges, methodology modules, contributions), positions the paper as Technique or New Problem/Setting, and runs a four-point self-consistency check

Install / Use

npx skills add HKUSTDial/Supervisor-Skills --skill tech-paper-template

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

88/100

Supported Platforms

Universal

Tags

Our assessment of tech-paper-template

tech-paper-template scores 88/100 on our quality scale, 208th of 421 Education & Research skills we index (top 50%).

Its SKILL.md is 6.8 KB long, well organised into 18 sections and no code examples: a thorough specification that gives an agent plenty to work with.

With 7,505 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
13/20
Description
15/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so tech-paper-template is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-28. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

tech-paper-template compared with similar skills

All 4 of these similar skills score higher than tech-paper-template; compare them before choosing.

SkillScoreStarsUpdatedFormat
tech-paper-template (this skill)by HKUSTDial887.5k2mo agoSKILL.md
last30days-skillby mvanhorn10068.0ktodayCLAUDE.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install tech-paper-template?
Run npx skills add HKUSTDial/Supervisor-Skills --skill tech-paper-template. The install tabs above show the steps for each supported agent.
Which AI agents does tech-paper-template work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is tech-paper-template safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is tech-paper-template still maintained?
The repository was last updated about 2 months ago, so tech-paper-template is actively maintained.

name: tech-paper-template description: >- Structures a technical paper's full logical skeleton using a thinking-template table (research background, limitations, key idea or goal, challenges, methodology modules, contributions), positions the paper as Technique or New Problem/Setting, and runs a four-point self-consistency check. Use when the user is brainstorming a paper, discussing progress with an advisor, or planning the paper before drafting. Also use for 'paper skeleton', 'paper logic chain', 'thinking template', 'paper-structure planning'. license: CC-BY-4.0

Tech Paper Template

Overview

Before drafting any prose, a technical paper needs a full logical skeleton: the research background, the specific limitations of prior work, the key idea or research goal, the technical challenges that prevent a naive solution, the methodology modules that address each challenge, and the contributions that the paper will claim. This skill fills in that skeleton via a standardised thinking-template table, positions the paper type, and runs four self-consistency checks on the logic chain.

The output is a filled-in thinking template plus a consistency report. It is suitable for advisor-student brainstorming sessions, weekly progress meetings, and the final planning step before writing begins. It does not draft Introduction prose (use intro-drafter for that); it operates at the logical-skeleton layer.

When to use this skill

  • Early brainstorming of a paper project.
  • Weekly progress meeting with an advisor or collaborator.
  • Pre-drafting planning after idea-evaluator returns Strong Accept.
  • The paper's logic chain feels incoherent and needs an audit.
  • The user asks for 'paper skeleton', 'paper logic chain', 'thinking template', or 'paper-structure planning'.
  • The user is unsure whether their paper is Technique or New Problem/Setting.

When NOT to use this skill

  • The paper is a benchmark paper. Use benchmark-paper-template (separate plugin).
  • The user needs an Introduction-specific paragraph outline. Use intro-drafter (typically run this skill first, then intro-drafter).
  • The user has a written draft and wants review feedback. Use pre-submission-reviewer.
  • The idea itself is not yet vetted. Use idea-evaluator first.

Core procedure

Step 1: Paper-type positioning

See: references/paper-types.md for the positioning criteria and worked examples.

Decide Technique versus New Problem/Setting. In Technique, the Key Idea carries the narrative and Our Goal is a short bridge. In New Problem/Setting, Our Goal is the contribution and the Key Idea justifies feasibility.

If the user's inputs describe a benchmark, stop and redirect to benchmark-paper-template (separate plugin).

Step 2: Fill the thinking template

See: references/thinking-template.md for each template cell's content contract, what a strong cell looks like, and common failure modes.

Fill the seven cells:

  1. Research background. Scenario, importance, motivation.
  2. Limitations 1 through 3 (2 is acceptable; more than 3 is not).
  3. Key idea or Our Goal. One sentence.
  4. Challenges 1 through 3 (similar cap).
  5. Methodology modules. One module per challenge.
  6. Contributions (3 or 4, each mapped to a section).

If a cell is incomplete given the user's inputs, mark it as a gap with severity.

Step 3: Run four self-consistency checks

See: references/consistency-checks.md for the detailed checking procedure and examples of chain breaks.

Run each check:

  1. Limitations to Key Idea: does the Key Idea or Goal address the stated Limitations? If not, either the Limitations are wrong or the Key Idea is misaligned.
  2. Key Idea to Challenges: do the Challenges arise naturally from implementing the Key Idea? If not, the challenges are invented to justify modules rather than derived from the idea.
  3. Challenges to Methodology: does each methodology module address one challenge? If not, there is a module without justification or a challenge without a fix.
  4. Methodology to Contributions: do the contributions cover each module or experimental result? If not, contributions are vague or promising more than the paper delivers.

Every failure is CRITICAL.

Step 4: Generate methodology outline

See: references/thinking-template.md for the methodology-outline template.

From the challenges, derive a methodology outline: topic sentence, per-module subsection names, and per-module one-sentence summary. This becomes the skeleton for Section 3 or 4 of the paper.

Step 5: Integrity gate

Before emitting, run the checks in the Integrity gate section below.

Step 6: Output

Emit the filled template plus the consistency report in the Output format below.

Integrity gate

All seven bullets are [inspection] class: the LLM verifies each directly from the filled template (counting, pattern-matching, or comparing cells). No user-side attestation required.

Before returning the filled template:

  1. [inspection] Paper-type positioning is consistent with the user's actual contribution (Technique paper not shoehorned into New Problem framing, or vice versa).
  2. [inspection] Limitations are specific and cited-able, not vague.
  3. [inspection] Key Idea or Goal is a single sentence a reviewer could quote.
  4. [inspection] Challenges derive from implementing the Key Idea; they are not invented.
  5. [inspection] Methodology modules have one-to-one mapping with challenges.
  6. [inspection] Contributions map to methodology modules and to specific sections.
  7. [inspection] All four self-consistency checks pass.

If any check fails, mark the skeleton as "needs user attention".

Output format

1. Paper-type positioning

  • Type: <Technique Paper or New Problem/Setting Paper>
  • Rationale: <one sentence>

2. Thinking template

| Stage | Your content | |---|---| | Research background | ... | | Limitation 1 | ... | | Limitation 2 | ... | | Limitation 3 (if applicable) | ... | | Key Idea / Our Goal | ... | | Challenge 1 | ... | | Challenge 2 | ... | | Challenge 3 (if applicable) | ... | | Methodology topic sentence | ... | | Module A (addresses Challenge 1) | ... | | Module B (addresses Challenge 2) | ... | | Module C (addresses Challenge 3) | ... | | Contribution 1 | ... (Section <X>) | | Contribution 2 | ... (Section <Y>) | | Contribution 3 | ... (Section <Z>) |

3. Self-consistency checks

  • Check 1 Limitations -> Key Idea: <pass or fail>
  • Check 2 Key Idea -> Challenges: <pass or fail>
  • Check 3 Challenges -> Methodology: <pass or fail>
  • Check 4 Methodology -> Contributions: <pass or fail>

4. Severity summary

  • <n> CRITICAL, <m> MAJOR, <k> MINOR.
  • Top three fixes first: ...

5. Next suggested skill

  • If all checks pass: intro-drafter to produce the Introduction paragraph outline.
  • If checks fail: address the flagged chain breaks first.

Related Skills

View on GitHub
GitHub Stars7.5k
CategoryEducation
Updated2mo ago
Forks465

Languages

Python

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium