Papyrus init
Atomic — create a Papyrus workspace at a given pathFrom its SKILL.md
npx -y skills add bburda/papyrus --skill papyrus-initAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, as published. Nobody here has run it
papyrus-init
Initialize one Papyrus workspace at a filesystem path. Idempotent.
Atomicity
- (a) Indivisible: single operation (create dir + conf.py + memory/*.rst skeletons)
- (b) Input:
path: Path. Output: workspace directory exists with expected files - (c) Objective reward:
(path / "conf.py").is_file() and (path / "memory" / "facts.rst").is_file() - (d) Reusable: invoked per workspace in a chain (
silos= 1×,program= 2×,enterprise= 3×) - (e) No interference: operates on a single path; multi-workspace setup is composition
Input / Output
input: path (filesystem path, absolute or relative)
output: side effect — workspace scaffold at path
stdout: "Initialized Papyrus workspace at <path>"
exit: 0
Success criterion
After invocation:
test -f <path>/conf.py && test -f <path>/memory/facts.rst
Exit code 0 = success.
Workflow
papyrus init .papyrus
For multi-workspace (composition):
papyrus init .papyrus
papyrus init ../program-papyrus
# Then write papyrus.toml to declare the chain.
Composition examples
- Setup silos project:
papyrus-init× 1 - Setup program project:
papyrus-init× 2 (local + program) - Setup enterprise:
papyrus-init× 3 (local + program + org)
See also
shared/scopes-and-promote.md— presets that dictate how many times to invokepapyrus-write— first write after init