De-AI-ify

Remove AI-generated jargon and restore human voice to text

Security Scan

The skill's instructions and requirements align with its stated purpose (editing a provided file to remove AI-like phrasing); it has no installs, no credential requests, and is instruction-only.

Purpose & Capability

Name and description (remove AI jargon and restore human voice) match the runtime instructions: the SKILL.md describes reading a source file, producing a '-HUMAN' copy, applying transformations, and producing a change log. Nothing requested (no env vars, no binaries) appears unnecessary for a file-editing text transformation.

Instruction Scope

The instructions explicitly tell the agent to 'Read original file' and create a copy with a '-HUMAN' suffix. That is expected for a file-editing skill, but it means the agent will read whatever file path the user supplies — including potentially sensitive system files if the user provides them. The instructions do not transmit data externally or request additional context beyond the file, and they do not instruct reading other environment variables or unrelated paths.

Install Mechanism

No install spec and no code files (instruction-only). This is the lowest-risk install model: nothing is downloaded or written by an installer.

Credentials

No environment variables, credentials, or config paths are requested. The lack of secret/credential access is proportionate to the described text-editing function.

Persistence & Privilege

The skill is not flagged as always: true and does not request persistent system changes. It will operate only when invoked. Note: the platform default allows autonomous invocation, but there are no other indicators (no persistent installs or credential writes) that increase privilege.

Assessment

This skill is internally consistent for editing files, but be cautious when using it: 1) Only pass file paths you intend to edit — do not point it at system files, private keys, or other secrets. 2) Because it writes a new file with a '-HUMAN' suffix, review the output and change log before publishing or replacing originals. 3) The skill author and source are unknown and there is no homepage; if provenance matters for your workflow, prefer skills from known authors or test on non-sensitive sample files first. 4) The skill does not transmit data externally or request credentials, so the main risk is accidental exposure from supplying sensitive file paths.

De-AI-ify Text

Remove AI-generated patterns and restore natural human voice to your writing.

Usage

/de-ai-ify <file_path>

What Gets Removed

1. Overused Transitions

• "Moreover," "Furthermore," "Additionally," "Nevertheless"
• Excessive "However" usage
• "While X, Y" openings

2. AI Cliches

• "In today's fast-paced world"
• "Let's dive deep"
• "Unlock your potential"
• "Harness the power of"

3. Hedging Language

• "It's important to note"
• "It's worth mentioning"
• Vague quantifiers: "various," "numerous," "myriad"

4. Corporate Buzzwords

• "utilize" → "use"
• "facilitate" → "help"
• "optimize" → "improve"
• "leverage" → "use"

5. Robotic Patterns

• Rhetorical questions followed by immediate answers
• Obsessive parallel structures
• Always using exactly three examples
• Announcement of emphasis

What Gets Added

Natural Voice

• Varied sentence lengths
• Conversational tone
• Direct statements
• Specific examples

Human Rhythm

• Natural transitions
• Confident assertions
• Personal perspective
• Authentic phrasing

Process

1. Read original file
2. Create copy with "-HUMAN" suffix
3. Apply de-AI-ification
4. Provide change log

Output

You'll get:

• A new file with natural human voice
• Change log showing what was fixed
• List of places needing specific examples

Example Transformations

Before (AI): "In today's rapidly evolving digital landscape, it's crucial to understand that leveraging AI effectively isn't just about utilizing cutting-edge technology—it's about harnessing its transformative potential to unlock unprecedented opportunities."

After (Human): "AI works best when you use it for specific tasks. Focus on what it does well: writing code, analyzing data, and answering questions."