About housing-subscription-reference
A coding-agent skill for housing-subscription tasks. It requires loading current, runtime-specific instructions first and sets boundaries around sensitive actions and credentials.
Key features
- 01Runtime-specific instructions via CLI
- 02Lists bundled helper files
- 03Explicit approval for consequential actions
- 04Protects credentials and verification boundaries
Use cases
- 01Preparing an agent for housing-subscription work
- 02Checking available skill helper files
- 03Preventing unapproved submissions or cancellations
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ nomadamas/ k-skill --skill housing-subscription-referenceAfter installing, type/housing-subscription-referencein Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
instruction.mdskill.jsonreferences/housing_subscription_score.csvprivate_housing_deposit.csvregion-and-area-rules.mdDetails
From the project READMEhousing-subscription-reference
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 housing-subscription-reference
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 housing-subscription-reference
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/housing-subscription-reference/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.