mcpField
K
kstartup-search

kstartup-search

github.com/nomadamasProductivity8.2k5.9k installsUpdated 2d ago
Repository

About kstartup-search

A coding-agent skill named kstartup-search. Its README requires loading the current instructions through the k-skill CLI before use and specifies operational safeguards.

Key features

  1. 01Runtime-specific instructions via CLI
  2. 02Bundled helper-file listing
  3. 03CLI and skill update command
  4. 04Operational safety rules

Use cases

  1. 01Loading the skill's current instructions
  2. 02Reviewing safeguards before use

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nomadamas/k-skill --skill kstartup-search

After installing, type/kstartup-searchin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

instruction.md
skill.json
scripts/
run_kstartup.py
tests/
__init__.py
test_run_kstartup.py

Details

From the project README

kstartup-search

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 kstartup-search

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 kstartup-search

Keep the CLI and every coding-agent skill install current (including Vercel Agent Skills) with:

npx -y @nomadamas/k-skill@0 update

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/kstartup-search/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.

Comments

Markdown supported