fluxly Search skills… ⌘K 中文 Publish

business-analysis-summary

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
@aifinlab · 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 business-analysis-summary.preview 
---
name: business-analysis-summary
description: 银行各条线、各维度的经营分析结果分散在不同报表和分析输出中，管理层需要一份结构清晰、结论先行的综合摘要。传统做法依赖人工汇总编写，耗时且容易遗漏关键信息或重点不突出。本技能将上游各分析技能的输…
category: other
runtime: no special runtime
---

# business-analysis-summary output preview

## PART A: Task fit
- Use case: 银行各条线、各维度的经营分析结果分散在不同报表和分析输出中，管理层需要一份结构清晰、结论先行的综合摘要。传统做法依赖人工汇总编写，耗时且容易遗漏关键信息或重点不突出。本技能将上游各分析技能的输出整合为标准化的经营分析摘要，确保关键结论前置、数据支撑充分、风险提示明确。 | 输入项 | 说明 | 是否必须 | |--------|------|----------| runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “1. 业务问题 / 2. 适用场景 / 3. 输入” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “银行各条线、各维度的经营分析结果分散在不同报表和分析输出中，管理层需要一份结构清晰、结论先行的综合摘要。传统做法依赖人工汇总编写，耗时且容易遗漏关键信息或重点不突出。本技能将上游各分析技能的输出整合为标准化的经营分析摘要，确保关键结论前置、数据支撑充分、风险提示明确。 | 输入项 | 说明 | 是否必须 | |--------|------|----------| runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “1. 业务问题 / 2. 适用场景 / 3. 输入” 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: 银行各条线、各维度的经营分析结果分散在不同报表和分析输出中，管理层需要一份结构清晰、结论先行的综合摘要。传统做法依赖人工汇总编写，耗时且容易遗漏关键信息或重点不突出。本技能将上游各分析技能的输出整合为标准化的经营分析摘要，确保关键结论前置、数据支撑充分、风…
  • 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 “1. 业务问题”, “2. 适用场景”, “3. 输入”, “4. 输出”, 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 business-analysis-summary 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 “1. 业务问题 / 2. 适用场景 / 3. 输入” 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.