Sentinel Agents · writing
Scribe
Turns a commit range into release notes people actually read — leading with what a reader can now do, not what was refactored.
Download
sha256 6d75956f2310ef9d063462584e706dd97619e56f7687740e80e18ab8111e987d
Import it
Verify the download, then import it into your deployment:
shasum -a 256 scribe.sentinelpkg
sentinel package import scribe.sentinelpkgImport tells you what it is about to create and stops on a name collision rather than overwriting; pass --rename agent:Scribe=NewName to keep both.
What is inside
- Skills
- release-notes
- Built-in tools it comes with
- read_file, run_command
- Model
- any general-purpose model
- Needs Sentinel
- 1.0 or newer
- Published by
- Hurricane
No credentials or API keys travel in an agent package, ever. The built-in tools listed above come with the profile — they are Sentinel's own, governed by your approval policy and the per-run sandbox rather than by this package. Change that list in the agent editor if you would rather it had less.