Run any Skill in Manus with one click

savitar-provenance

Stars0

Forks0

UpdatedApril 6, 2026 at 22:00

Create or update a Savitar provenance log entry for clean-room work. Use when a feature depends on external documentation, parity targets, third-party products, or public APIs and the repo needs an auditable record of what was consulted.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

AlexiosBluffMara

AlexiosBluffMara/Savitar

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	savitar-provenance
description	Create or update a Savitar provenance log entry for clean-room work. Use when a feature depends on external documentation, parity targets, third-party products, or public APIs and the repo needs an auditable record of what was consulted.
argument-hint	Describe the feature or workstream that needs a provenance entry

Savitar Provenance Workflow

When to Use

Starting a feature inspired by another system.
Studying public API or setup documentation before implementation.
Recording the source material behind an integration or deployment change.

Procedure

Copy the template in ./assets/entry-template.md into a new file under docs/provenance/.
Record the public sources, product docs, or requirements that informed the work.
State clearly what was not copied and which implementation details were authored from scratch.
Link the provenance entry from the relevant ADR, roadmap item, or pull request.
Update the entry if the scope changes or new external references are consulted.

More from this repository

same repository

savitar-architecture

AlexiosBluffMara/Savitar

Plan or revise Savitar architecture, ADRs, contracts, system boundaries, phase sequencing, or multi-surface integration. Use when scoping features, defining interfaces, or breaking work into clean-room milestones.

2026-04-060

savitar-integration

AlexiosBluffMara/Savitar

Add or change a Savitar model route, MCP server, transport, browser automation feature, or memory workflow. Use when implementing new integrations, extending contracts, or wiring new capabilities into the runtime.

2026-04-060

savitar-persona

AlexiosBluffMara/Savitar

Design or refine the Savitar persona. Use when defining speech patterns, public bio, reply style, identity consistency, or human-conversational behavior across CLI, messaging, and web surfaces.

2026-04-060

savitar-security

AlexiosBluffMara/Savitar

Review Savitar for security risks. Use when working on public web UI, Google auth, messaging transports, remote execution, MCP/tool safety, secret handling, or prompt-injection-resistant workflows.

2026-04-060

savitar-testing

AlexiosBluffMara/Savitar

Test or validate Savitar runtime changes. Use when adding unit tests, doctor checks, CI coverage, regression validation, or release-readiness checks.

2026-04-060

savitar-transport-design

AlexiosBluffMara/Savitar

Design or extend Savitar messaging transports and the shared gateway. Use when working on Discord, WhatsApp, iMessage, message normalization, delivery flows, or channel identity policy.

2026-04-060

name	savitar-provenance
description	Create or update a Savitar provenance log entry for clean-room work. Use when a feature depends on external documentation, parity targets, third-party products, or public APIs and the repo needs an auditable record of what was consulted.
argument-hint	Describe the feature or workstream that needs a provenance entry

Savitar Provenance Workflow

When to Use

Starting a feature inspired by another system.
Studying public API or setup documentation before implementation.
Recording the source material behind an integration or deployment change.

Procedure

Copy the template in ./assets/entry-template.md into a new file under docs/provenance/.
Record the public sources, product docs, or requirements that informed the work.
State clearly what was not copied and which implementation details were authored from scratch.
Link the provenance entry from the relevant ADR, roadmap item, or pull request.
Update the entry if the scope changes or new external references are consulted.