Layerkit Author Processor
Author or update client-side transform/helper code from vendor docs with mandatory citations.
Install
$ agentstack add skill-hariharapanigrahy-layerkit-layerkit-author-processor ✓ 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 Used
- ✓ 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.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-hariharapanigrahy-layerkit-layerkit-author-processor) 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
layerkit-author-processor
Use this skill when a vendor contract requires normalization, hashing, formatting, date conversion, object shaping, or other deterministic helper logic in the client package.
These helpers are client-owned source code. They are not Layerkit runtime processors.
Protocol
- Identify the transform requirement from vendor docs/OpenAPI/curl and existing client mapper code.
- Search for an existing helper before adding one.
- Prefer updating an existing helper or mapper method.
- Add a new helper only when no existing function can be changed cleanly.
- For any new helper, state what it replaces. If it replaces nothing, justify why it must exist.
- Add or update tests that prove the transform against cited examples.
- Validate any map/proposal artifact only if the client uses one:
layerkit proposal validate ./proposal.json
layerkit map validate ./map.jsonCitation Rules
- Cite the vendor/customer rule for every non-obvious transform.
- Excerpts must cover the rule, such as hashing order, casing, phone format, timestamp unit, or nested object shape.
- If docs are silent, do not invent SHA variants, phone formats, timezone assumptions, or fallback defaults.
Forbidden
- Network, credentials, or AI calls inside transform helpers.
- Double-hashing or re-normalizing without evidence.
- Adding a parallel helper when an existing mapper/helper should be changed.
- Creating Layerkit processor proposal artifacts as a substitute for editing source.
Success Criteria
- [ ] Transform source code lives in the client package path.
- [ ] Existing code was updated or stale code was removed before adding a helper.
- [ ] Tests cover vendor examples or cited schema rules.
- [ ] Any remaining datalayer gap is a precise TODO in source and handoff.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: hariharapanigrahy
- Source: hariharapanigrahy/layerkit
- License: MIT
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.