Install
$ agentstack add skill-xcaeser-work-skill-work-init ✓ 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
Work / 1. Init
Create the smallest project foundation that builds and runs. Preserve reliability, user state, simplicity, and clean breaks. Do not add product features, speculative packages, compatibility scaffolding, or infrastructure the foundation does not yet need.
Resolve only essential choices
Inspect the destination and conversation before asking anything. Reuse answers already given. If the request is sufficient, proceed without an interview.
Ask no more than three short questions at a time, in this order:
- What is being built, where should it live, and which platform must it run on?
- Which language, runtime or toolchain, and minimum supported version are required?
- Which packages, services, storage, authentication, and quality commands are genuinely required now?
Offer sensible defaults when local conventions or the ecosystem make them clear. Explain only choices with a meaningful tradeoff.
Before writing, state:
- Foundation goal: one end-to-end capability the scaffold must prove.
- Ready when: build, run, and relevant quality checks succeed.
- Does not count: an empty or unexecuted scaffold.
- Deferred: product features and infrastructure intentionally excluded.
Build in working layers
- Read local instructions and inspect the destination for unrelated files.
- Create an idiomatic scaffold with native metadata and one obvious entry point.
- Add only approved dependencies; prefer platform and existing workspace tooling.
- Format or lint, run focused tests when behavior exists, and perform a clean build.
- Start the project locally when safe and useful.
- Exercise one relevant failure boundary, such as invalid configuration or a missing required dependency.
- Inspect generated files and lockfiles. Report exact commands and evidence.
Do not invent tests for an empty entry point. When the scaffold establishes real behavior, state the behavior being protected, why it matters, the test level, and the exact observable assertion before test edits.
Do not spawn agents for the setup interview. If the work expands into product implementation, stop at the verified foundation and hand the scoped task to $work.
Return
## Work / 1. Init
**Goal:**
**Created:**
**Run:**
**Validation:**
**Failure boundary checked:**
**Deferred:**
**State:** complete / partial / blocked
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: xcaeser
- Source: xcaeser/work-skill
- License: MIT
- Homepage: https://skills.sh/xcaeser/work-skill
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.