ワンクリックで
editing
// Edit and improve existing text for clarity, tone, grammar, and structure. Use when the user submits text for review, asks to improve writing, or needs proofreading.
// Edit and improve existing text for clarity, tone, grammar, and structure. Use when the user submits text for review, asks to improve writing, or needs proofreading.
Review code for bugs, security issues, performance problems, and style violations. Use when the user asks for a code review, submits code for feedback, or wants to improve code quality.
Create polished written content including blog posts, documentation, emails, reports, and marketing copy. Use when the user needs to write, draft, or generate any form of text content.
Analyze datasets, identify patterns, compute statistics, and generate summary reports. Use when the user provides data to analyze, asks about trends, or needs statistical insights.
Systematically diagnose and fix bugs in code. Use when the user reports an error, unexpected behavior, test failure, or needs help troubleshooting.
Search the web for current information, verify facts across multiple sources, and compile cited research summaries. Use when the user asks factual questions, needs current data, or requests research on any topic.
| name | editing |
| description | Edit and improve existing text for clarity, tone, grammar, and structure. Use when the user submits text for review, asks to improve writing, or needs proofreading. |
| metadata | {"author":"symphony","version":"1.0"} |
Activate this skill when the user:
Fix only:
Everything in proofreading, plus:
Everything in copy editing, plus:
For small edits (under 100 words), show before/after:
**Before**: The system was very slow and it had a lot of bugs that were causing problems.
**After**: The system suffered from poor performance and numerous bugs.
**Why**: Removed filler words; combined redundant phrases.
For larger edits, provide the revised text with a summary of changes:
## Revised Text
[full revised text]
## Changes Made
1. Restructured opening paragraph for stronger hook
2. Removed redundant sentences in section 2
3. Fixed subject-verb agreement throughout
4. Tightened conclusion to focus on call to action