Excel / WPS Table Diagnosis

v1.0.0

Diagnose spreadsheet structure and recommend practical Excel/WPS-compatible formulas and workflows for cleaning, lookup and matching, summarization, text and...

0· 237·0 current·0 all-time
byWinston@winstonice-prog

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for winstonice-prog/excel-wps-table-diagnosis.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Excel / WPS Table Diagnosis" (winstonice-prog/excel-wps-table-diagnosis) from ClawHub.
Skill page: https://clawhub.ai/winstonice-prog/excel-wps-table-diagnosis
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install excel-wps-table-diagnosis

ClawHub CLI

Package manager switcher

npx clawhub@latest install excel-wps-table-diagnosis
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name, description, and included files (SKILL.md, WORKFLOW.md, examples, docs) align with a purely advisory spreadsheet-diagnosis skill. There are no unrelated credentials, binaries, or install steps requested.
Instruction Scope
SKILL.md limits behavior to inspecting table headers/sample rows, diagnosing issues, recommending formulas/workflows, and pausing before making direct changes. It does not instruct reading system files, accessing hidden endpoints, or exfiltrating data.
Install Mechanism
No install spec and no code files that would be fetched or executed. Being instruction-only minimizes on-disk risk.
Credentials
The skill requests no environment variables, credentials, or config paths. The requested resources are proportionate to an advisory spreadsheet skill.
Persistence & Privilege
always is false and there is no install or persistent agent modification. agents/openai.yaml sets allow_implicit_invocation: true, which allows implicit invocation metadata but does not elevate privileges or request persistent access to credentials.
Assessment
This skill is instruction-only and appears coherent and low-risk: it only asks for table headers/sample rows and provides advice before doing any direct edits. Before you use it, confirm you will paste only the non-sensitive sample data (no full confidential spreadsheets), and explicitly approve any execution steps the skill proposes. Note that the agent metadata allows implicit invocation in some UIs — if you prefer explicit control, check your platform settings so the skill cannot be invoked without your prompt. If you later integrate this with services that open or modify real workbook files or cloud storage, verify and restrict any added credentials to the minimum necessary.

Like a lobster shell, security has layers — review code before you run it.

data-cleaningvk97ddde4pyxvc5j9r4aeaxv1gx83ws9zexcelvk97ddde4pyxvc5j9r4aeaxv1gx83ws9zformulavk97ddde4pyxvc5j9r4aeaxv1gx83ws9zlatestvk97ddde4pyxvc5j9r4aeaxv1gx83ws9zlookupvk97ddde4pyxvc5j9r4aeaxv1gx83ws9zspreadsheetvk97ddde4pyxvc5j9r4aeaxv1gx83ws9zworkflowvk97ddde4pyxvc5j9r4aeaxv1gx83ws9zwpsvk97ddde4pyxvc5j9r4aeaxv1gx83ws9z
237downloads
0stars
1versions
Updated 4w ago
v1.0.0
MIT-0

Excel/WPS Table Diagnosis

Use this skill when a spreadsheet task should start with the table itself, not with a guess at the formula.

Core Approach

  1. Inspect the input.
  • Identify whether the user provided headers, sample rows, CSV content, or only a task description.
  • If the structure is unclear, ask for the smallest missing detail that would change the recommendation.
  1. Diagnose the table.
  • Identify likely column types such as IDs, dates, amounts, names, status fields, phone numbers, or free text.
  • Look for blanks, duplicates, mixed formats, unstable lookup keys, and columns that should be cleaned before formulas are applied.
  1. Choose the most practical path.
  • Prefer simple formulas when they are stable and readable.
  • Prefer Excel and WPS compatible approaches over newer functions with weaker compatibility.
  • Prefer helper columns when a single long formula would be fragile.
  • Recommend built-in spreadsheet tools when they are a better fit than formulas.
  1. Present a clear recommendation.
  • State what the table appears to contain.
  • State what should be done first.
  • Recommend the formula or workflow.
  • Mention compatibility notes for Excel and WPS.
  • Provide a fallback when the preferred formula may not work everywhere.
  1. Pause before execution.
  • If the next step would directly modify a workbook, add helper columns, rewrite formulas, or otherwise move from diagnosis into execution, ask for confirmation first.
  • Once the user agrees, continue with the concrete formulas, helper columns, or execution steps instead of repeating the analysis.
  • If the scope is already clear, finish the approved execution step before suggesting extra optional follow-up work.

Priorities

  • Diagnose before suggesting formulas.
  • Prefer maintainability over cleverness.
  • Treat compatibility as an early constraint.
  • Do not force everything into one formula.
  • Do not make direct spreadsheet changes without user confirmation.

Output Shape

Keep the response close to this shape:

Diagnosis

  • what the table likely contains
  • what looks inconsistent or risky

Recommendation

  • what to do first
  • which formula or method to use

Execution

  • what can be done immediately after approval
  • which formulas, helper columns, or spreadsheet steps should be applied

Compatibility

  • whether it should work in Excel
  • whether it should work in WPS
  • what fallback to use if needed

Notes

  • where to place the formula
  • whether helper columns or built-in tools would be easier

References

  • Read WORKFLOW.md for the longer working notes.
  • Read docs/use-cases.md for common task shapes.
  • Read examples/README.md for example inputs and outputs.

Comments

Loading comments...