Repository navigation
chore: v1.1 polish — skills, panel fixes, README SEO #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 4 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
a120e63
refactor: rewrite built-in skills with CSO-optimized structure
Astro-Han 37e26c1
fix: right panel auto-open reads from Snapshot instead of message sum…
Astro-Han 47b2817
fix: highlight file-tree button when side panel is open on any tab
Astro-Han 1878d17
docs: rewrite READMEs for search discoverability
Astro-Han 412a8ec
fix: use Snapshot diffs with turnDiffs fallback for panel auto-open
Astro-Han a83bdd6
fix: revert file-tree button highlight to track Files tab only
Astro-Han 2e65105
docs: add modification notice to credits for Apache-2.0 compliance
Astro-Han File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,51 +1,41 @@ | ||
| --- | ||
| name: data-analysis | ||
| description: Analyze spreadsheets and CSVs, create charts, and produce structured reports. | ||
| description: Use when user wants analysis, charts, summaries, or reports from spreadsheets, CSVs, or tabular data | ||
| --- | ||
|
|
||
| # Data Analysis | ||
|
|
||
| Use this skill when the user wants analysis, summaries, charts, comparisons, or report-ready tables from local files. | ||
| Analyze local data files: xlsx, csv, tsv. Produce summaries, charts, or reports. If user mainly needs prose, do analysis here first, hand off tone to `writing-assistant`. | ||
|
|
||
| ## Scene Detection | ||
| ## Clarify Before Acting | ||
|
|
||
| - Use for spreadsheets, csv, tsv, charting, KPI summaries, comparisons, and report outputs. | ||
| - If the user mainly needs copywriting or a memo, do the analysis here first and hand off final prose tone to `writing-assistant` only if needed. | ||
| Use `question` if the business question is vague. Skip when the request is already specific. | ||
|
|
||
| ## question Flow | ||
| - Which file(s) contain the data | ||
| - What question should the analysis answer | ||
| - Desired output: report, chart image, updated spreadsheet, or all three | ||
| - Key dimensions, metrics, or date ranges | ||
|
|
||
| Use question to confirm: | ||
| ## Tool Selection | ||
|
|
||
| 1. Which file or files contain the data? | ||
| 2. What question should the analysis answer? | ||
| 3. Do they want a report, a chart image, an updated spreadsheet, or all three? | ||
| 4. Are there date ranges, dimensions, or metrics that matter most? | ||
| | Task | Tool | | ||
| |------|------| | ||
| | xlsx with formulas/structure | `officecli` | | ||
| | csv/tsv parsing, reshaping | Node.js | | ||
| | Chart/image output | `sharp` | | ||
|
|
||
| If the business question is vague, force clarity before running analysis. | ||
| Stay within local files and bundled tools. | ||
|
|
||
| ## Workflow | ||
|
|
||
| 1. Inspect the schema and identify the relevant tables, sheets, and columns. | ||
| 2. Validate obvious data-quality issues, missing values, malformed dates, duplicate rows, or mixed units. | ||
| 3. Run the requested aggregation or comparison. | ||
| 4. Produce the requested outputs, spreadsheet, chart image, report, or a combination. | ||
| 5. State the main finding first, then supporting detail. | ||
| 1. Inspect schema: tables, sheets, columns | ||
| 2. Flag data-quality issues (missing values, duplicates, mixed units) | ||
| 3. Run aggregation or comparison | ||
| 4. Produce requested outputs | ||
| 5. State the main finding first, then supporting detail | ||
|
|
||
| ## Tool Rules | ||
| ## Guardrails | ||
|
|
||
| - Prefer `officecli` for xlsx reading and writing when formulas or workbook structure matter. | ||
| - Use Node.js parsing for csv and tsv plus lightweight table reshaping. | ||
| - Use `sharp` only for chart or image output generation. | ||
| - Do not require `opencli`. Stay within local files and bundled tools. | ||
|
|
||
| ## Error Handling and Degradation | ||
|
|
||
| - If the data is incomplete, contradictory, or suspicious, call it out explicitly instead of smoothing it over. | ||
| - If a chart cannot be produced cleanly, return the analysis table and explain what blocked the chart. | ||
| - If the workbook is too complex for safe rewriting, write a separate output file instead of corrupting the original. | ||
|
|
||
| ## Output Requirements | ||
|
|
||
| - State the main finding first. | ||
| - Include the exact file path for any generated spreadsheet, image, or report. | ||
| - If data quality looks suspicious, call it out explicitly instead of smoothing it over. | ||
| - Data incomplete or suspicious → call it out explicitly, don't smooth over | ||
| - Chart can't render cleanly → return analysis table, explain what blocked it | ||
| - Workbook too complex for safe rewriting → write a separate output file |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,53 +1,39 @@ | ||
| --- | ||
| name: document-processing | ||
| description: Handle Word, Excel, PowerPoint, PDF, and mixed office-file requests. | ||
| description: Use when user wants to create, edit, convert, or extract from Word, Excel, PowerPoint, or PDF files | ||
| --- | ||
|
|
||
| # Document Processing | ||
|
|
||
| Use this skill when the user wants to create, edit, convert, clean up, or extract information from office documents. | ||
| Process office documents: docx, xlsx, pptx, pdf, csv. Pure writing requests without source files → `writing-assistant`. | ||
|
|
||
| ## Scene Detection | ||
| ## Clarify Before Acting | ||
|
|
||
| - Use for docx, xlsx, pptx, pdf, or mixed office-file workflows. | ||
| - Do not use for pure writing requests without source files. Route those to `writing-assistant`. | ||
| - Do not guess the target format from the input extension alone. Follow the requested output. | ||
| Use `question` if ambiguous. Skip when the request is already specific. | ||
|
|
||
| ## question Flow | ||
| - Source file(s) and target format | ||
| - New file, edit, or conversion | ||
| - What must stay unchanged (layout, formulas, branding) | ||
|
|
||
| Use question to collect the missing execution constraints before touching files. Ask for: | ||
| ## Tool Selection | ||
|
|
||
| 1. Which file or files are the source material? | ||
| 2. What output format do they want, docx, xlsx, pptx, pdf, or plain text? | ||
| 3. Is this a new file, an edit to an existing file, or a conversion? | ||
| 4. What must stay unchanged, layout, formulas, page order, wording, or branding? | ||
|
|
||
| If any of those are missing and the wrong choice would change the output, stop and ask before proceeding. | ||
| | Format | Tool | | ||
| |--------|------| | ||
| | docx, xlsx, pptx | `officecli` | | ||
| | PDF merge/split/fill/extract | `pdf-lib` | | ||
| | Mixed formats | Decide final output format first | | ||
|
|
||
| ## Workflow | ||
|
|
||
| 1. Inspect the source files and confirm the requested output. | ||
| 2. Choose the least-destructive toolchain for that file type. | ||
| 3. Make the edit or conversion. | ||
| 4. Verify the output exists and still matches the non-negotiable constraints. | ||
| 5. Report exactly what changed and where the file was written. | ||
|
|
||
| ## Tool Rules | ||
|
|
||
| - Prefer `officecli` for docx, xlsx, and pptx read or write tasks. | ||
| - Use `pdf-lib` only for PDF-specific work, merge, split, reorder, fill, stamp, or extract. | ||
| - If the request mixes office files and PDF, decide the final output format before editing. | ||
| - If the input is ambiguous, ask before editing the wrong file. | ||
| - When creating output, save it inside the current PawWork workspace unless the user gives a different path. | ||
|
|
||
| ## Error Handling and Degradation | ||
|
|
||
| - If formatting fidelity is uncertain, warn before you finalize. | ||
| - If a requested conversion would destroy formulas, layout, comments, or pagination, explain the tradeoff and offer a safer alternative. | ||
| - If a file cannot be parsed by the preferred tool, say which file failed and switch to the closest safe fallback instead of silently skipping it. | ||
| 1. Inspect source files, confirm requested output | ||
| 2. Choose least-destructive toolchain for the file type | ||
| 3. Make the edit or conversion | ||
| 4. Verify output matches constraints | ||
| 5. Report what changed and where the file was saved | ||
|
|
||
| ## Output Requirements | ||
| ## Guardrails | ||
|
|
||
| - Say which file you created or changed. | ||
| - If formatting fidelity is uncertain, warn the user before finishing. | ||
| - If a requested conversion cannot preserve structure, offer the closest safe alternative. | ||
| - Conversion would destroy formulas/layout/comments → explain tradeoff, offer alternative | ||
| - Formatting fidelity uncertain → warn before finalizing | ||
| - File can't be parsed → name the file, switch to closest safe fallback | ||
| - Save output in current workspace unless user specifies a path |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,50 +1,40 @@ | ||
| --- | ||
| name: writing-assistant | ||
| description: Draft and revise work writing such as emails, reports, plans, and copy. | ||
| description: Use when user wants to draft or revise work writing like emails, reports, plans, announcements, or copy | ||
| --- | ||
|
|
||
| # Writing Assistant | ||
|
|
||
| Use this skill when the user wants help writing or rewriting business content. | ||
| Draft and revise business content. If the request is mostly file transformation or analysis, finish that first, use this skill only for the writing pass. | ||
|
|
||
| ## Scene Detection | ||
| ## Clarify Before Acting | ||
|
|
||
| - Use for emails, reports, plans, announcements, summaries, and work copy. | ||
| - If the request is mostly file transformation or analysis, finish that work first and only use this skill for the writing pass. | ||
| Use `question` if ambiguous. Skip when the request is already specific. | ||
|
|
||
| ## question Flow | ||
| - Content type (email, report, announcement, plan, copy) | ||
| - Audience | ||
| - Tone (concise, warm, formal, direct, persuasive) | ||
| - Length or structure constraints | ||
|
|
||
| Use question to collect: | ||
|
|
||
| 1. What are they writing, email, weekly update, announcement, report, or copy? | ||
| 2. Who is the audience? | ||
| 3. What tone should it have, concise, warm, formal, direct, or persuasive? | ||
| 4. What length or structure do they want? | ||
|
|
||
| If the user gives weak or fragmented source notes, ask for the missing facts before drafting as if you know them. | ||
| If source notes are thin, ask for missing facts before drafting. | ||
|
|
||
| ## Workflow | ||
|
|
||
| 1. Identify the content type and audience. | ||
| 2. Pull facts, constraints, deadlines, and asks from the user's notes. | ||
| 3. If the input is thin, propose a brief structure before writing long-form output. | ||
| 4. Draft the response in the requested tone. | ||
| 5. Tighten for clarity, remove filler, and check that every claim is sourced from the provided material. | ||
| 1. Identify content type and audience | ||
| 2. Extract facts, constraints, deadlines from user's notes | ||
| 3. If input is thin, propose structure before writing long-form | ||
| 4. Draft in requested tone | ||
| 5. Tighten: remove filler, verify every claim is from provided material | ||
|
|
||
| ## Working Rules | ||
|
|
||
| - Default to clear, concrete wording and short paragraphs. | ||
| - If the user provides source notes, preserve facts and tighten wording. | ||
| - If they provide no material, propose a sensible structure before drafting long content. | ||
| - Do not invent facts, names, numbers, or commitments. | ||
|
|
||
| ## Error Handling and Degradation | ||
|
|
||
| - If required facts are missing, ask instead of hallucinating. | ||
| - If two plausible tones fit, provide the stronger default first and note the alternative briefly. | ||
| - If the request mixes drafting and strategy, separate the final copy from the advice so the user can use the output immediately. | ||
| - Default: clear wording, short paragraphs | ||
| - Preserve facts from source notes, tighten wording | ||
| - Never invent facts, names, numbers, or commitments | ||
| - Return polished copy, not brainstorming fragments (unless user asks for outline) | ||
|
|
||
| ## Output Requirements | ||
| ## Guardrails | ||
|
|
||
| - Return polished copy, not brainstorming fragments, unless the user explicitly asks for an outline. | ||
| - If there are two plausible tones, give the stronger default first and mention the alternative briefly. | ||
| - Missing facts → ask, don't hallucinate | ||
| - Two plausible tones → give stronger default first, mention alternative | ||
| - Mixed drafting + strategy → separate final copy from advice so output is immediately usable |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.