mcpField
F
fsc-corporate-info

fsc-corporate-info

github.com/nomadamasOther8.2k5.3k installsUpdated 2d ago
Repository

About fsc-corporate-info

fsc-corporate-info is a coding-agent skill whose current, runtime-specific instructions are retrieved through the k-skill CLI. The README documents safeguards for consequential actions and credential handling; it does not describe the skill's corporate-information capabilities.

Key features

  1. 01Fetch runtime-specific instructions with the CLI
  2. 02List bundled helper files
  3. 03Update the CLI and skill installs
  4. 04Require approval for consequential actions
  5. 05Avoid handling plaintext credentials

Use cases

  1. 01Checking applicable skill instructions for the current runtime
  2. 02Reviewing safeguards before using the skill

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nomadamas/k-skill --skill fsc-corporate-info

After installing, type/fsc-corporate-infoin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

instruction.md
skill.json
scripts/
fsc_corporate_info.py
test_fsc_corporate_info.py

Details

From the project README

fsc-corporate-info

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 fsc-corporate-info

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 fsc-corporate-info

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/fsc-corporate-info/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