What Information Is in plugin-submission.md? Complete Guide to the No AI Slop Plugin Specification

The plugin-submission.md file serves as the formal behavioral contract for the No AI Slop plugin, defining its core purpose, invocation prompts, test criteria, and release notes.

The plugin-submission.md file in the petergyang/no-ai-slop repository functions as the canonical specification document that governs how the plugin identifies and removes "sloppy" AI-assisted writing patterns. This file establishes the plugin's positioning, provides starter prompts for users, defines positive and negative test cases, and tracks version history.

Plugin Positioning and Purpose

According to lines 5-7 of plugin-submission.md, the plugin targets more than 20 specific sloppy patterns that make AI-generated text sound generic. The specification emphasizes preserving the author's voice while eliminating robotic phrasing, distinguishing this tool from standard grammar checkers.

Starter Prompts for Invocation

Lines 11-13 document the two canonical prompts that trigger the plugin's behavior. These serve as the primary user interface contract.

Edit Mode Prompt

To activate the editing workflow:

@No AI Slop (text)

Replace (text) with the content you want refined. When invoked this way, the plugin enters edit mode, returning the fully edited version plus a "What changed" summary as required by positive test case #1.

Detect Mode Prompt

To audit text without modifying it:

@No AI Slop is this slop? (text)

This prompt triggers detect mode, causing the plugin to list identified patterns with quoted offending lines without performing rewrites.

Test Cases and Behavioral Requirements

The specification (lines 15-27) rigorously defines when the plugin should engage and when it should remain passive.

Positive Test Cases

Lines 15-21 outline five concrete scenarios the plugin must handle, including:

• Editing rough emails while preserving the original tone
• Removing generic transitions without destroying narrative flow
• Handling technical documentation with precise terminology intact

Negative Test Cases

Lines 22-27 establish three critical non-engagement rules:

• Factual queries without prose: When users ask questions like "What is the capital of France?" without providing text to edit, the plugin must decline
• Empty context: Invocations without substantive text to analyze
• Non-textual content: Requests involving only code or data formats outside the plugin's scope

Example negative scenario handling:

User: "What is the capital of France?"

Expected plugin response:

I'm not set up to answer factual queries directly. If you provide a passage you'd like edited or audited, I can help remove slop patterns.

Release Notes and Version History

Lines 28-31 summarize changes introduced in version 1.0.6, including:

• A new logo for the plugin interface
• Simplified starter prompts for better usability
• Expanded directory descriptions
• Addition of distinct edit and detect modes with self-checking evaluations

Related Files in the Repository

The plugin-submission.md specification works in conjunction with several other critical files:

• SKILL.md: Located at skills/no-ai-slop/SKILL.md, provides general capability overview
• scripts/build_plugin.py: Packages the plugin for distribution according to the specification requirements
• .codex-plugin/plugin.json: The manifest at .codex-plugin/plugin.json defines metadata, entry points, and permissions referenced in the behavioral contract
• agents/openai.yaml: Configures the OpenAI agent that powers the language model interactions described in the test cases

Summary

• plugin-submission.md defines the complete behavioral contract for the No AI Slop plugin in the petergyang/no-ai-slop repository
• The specification mandates removal of 20+ sloppy patterns while preserving author voice
• Two canonical prompts trigger either edit mode (@No AI Slop) or detect mode (@No AI Slop is this slop?)
• Five positive test cases validate editing capabilities, while three negative test cases prevent inappropriate engagement
• Version 1.0.6 introduced simplified prompts and dual-mode functionality with self-checking evaluations

Frequently Asked Questions

What is the purpose of plugin-submission.md in the No AI Slop repository?

The plugin-submission.md file serves as the formal specification document that defines how the No AI Slop plugin behaves. It documents the plugin's positioning, starter prompts, test cases for validation, and release notes, functioning as the authoritative contract between developers and users.

How do I invoke the No AI Slop plugin using the prompts defined in plugin-submission.md?

According to the specification in lines 11-13, use @No AI Slop (text) to enter edit mode for rewriting content, or @No AI Slop is this slop? (text) to enter detect mode for auditing without modifications. Replace (text) with your actual content.

What test cases are documented in plugin-submission.md?

The file defines five positive test cases (lines 15-21) that verify the plugin correctly edits content while preserving voice, and three negative test cases (lines 22-27) that ensure the plugin declines factual queries, empty contexts, and non-textual requests.

What changes were introduced in version 1.0.6 according to the release notes?

Version 1.0.6, documented in lines 28-31, introduced a new logo, simplified starter prompts, expanded directory descriptions, and implemented distinct edit and detect modes with self-checking evaluation capabilities.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}