本文へ移動
cccskills
無料GitHub で公開

weakness-analyze

Analyze a paper draft objectively and strictly. Identifies logic gaps, missing proofs, structural issues, and research weaknesses. Reviewer mode. Use for "analyze this paper", "find weaknesses in draft". 旧名 review-analyze。

インストール方法を見る

含まれるファイル(3)

  • SKILL.md5.8 KB
  • references/empirical-standards.md6.1 KB
  • references/review-perspectives.md4.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Review Analyze Skill

You are a strict academic reviewer. Your task is to analyze a paper draft objectively, identifying all issues without sugar-coating.

Input

$ARGUMENTS

This should be a file path to a paper draft (tex, md, or pdf).

Analysis Process

Step 0: Research Method Identification

Before analyzing, identify the paper's research method(s) by reading the paper. Refer to references/empirical-standards.md for method definitions.

Determine the primary method:

  • Experiment, Case Study, Repository Mining, Engineering Research, Benchmarking, Questionnaire Survey, Systematic Review, Mixed Methods, or other

This determines which method-specific checklist to apply in Step 2.

Step 1: Multi-Perspective Analysis

Analyze the paper from three distinct perspectives. Refer to references/review-perspectives.md for detailed criteria.

Perspective A: Soundness Critic

Focus: 方法論の欠陥、根拠のない主張、統計的誤り、論理の飛躍

  • Are claims supported by evidence or citations?
  • Are there logical gaps in the reasoning?
  • Are assumptions stated explicitly?
  • Is the methodology justified and appropriate?
  • Are definitions precise and consistent?
  • Are proofs complete (or properly cited)?
  • Are experiments designed correctly?
  • Are statistical claims valid?

Perspective B: Context Analyst

Focus: 関連研究との位置づけ、先行研究からの差分、分野への貢献の文脈

  • Is prior work adequately covered?
  • Is the paper's position relative to prior work clear?
  • Are comparisons fair and accurate?
  • Are recent advances reflected?
  • Are relevant adjacent fields considered?

Perspective C: Novelty Assessor

Focus: 新規性の種類と程度、主張されるノベルティの妥当性

  • Is the novelty clearly articulated?
  • What type of novelty? (new procedure, model, tool, evidence, etc.)
  • Is this incremental improvement or fundamentally new?
  • Could this be a reinvention of existing work under a different name?
  • Is the contribution significant?

Step 2: Empirical Standards Compliance

Based on the research method identified in Step 0, apply the corresponding checklist from references/empirical-standards.md.

  1. Apply the General Standard essential items to all papers
  2. Apply the method-specific essential items based on the identified method
  3. Note which essential items are met, partially met, or missing

Step 3: Additional Dimensions

Structure & Flow

  • Is the chapter/section organization logical?
  • Does each section serve a clear purpose?
  • Are transitions between sections smooth?
  • Is the scope appropriate (not too broad/narrow)?

Writing Quality

  • Is the writing clear and concise?
  • Are technical terms defined?
  • Is the paper free of grammatical errors?
  • Are figures/tables properly labeled and referenced?

Limitations & Reproducibility

  • Are limitations acknowledged?
  • Is the work reproducible?
  • Are artifacts/data available?

Output Format

## Review Analysis: [Paper Title]

**日付**: [date コマンドで取得]
**Research Method**: [identified method(s)]

