Remove unpublished nm and proceed skills; support draft/local skill development workflow

[krisrowe]

Problem

nm and proceed are published in the marketplace but haven't been validated — they may not add value or function correctly. Publishing untested skills adds noise to the marketplace and to the echoskill.ai showcase. There's no mechanism to:

1. Keep a skill in the repo for development/testing without it appearing on the public showcase
2. Mark a skill as "not ready" so it's excluded from discovery and installation
3. Develop and test skills locally without losing track of which ones should eventually be published

Proposed solution

Immediate: remove nm and proceed from the marketplace

These should be removed from the published repo until they're validated. They can live locally (in ~/.claude/skills/ or a private repo) during development.

Longer-term: support unpublished/draft skills

Two mechanisms needed:

1. Draft/unpublished flag in the marketplace

A way to keep a skill in the repo (for version control and collaboration) without it appearing in em skills list or on echoskill.ai. Options:

• Frontmatter field: published: false or draft: true
• Collection-level: a drafts/ collection that em skills list and the showcase site skip by default
• .marketplace config: an exclude list of skill names or paths

Whichever mechanism is chosen, it should be simple — one field or one folder, not a multi-step process.

2. Local skill development workflow

A clear path for: create skill locally → test it → iterate → publish when ready. Currently there's no way to have a local skill that's tracked as "should eventually be published" without it already being in the marketplace repo. This could be as simple as a local manifest or a em skills draft command that tracks intent.

Work breakdown

• Remove prompting/nm/ from the echoskill repo
• Remove prompting/proceed/ from the echoskill repo
• Uninstall both locally: em skills uninstall nm && em skills uninstall proceed
• Design the draft/unpublished mechanism (frontmatter field vs. collection vs. config)
• Implement in em skills list to skip draft skills by default (with --include-drafts flag)
• Implement in echoskill.ai showcase to exclude draft skills
• Document the local development → publish workflow in CONTRIBUTING.md

[krisrowe]

Note: disable-model-invocation: true on nm and proceed is correct — it's official Claude Code frontmatter that prevents the agent from auto-triggering slash-command-only skills. This field should be preserved if these skills return in any form. It's not a hack or workaround.