メニュー
Learned from user correction: Correction: Avoid: 'misss any info'
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Detect AI writing patterns in text. Use when: (1) need to check if text sounds AI-generated, (2) reviewing content before publication, (3) analyzing writing for Wikipedia-style AI markers, (4) generating report-only analysis without changes.
Use when: (1) User asks to "review for AI writing" or "check for LLM signs" (2) User wants to "detect AI-generated text" or "humanize this document" (3) User wants to identify and fix signs of AI/LLM-generated writing (4) User mentions Wikipedia AI writing guidelines
Fix AI writing patterns in text. Use when: (1) ai-writing-analyzer found issues to fix, (2) need to humanize AI-generated content, (3) preparing content for publication, (4) iteratively refining text until clean.
Humanize a document by removing AI-writing patterns via a multi-agent workflow (analyze → revise → adversarial review → loop-until-clean). Use when the user asks to "humanize", "de-AI", "remove AI tells", or "review for AI writing" on a file.
Fix for Claude Code slash command frontmatter that fails to parse when `argument-hint:` is given square-bracketed placeholder values. Use when: (1) authoring `commands/<name>.md` files in a CC plugin and the frontmatter shows `argument-hint: [working-dir] [team-name]` or similar multi-token bracketed values; (2) a frontmatter-validation test (e.g. `yaml.safe_load(block)` over the SKILL/command frontmatter) raises `ScannerError` or `ConstructorError` complaining about flow sequences or "expected a mapping"; (3) the slash command silently doesn't appear in `/help` after install, or a plugin-marketplace test asserting the `description` field is present trips because the whole frontmatter parse blew up. The fix is to QUOTE the value as a single string. Covers the same trap for `commands/<name>.md` directly authored in CC format AND APM-managed marketplaces shipping commands via APM.
Organize GitHub repository issues with proper milestones, native relationships, and clean labeling structure. Use when grooming issues, setting up milestones, establishing dependencies, or cleaning up issue tracking in a GitHub repository.
| name | correction-avoid-misss-any |
| description | Learned from user correction: Correction: Avoid: 'misss any info' |
| author | Claude Code (extracted by Claudeception v4.0) |
| version | 1.0.0 |
| date | "2026-02-02T00:00:00.000Z" |
| tags | ["correction","learned","negation_reference"] |
| level | user |
| breakthrough_score | 3.06 |
this is too compack. Lets have 3 pages. Make sure we dont misss any info
When making similar mistakes to: negation_reference
Correction: Avoid: 'misss any info'
