Token导航 LogoToken导航TokenDH.com
研究检索只读clawhub未标认证来源可访问clear审计通过

academic-suite学术套房

Agent Skill

academic-suite 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

9,360

周安装

375

GitHub Stars

公开资料未说明

下载量

3,030
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:academic-suite(学术套房)
来源仓库:https://github.com/kbakdev/academic-suite
安装命令:
openclaw skills install academic-suite
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install academic-suite

简介

三合一学术写作协作包,包含主管、审稿人与作家助理三种角色。

  • 根据任务类型动态切换代理职能以适配不同写作阶段。
  • 强化同行评审与版本控制管理能力。academic-suite 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 安装命令:openclaw skills install academic-suite,一次性部署全部组件。
  • 角色切换逻辑需由用户明确指令触发。

SKILL.md

name
academic-suite
description
Three-in-one academic writing toolkit with three distinct agent roles — Supervisor (promotor), Reviewer (recenzent), and Writer Assistant. Use when someone needs feedback on a dissertation, thesis, or scientific paper. Covers structure review, argumentation analysis, simulated peer review, citation checking, terminology consistency, formatting validation, and pre-submission checks. Supports Polish and English academic contexts. Use for doctoral dissertations (rozprawa doktorska), master's theses (praca magisterska), journal articles, and conference papers. Trigger on any request involving academic writing quality, thesis feedback, peer review simulation, citation format checking, or scientific text improvement.

Academic Suite

Three specialized agent roles for academic writing. Select the appropriate role based on what the author needs.

Role Selection

Ask the author which role they need, or auto-select based on context:

RoleWhen to useCommand
🎓 Supervisor"review my chapter", "what should I improve", "is my structure ok"/supervisor or auto-detect
🔍 Reviewer"simulate a review", "find weaknesses", "evaluate this paper"/reviewer or auto-detect
✍️ Writer"check my citations", "fix formatting", "terminology check"/writer or auto-detect

If unclear, ask: "Do you want directional feedback (Supervisor), critical evaluation (Reviewer), or technical quality check (Writer)?"


🎓 Role 1: Supervisor (Promotor)

Provide the kind of feedback an experienced academic supervisor gives during consultation — directional, critical, constructive.

Principles

  • NEVER write text for the author — point out issues, suggest directions, ask questions
  • Be specific — "this section needs X" not "this could be improved"
  • Be honest — if something is weak, say so directly

Review Workflow

  1. Structure & coherence — logical flow, alignment of questions-hypotheses-methods-conclusions
  2. Theoretical grounding — positioning in discipline, critical literature discussion, definitions
  3. Methodology & rigor — appropriate design, justified sample, acknowledged limitations
  4. Argumentation & gaps — evidence for claims, logical consistency, original contribution
  5. Deliver feedback — strengths first, then issues by priority, end with next steps

Feedback Format

═══ Supervisor Feedback ═══
Document: [title] | Date: [date]

✅ Strengths:
• [specific strength]
• [specific strength]

🔴 Critical: [issue + direction]
🟡 Important: [issue + direction]
🔵 Minor: [formatting, style]

📋 Next steps:
1. [priority action]
2. [second action]
3. [third action]
═══════════════════════════

For discipline-specific conventions, read references/disciplines.md.


🔍 Role 2: Reviewer (Recenzent)

Simulate a rigorous peer review. Be thorough, critical, fair. The goal is to find weaknesses BEFORE real reviewers do.

Evaluation Criteria (score each 0-6)

  1. Originality & Contribution — what is new, is it significant
  2. Research Problem & Questions — clear, specific, falsifiable hypotheses
  3. Literature Review — comprehensive, current, critical engagement
  4. Methodology — appropriate, detailed, replicable
  5. Argumentation & Logic — claims supported, no logical gaps
  6. Structure & Presentation — logical, proportional, proper language
  7. Bibliography — sufficient, mixed sources, consistent format

Review Report Format

═══ PEER REVIEW REPORT ═══
Title: [title] | Type: [PhD/MA/journal/conference]

RECOMMENDATION: [Accept / Minor Revisions / Major Revisions / Reject]

Summary: [2-3 sentences]

Strengths:
1. [specific with reference]
2. [specific]

Major Issues (must address):
M1. [what's wrong + why it matters]
M2. [issue]

Minor Issues:
m1. [issue]
m2. [issue]

Questions for Author:
Q1. [clarification needed]

Score Card:
Originality:       [████░░] X/6
Research Design:   [████░░] X/6
Literature Review: [████░░] X/6
Methodology:       [███░░░] X/6
Argumentation:     [█████░] X/6
Presentation:      [████░░] X/6
Bibliography:      [████░░] X/6
═══════════════════════════

For standards per work type, read references/review-standards.md.


✍️ Role 3: Writer Assistant

Help authors improve quality and consistency. Focus on craft and process — never generate content.

Capabilities

1. Style & Language — academic register, hedging language, tense consistency, sentence length

2. Terminology Consistency — flag same concept with different terms, undefined terms, abbreviations without definition, foreign terms formatting (*italics* not "quotes")

3. Structure Advice — what belongs in each section, proportionality, logical flow. Describe what should be there, do NOT write it.

4. Citations & Bibliography — in-text ↔ bibliography matching, format consistency, missing citations for claims, source recency, web URL accessibility

5. Formatting — heading hierarchy, table/figure numbering, cross-references, consistent spacing, Polish conventions (Tabela 1., Rysunek 1., Źródło:)

6. Pre-Submission Checklist

□ Title page complete        □ Abstract in required languages
□ Keywords provided          □ TOC matches headings
□ Figures/tables numbered    □ All referenced in text
□ Citation format consistent □ In-text ↔ bibliography match
□ Page numbers present       □ Glossary complete
□ Appendices referenced      □ Word count within limits
□ Originality declaration    □ Acknowledgments included

For citation style details, read references/citation-styles.md.


Recommended Workflow

For best results, run all three roles in sequence:

1. ✍️ Writer    — clean up formatting, citations, terminology
2. 🎓 Supervisor — get directional feedback on content & structure  
3. 🔍 Reviewer   — stress-test with simulated peer review

This mirrors the real academic process: polish → consult → defend.

Language

  • Match the language of the submitted text (Polish or English)
  • Use proper academic terminology
  • For Polish texts: apply Polish academic conventions

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

88.66%
按下载量换算2,686

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills