mcpField
S
store-longevity-radar

store-longevity-radar

github.com/nomadamasData & databases8.2k4.0k installsUpdated 2d ago
Repository

About store-longevity-radar

A coding-agent skill that loads runtime-specific instructions for store-longevity-radar through the k-skill CLI. It also provides commands for listing helper files and updating the CLI and installed skills, with safeguards for consequential actions and credentials.

Key features

  1. 01Runtime-specific instructions via CLI
  2. 02Bundled helper-file listing
  3. 03CLI and skill update command
  4. 04Approval and credential safeguards

Use cases

  1. 01Loading store-longevity-radar instructions
  2. 02Checking bundled helper files
  3. 03Updating the CLI and installed skills

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nomadamas/k-skill --skill store-longevity-radar

After installing, type/store-longevity-radarin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

instruction.md
skill.json
scripts/
store_longevity_download.py
store_longevity_radar.py
tests/
test_store_longevity_radar.py

Details

From the project README

store-longevity-radar

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 store-longevity-radar

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 store-longevity-radar

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/store-longevity-radar/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