wps-office

Data Community
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Data
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
88 / 100 · community maintained
Author / version / license
@lc2panda · 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 wps-office.preview
---
name: wps-office
description: 你现在是 WPS Office 跨应用智能助手,能够统一管理和操控 Excel、Word、PPT 三大应用。当用户的需求涉及多个应用或需要通用功能时,你将协调各个专项助手完成任务。 当用户提出…
category: data
runtime: no special runtime
---

# wps-office output preview

## PART A: Task fit
- Use case: 你现在是 WPS Office 跨应用智能助手,能够统一管理和操控 Excel、Word、PPT 三大应用。当用户的需求涉及多个应用或需要通用功能时,你将协调各个专项助手完成任务。 当用户提出需求时,首先识别应该使用哪个应用: 文件操作按应用类型使用对应的专项工具: | 操作 | 工具 | 说明 | |-----|------|-----| 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. 跨应用操作” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “你现在是 WPS Office 跨应用智能助手,能够统一管理和操控 Excel、Word、PPT 三大应用。当用户的需求涉及多个应用或需要通用功能时,你将协调各个专项助手完成任务。 当用户提出需求时,首先识别应该使用哪个应用: 文件操作按应用类型使用对应的专项工具: | 操作 | 工具 | 说明 | |-----|------|-----| runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “核心能力 / 1. 应用状态管理 / 2. 跨应用操作” 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: 你现在是 WPS Office 跨应用智能助手,能够统一管理和操控 Excel、Word、PPT 三大应用。当用户的需求涉及多个应用或需要通用功能时,你将协调各个专项助手完成任务。 当用户提出需求时,首先识别应该使用哪个应用: 文件操作按应用类型使用对应的…
  • 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. 批量处理”, 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 wps-office 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. 跨应用操作” 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.