About company-analysis
A skill for company analysis; its README directs users to retrieve the current, runtime-specific instructions through the k-skill CLI. It also sets boundaries for approvals, credentials, and actions that must not bypass legal or identity checks.
Key features
- 01Runtime-specific instructions via CLI
- 02Bundled helper-file listing
- 03Explicit approval required for consequential actions
- 04Credential and verification safeguards
Use cases
- 01Load applicable company-analysis instructions
- 02Inspect helper files provided with the skill
- 03Avoid unapproved submissions or credential exposure
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ nomadamas/ k-skill --skill company-analysisAfter installing, type/company-analysisin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
instruction.mdskill.jsonreferences/source-contract.mdscripts/dart-rows.jsdart-rows.tsevidence.jsevidence.tsfetch-public.jsfetch-public.tstests/evidence.test.jsevidence.test.tslive-multi.test.tsrun_tests.pyDetails
From the project READMEcompany-analysis
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 company-analysis
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 company-analysis
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/company-analysis/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.