fluxly Search skills… ⌘K 中文 Publish

research-summarizer

AI Community
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
AI
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
88 / 100 · community maintained
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No special requirements
Permissions
  • Read-only
  • Write / modify
  • Shell exec
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 research-summarizer.preview 
---
name: research-summarizer
description: 这是一个结构化的研究摘要工作流程，能够将冗长的原始材料转化为实用的简报。专为产品经理、分析师、创业者以及所有需要阅读大量资料的人设计。 这不仅仅是一个简单的“总结”功能——而是一个可重复使用的…
category: ai
runtime: no special runtime
---

# research-summarizer output preview

## PART A: Task fit
- Use case: 这是一个结构化的研究摘要工作流程，能够将冗长的原始材料转化为实用的简报。专为产品经理、分析师、创业者以及所有需要阅读大量资料的人设计。 这不仅仅是一个简单的“总结”功能——而是一个可重复使用的框架，能够提取关键信息、对比不同来源的内容，并正确格式化引用。 |---------|-------------| | /research:summarize | 将单个来源的内容总结为结构化的简报 | runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “命令行工具 / 该技能的触发条件 / 工作流程” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “这是一个结构化的研究摘要工作流程，能够将冗长的原始材料转化为实用的简报。专为产品经理、分析师、创业者以及所有需要阅读大量资料的人设计。 这不仅仅是一个简单的“总结”功能——而是一个可重复使用的框架，能够提取关键信息、对比不同来源的内容，并正确格式化引用。 |---------|-------------| | /research:summarize | 将单个来源的内容总结为结构化的简报 | runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “命令行工具 / 该技能的触发条件 / 工作流程” 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, run shell commands; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files, run shell commands; 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: 这是一个结构化的研究摘要工作流程，能够将冗长的原始材料转化为实用的简报。专为产品经理、分析师、创业者以及所有需要阅读大量资料的人设计。 这不仅仅是一个简单的“总结”功能——而是一个可重复使用的框架，能够提取关键信息、对比不同来源的内容，并正确格式化引用。…
  • 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 “命令行工具”, “该技能的触发条件”, “工作流程”, “/research:summarize — 单个来源的摘要”, 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 research-summarizer 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 “命令行工具 / 该技能的触发条件 / 工作流程” 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 / shell-exec; 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.