aops-tools/skills/style/SKILL.md
Analyze writing samples and create a comprehensive personal writing style guide
npx skillsauth add nicsuzor/academicops aops-tools/skills/styleInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Instructions for Large Language Models
This document provides step-by-step instructions for an LLM to analyze someone's writing samples and create a comprehensive personal writing style guide. Follow each phase sequentially, asking for user input only when specified.
You will help a user create a detailed personal writing style guide by:
The final product should be a working document that enables consistent, authentic writing that matches their personal voice.
Say to the user:
"I'll help you create a personal writing style guide by analyzing your existing writing. I need 5-10 pieces of writing that feel most authentically 'you' - pieces where you felt confident and natural while writing.
Please provide:
- 5-10 writing samples (any format: emails, blog posts, social media posts, articles, reports, presentations)
- Mix of contexts (professional, personal, formal, casual)
- Recent work preferred (represents your current voice)
- Your best work (pieces you're proud of or that got positive responses)
You can paste the text directly, provide links, or upload documents. What works best for you?"
Once you receive the samples:
Analyze the writing samples for these specific elements:
Create detailed lists of:
Look for what they DON'T do:
Create a comprehensive style guide document with these sections:
### 1. [Primary Quality - e.g., "Direct but Thoughtful"]
**Description**: [How this shows up in their writing]
**Example**: "[Quote from their writing that demonstrates this]"
**In practice**: [Specific guidance for applying this quality]
### 2. [Secondary Quality]
[Same structure]
### Words and Phrases They Use
**For [specific context]**: "[Their actual phrases]"
**For [situation type]**: "[Their typical responses]"
**Transition words**: "[Their preferred connectors]"
### Words and Phrases They Avoid
**Never use**: "[Specific phrases absent from their writing]"
**Instead of** "[common alternatives]" **they use**: "[their authentic versions]"
### Content Organization
**Opening style**: [How they typically begin pieces]
**Development pattern**: [How they build arguments/present information]\
**Supporting evidence**: [How they incorporate examples, data, or sources]
**Conclusion approach**: [How they end pieces]
### Formatting Preferences
**Emphasis techniques**: [Bold, italics, caps, other approaches they use]
**List usage**: [When they use bullets vs numbers vs prose]
**Paragraph length**: [Short and frequent vs longer blocks]
### Professional vs Personal Writing
[Document specific changes between contexts]
### Platform/Format Adaptations
[Note any differences for social media, email, formal documents, etc.]
### Audience Considerations
[How they adjust for different readers or expertise levels]
### Avoid These Response Patterns
**Never start with**: "[Phrases they don't use]"
**Never use**: "[Language patterns absent from their work]"
**Avoid**: "[Structural approaches they don't employ]"
Add a section with:
### Strong Examples from Their Writing
**[Context 1]**: "[Direct quote showing their voice in this context]"
**[Context 2]**: "[Quote from different context showing adaptation]"
### Before/After Transformations
**Generic version**: "[Standard/corporate way of saying something]"
**Their voice**: "[How they would actually phrase it]"
Present the draft style guide to the user with:
"Here's your draft personal writing style guide based on analyzing your writing samples. Before we finalize it, I'd like to test whether this guide actually captures your voice.
I'm going to write a sample piece using this guide, then ask for your feedback on what sounds right and what needs adjustment.
Test scenario: [Choose a scenario relevant to their work/interests - could be explaining a concept, responding to a question, or writing about a current event]"
Then write a 2-3 paragraph sample using the style guide.
After presenting the test writing, ask:
"How does this sound to you? Please give me specific feedback on:
- What sounds authentically like you? (quote specific phrases or approaches)
- What feels off or not quite right? (again, specific quotes or patterns)
- What's missing? (voice elements I didn't capture)
- What did I overemphasize? (patterns I focused on too much)
- Are there any words or phrases here you would never actually use?
The more specific you can be, the better I can refine the guide."
Based on their feedback:
Create one more test sample using the refined guide and ask:
"Here's a revised sample using your feedback. Does this feel more accurate to how you would naturally write this?"
Continue refining until they confirm it sounds authentically like them.
Present the complete, refined style guide in a well-organized document format that includes:
Include instructions on how to use the guide:
"## How to Use This Style Guide
For AI writing assistance:
- Share this complete guide with any AI tool you use for writing
- Reference specific sections when requesting content in particular contexts
- Use the examples and anti-patterns to clarify what you want
For self-editing:
- Review the 'Words/Phrases to Avoid' list before publishing
- Check that your content matches the structural preferences
- Confirm the voice characteristics show through in your final draft
For collaborators:
- Share relevant sections with editors or team members
- Use the examples to show what 'sounds like you'
- Reference the context adaptations for different formats or audiences"
The style guide is successful when:
You have now created a comprehensive personal writing style guide that captures their authentic voice and enables consistent, natural-sounding content creation.
tools
Program / portfolio supervision — the autonomous top loop above /supervisor. "Ready the release" → discover and decompose the constituent epics → run /supervisor on each → surface only escalations + merge-ready PRs. Stateless tick driven by /loop; all cross-tick state lives in the program task body.
development
Mirror PKB tasks onto the Cowork native task list at claim time and sync completion back to PKB. Cowork-only; ships only in the cowork build of aops-core.
testing
Instruction quality gate — reviews agent instructions (task bodies, workflow steps, skill procedures, self-test protocols) for shallow-execution vulnerabilities before deployment. Two modes: author (pre-hoc review) and audit (trace a failure back to the instruction gap). The bar is excellence, not compliance.
content-media
Design-stage fitness rubric — persona immersion, scenario design, dimensions that define what excellence looks like for the people a feature serves. Two modes — author (produce a rubric for a new spec) and critique (red-team an existing spec). Output lives on the spec, not in the verification brief. Owned by pauli.