paper-analyst

Other Community
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Other
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
88 / 100 · community maintained
Author / version / license
@luwill · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No special requirements
Permissions
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools,默认拥有全部工具权限。

Output preview paper-analyst.preview
---
name: paper-analyst
description: > 精读论文、提取方法细节、构建结构化对比表。 对每篇核心论文,通过以下方式获取内容: 每篇论文生成一个分析文件: paper_analyses/{arxiv-id}.md 跨论文对比,生成…
category: other
runtime: no special runtime
---

# paper-analyst output preview

## PART A: Task fit
- Use case: > 精读论文、提取方法细节、构建结构化对比表。 对每篇核心论文,通过以下方式获取内容: 每篇论文生成一个分析文件: paper_analyses/{arxiv-id}.md 跨论文对比,生成 comparison_tables.md [用一句话概括这篇论文的核心贡献] runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “角色定位 / 分析流程 / Step 1: 理解任务” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “> 精读论文、提取方法细节、构建结构化对比表。 对每篇核心论文,通过以下方式获取内容: 每篇论文生成一个分析文件: paper_analyses/{arxiv-id}.md 跨论文对比,生成 comparison_tables.md [用一句话概括这篇论文的核心贡献] runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “角色定位 / 分析流程 / Step 1: 理解任务” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: > 精读论文、提取方法细节、构建结构化对比表。 对每篇核心论文,通过以下方式获取内容: 每篇论文生成一个分析文件: paper_analyses/{arxiv-id}.md 跨论文对比,生成 comparison_tables.md [用一句话概括这篇论文…
  • Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
  • Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

  • Structure: The skill is organized around “角色定位”, “分析流程”, “Step 1: 理解任务”, “Step 2: 确定分析范围”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
  • Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
  • Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

  • Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
  • Invocation: Name paper-analyst directly; if the source includes slash commands, start with the command and then add task context.
  • Validation: Start small and check whether the result follows “角色定位 / 分析流程 / Step 1: 理解任务” before expanding.

Boundaries And Review

  • Dependencies: It usually needs no extra API key, so start with a small validation task.
  • Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
  • Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.