Skip to content

feat: add pattern scorecard to humanizer output #65

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.

Sign up for GitHub

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

Open
mvanhorn wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat: add pattern scorecard to humanizer output #65

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -133,6 +133,7 @@ The skill also includes a final "obviously AI generated" audit pass and a second

## Version History

- **2.4.0** - Added pattern scorecard: shows which patterns were detected before rewriting, and a change log after
- **2.3.0** - Added pattern #25: hyphenated word pair overuse
- **2.2.0** - Added a final "obviously AI generated" audit + second-pass rewrite prompts
- **2.1.1** - Fixed pattern #18 example (curly quotes vs straight quotes)
Expand Down
29 changes: 17 additions & 12 deletions SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
name: humanizer
version: 2.3.0
version: 2.4.0
description: |
Remove signs of AI-generated writing from text. Use when editing or reviewing
text to make it sound more natural and human-written. Based on Wikipedia's
Expand Down Expand Up @@ -382,26 +382,31 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as

1. Read the input text carefully
2. Identify all instances of the patterns above
3. Rewrite each problematic section
4. Ensure the revised text:
3. Output a pattern scorecard (see Output Format)
4. Rewrite each problematic section
5. Ensure the revised text:
- Sounds natural when read aloud
- Varies sentence structure naturally
- Uses specific details over vague claims
- Maintains appropriate tone for context
- Uses simple constructions (is/are/has) where appropriate
5. Present a draft humanized version
6. Prompt: "What makes the below so obviously AI generated?"
7. Answer briefly with the remaining tells (if any)
8. Prompt: "Now make it not obviously AI generated."
9. Present the final version (revised after the audit)
6. Present a draft humanized version
7. Prompt: "What makes the below so obviously AI generated?"
8. Answer briefly with the remaining tells (if any)
9. Prompt: "Now make it not obviously AI generated."
10. Present the final version (revised after the audit)

## Output Format

Provide:
1. Draft rewrite
2. "What makes the below so obviously AI generated?" (brief bullets)
3. Final rewrite
4. A brief summary of changes made (optional, if helpful)
1. **Pattern scan** - Table of detected patterns:
| # | Pattern | Instances |
|---|---------|-----------|
Only list patterns actually found. Skip patterns with 0 instances. Include the specific words or phrases that triggered each pattern.
2. Draft rewrite
3. "What makes the below so obviously AI generated?" (brief bullets)
4. Final rewrite
5. **Change log** - What was changed and which pattern each change addressed


## Full Example
Expand Down