humanize
Transform AI-generated text into natural, human-like content that bypasses AI detectors like GPTZero, Turnitin, and Originality.ai. Uses credits based on word count.
What this skill does
# Humanize AI Text
Transform AI-generated content into natural, human-like writing using the HumanizerAI API.
## How It Works
When the user invokes `/humanize`, you should:
1. Parse $ARGUMENTS for text and optional --intensity flag
2. Call the HumanizerAI API to humanize the text
3. Present the humanized text with before/after scores
4. Show remaining credits
## Parsing Arguments
The user may provide:
- Just text: `/humanize [their text]`
- With intensity: `/humanize --intensity aggressive [their text]`
Default intensity is `medium`.
## Intensity Levels
| Value | Name | Description | Best For |
|-------|------|-------------|----------|
| `light` | Light | Subtle changes, preserves style | Already-edited text, low AI scores |
| `medium` | Medium | Balanced rewrites (default) | Most use cases |
| `aggressive` | Bypass | Maximum bypass mode | High AI scores, strict detectors |
## API Call
Make a POST request to `https://humanizerai.com/api/v1/humanize`:
```
Authorization: Bearer $HUMANIZERAI_API_KEY
Content-Type: application/json
{
"text": "<user's text>",
"intensity": "medium"
}
```
## Response Format
Present results like this:
```
## Humanization Complete
**Score:** X → Y (improvement)
**Words Processed:** N
**Credits Remaining:** X
---
### Humanized Text
[The humanized text]
---
[Recommendation based on final score]
```
## Credit Usage
- 1 word = 1 credit
- Detection is free
- Check credits at https://humanizerai.com/dashboard
## Error Handling
### Insufficient Credits
If the user doesn't have enough credits:
1. Show how many credits are needed vs available
2. Direct them to https://humanizerai.com/dashboard to top up
### Invalid API Key
1. Check HUMANIZERAI_API_KEY environment variable
2. Direct to https://humanizerai.com to get a key
### Rate Limit
If rate limited, suggest waiting or upgrading to Business plan.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.