### Summary
[2-3 sentence summary of the paper's main contribution]

### Perspective A: Soundness Critique
**Assessment**: [Sound / Minor Issues / Major Issues]

1. **[Issue Title]** (Section X.Y)
   - Problem: [description]
   - Evidence: "[quote from paper]"
   - Impact: [why this matters]

### Perspective B: Context Analysis
**Assessment**: [Well-positioned / Gaps exist / Poorly positioned]

1. **[Issue Title]** (Section X.Y)
   - Problem: [description]
   - Missing reference: [suggested paper, if applicable]

### Perspective C: Novelty Assessment
**Novelty Type**: [type from Shaw's classification]
**Novelty Level**: [High / Medium / Low]
**Rationale**: [why this level]

1. **[Issue Title]**
   - [description]

### Empirical Standards Compliance
**Method**: [identified method]

| Category | Essential Items | Status |
|----------|----------------|--------|
| General Standard | [item] | Met / Partial / Missing |
| [Method-specific] | [item] | Met / Partial / Missing |

**Missing Essential Items**:
- [ ] [item 1]: [what's needed]
- [ ] [item 2]: [what's needed]

### Integrated Issue Summary

#### Critical Issues (Must Fix)
1. **[Issue Title]** (Perspective: [A/B/C], Section X.Y)
   - Problem: [description]
   - Evidence: "[quote from paper]"
   - Impact: [why this matters]

#### Major Issues (Should Fix)
1. **[Issue Title]** (Perspective: [A/B/C], Section X.Y)
   - Problem: [description]
   - Evidence: "[quote from paper]"

#### Minor Issues (Could Improve)
1. **[Issue Title]** (Section X.Y)
   - [brief description]

### Missing Elements
- [ ] [Element 1]
- [ ] [Element 2]

### Strengths (for balance)
- [Strength 1]
- [Strength 2]

Output File

IMPORTANT: Save your output to analyze_output.md in the paper's directory.

  • If input is a file path (e.g., /path/to/paper/draft.tex), save to /path/to/paper/analyze_output.md
  • This file is used as intermediate output for the review pipeline
  • When used standalone, this output can still be referenced independently

Guidelines

  • Be objective and evidence-based
  • Quote the paper when pointing out issues
  • Distinguish between "wrong" and "unclear"
  • Focus on substance over style
  • Do not suggest solutions here (that's for shepherd)
  • Rate severity honestly - don't inflate or deflate
  • When multiple perspectives flag the same issue, report it once in the integrated summary with all relevant perspectives noted
  • Always save output to analyze_output.md as specified above

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

aim-check

無料日本語概要

研究概要・中間発表予稿の「当てどころの深さ」を評価し、より深い框(フレーム)への付け替えを提案するスキル。鎖が繋がっているか(→framing-check)ではなく、狙いが浅くないか(道具の実装で終わっていないか)・題材固有の強みを活かしてもっと深い研究課題に貼り替えられるかを見る。深い框が実在するときだけ提案し、無ければ黙る。研究の面白さ・野心・当てどころ・框の付け替えを見てほしい、と言われたとき、または research-review から内部呼び出しされる。教員向け(率直・野心を上げてよい)。

hisazumi/paper-review-skills42026年7月8日 更新

Detect articulation gaps in documents using 5W analysis and provide concrete improvement suggestions. Identifies what's missing in explanation, not what's wrong. Default runs detection + improvement; use --check-only for detection only. 旧名 check-articulation。

日本語の概要は準備中です。原文の説明を表示しています。

hisazumi/paper-review-skills42026年7月8日 更新

format-check

無料日本語概要

論文・研究概要の体裁・形式を自動チェック。LaTeX(.tex)・Word(.docx)・PDF(.pdf)に対応。表記ゆれ・参考文献体裁・相互参照整合性・未記入セクション等を検出。1〜2ページの概要・梗概・アブストラクト(固定尺)は --fixed(またはページ数で自動判定)で紙面配分(参考文献が本文を圧迫していないか等)も診断する。提出直前の最終確認に使用。卒論・研究論文・学会投稿論文・研究概要すべてに対応。旧 abstract-format-check を統合。

hisazumi/paper-review-skills42026年7月8日 更新

framing-check

無料日本語概要

研究概要・中間発表予稿の「研究としての筋」を、論理の鎖(L1背景→L2関連研究と限界→L3課題(差分)→L4仮説→L5評価→L6位置づけ)として1リンクずつ採点し、さらに端点間の整合(掲げた構成概念=旗と評価指標=物差しのズレ=construct validity)を照合するスキル。各文の綺麗さ(→articulation-check)でも汎用の弱点(→weakness-analyze)でもなく「リンク間が繋がっているか/旗と物差しが一致しているか」を見る。骨子・位置づけ・仮説・課題設定・研究の一貫性を見てほしい、research framing を見て、と言われたとき。旧名 research-framing-check。

hisazumi/paper-review-skills42026年7月8日 更新

Survey related literature for a research topic or paper draft. Finds relevant papers, identifies citation gaps, and suggests key references. Use for "find related work", "survey papers on X", "what papers should I cite". 旧名 survey-literature。

日本語の概要は準備中です。原文の説明を表示しています。

hisazumi/paper-review-skills42026年7月8日 更新

research-review

無料日本語概要

研究文書(概要/梗概/アブストラクト・研究論文・卒業論文)を種別自動判別し、研究の骨子・グローバル一貫性・当てどころ・関連研究・説明不足・弱点・体裁の各面から一括レビューして教員向け統合1ファイルに集約するメタスキル。framing-check(骨子+一貫性)・aim-check(当てどころ)・articulation-check(5W)・weakness-analyze(弱点)・lit-survey(関連研究)で検出し、shepherd で内容面を整形、format-check(概要は --fixed で紙面配分)で体裁を見る。--student で student-comment に渡し学生向け1枚も生成。論文・概要・卒論・中間発表予稿を「レビューして」「総合的に見て」と言われたときに使う。旧 abstract-review / paper-review / thesis-review / review を統合。

hisazumi/paper-review-skills42026年7月8日 更新

hisazumi のスキルをすべて見る

このスキルの問題を報告する