Install
$ agentstack add skill-jnmetacode-skillet-repo-onboarding ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
repo-onboarding
Resist editing until you can answer: how do I run it, how do I test it, where does the change go, and what style does this house write in?
Procedure (15 minutes, in order)
- The README + manifest first.
README.md, then the manifest
(package.json / pyproject.toml / go.mod / Cargo.toml): name, scripts, dependencies. The scripts block is the repo telling you its verbs.
- Find the entry points.
bin/mainfields,src/index.*,cmd/,
__main__.py. Trace one request/command end-to-end at skim depth — names only, no line-reading.
- Establish the test loop before touching anything. Run the test command;
record how long it takes and whether it's green at HEAD. A red baseline changes everything you conclude later.
- Map the directories (one line each, only top two levels). Mark the ones
that are generated/vendored so you never read them again.
- Sample the house style. Open the 2–3 most-recently-changed source files
(git log --name-only -10): error handling pattern, naming, comment density, test structure. Your changes should be indistinguishable from these.
- Find the seams. Where does config enter? Where is I/O isolated? What is
the one module everything imports? That module is load-bearing — changes there need the most care.
- Check the repo's own rules:
CONTRIBUTING.md,CLAUDE.md,.github/
workflows (what CI actually enforces), lint configs.
Output
Write a short map (10–20 lines) before starting the actual task:
run: npm start (src/cli.js) test: npm test, ~6s, green at HEAD
flow: cli.js → commands/* → store.js (all persistence) → index.json
style: ESM, no deps, errors thrown as plain Error, tests in test/*.test.js
care: store.js is imported everywhere; schema changes ripple
rules: CI runs lint+test on 3 OS; commits are conventional
Keep it honest — list what you didn't look at, so later-you knows where the map has blank spots.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jnMetaCode
- Source: jnMetaCode/skillet
- License: MIT
- Homepage: https://github.com/jnMetaCode/local-agent-toolkit
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.