PluginBench
Skill
Review
Audit score 70

catchtable-sniper

nomadamas/k-skill

Monitor Catchtable restaurant reservations and auto-book available slots via Chrome.

What is catchtable-sniper?

Watches a Korean restaurant reservation platform (Catchtable) for open booking slots and automatically attempts to reserve them using an authenticated Chrome session. Use this when you want to secure hard-to-get restaurant reservations without manual monitoring.

  • Monitors Catchtable for real-time availability changes
  • Automatically attempts booking when slots open
  • Uses existing logged-in Chrome session for authentication
  • Respects hard rules: requires explicit user approval before payment or final submission
  • Detects runtime environment and provides context-specific instructions

How to install catchtable-sniper

npx skills add https://github.com/nomadamas/k-skill --skill catchtable-sniper
Prerequisites
  • Chrome MCP (Model Context Protocol) integration
  • Active logged-in Catchtable session in Chrome
  • Node.js 18+ (for CLI-based instruction retrieval)
Claude Code
Cursor
Windsurf
Cline

How to use catchtable-sniper

  1. 1.Run `npx -y @nomadamas/k-skill@0 instruct catchtable-sniper` to retrieve full runtime-specific instructions
  2. 2.Ensure you have an active, logged-in Catchtable session in Chrome
  3. 3.Configure target restaurant, date, and time preferences
  4. 4.Start monitoring; the skill will alert when slots become available
  5. 5.Review and explicitly approve any booking before final submission

Use cases

Good for
  • Securing reservations at popular Korean restaurants with limited availability
  • Automating repetitive checking for tables at specific times or dates
  • Booking during high-demand periods when manual monitoring is impractical
Who it's for
  • Restaurant diners seeking hard-to-get reservations
  • Users familiar with Catchtable and Korean dining platforms
  • Anyone comfortable with browser automation for personal use

catchtable-sniper FAQ

Will this bypass CAPTCHAs or identity verification?

No. The skill explicitly respects legal and security boundaries including CAPTCHAs and identity-proofing requirements.

Can it complete payments automatically?

No. It requires explicit user approval before executing any payment, submission, or final booking action.

What if my Chrome session expires?

You must maintain an active logged-in Catchtable session; the skill uses your existing authentication and cannot re-authenticate.

Is this specific to Korean restaurants?

Yes, Catchtable is a Korean restaurant reservation platform; the skill is designed for that ecosystem.

Full instructions (SKILL.md)

Source of truth, from nomadamas/k-skill.


name: catchtable-sniper description: Monitor Catchtable for open reservation slots and attempt booking using a logged-in Chrome session. 돌쇠에서는 공식 표면을 통한 후속 액션까지 진행한다. license: MIT metadata: category: lifestyle subcategory: food locale: ko-KR phase: v1 requires: - Chrome MCP - Logged-in Catchtable Chrome session

catchtable-sniper

<!-- k-skill:cli-stub — generated by scripts/generate-skill-stubs.js; edit skill.json / instruction.md instead -->

Get the full instructions (required first step)

Run this and follow its output as the primary instructions for this skill:

npx -y @nomadamas/k-skill@0 instruct catchtable-sniper

The CLI detects the current runtime (Dolshoi vault/CloakBrowser vs generic) and prints only the applicable instructions, always up to date. Helper files bundled with the CLI are listed by:

npx -y @nomadamas/k-skill@0 files catchtable-sniper

If npx is unavailable, install Node.js 18+ or follow https://github.com/NomaDamas/k-skill#readme, or read the source instructions at https://github.com/NomaDamas/k-skill/blob/main/catchtable-sniper/instruction.md.

Hard rules even without the CLI

  • Never execute payment, message/email delivery, final submission, cancellation, or public posting without the user's explicit approval immediately beforehand.
  • Never ask for, print, or store plaintext credentials in chat, files, or shell arguments.
  • Never bypass legal, physical-presence, CAPTCHA, identity-proofing, or electronic-signature boundaries.