Generates a repo-local audit trail with plan, todo, and walkthrough files.
npx skills add https://github.com/hyophyop/artifacts-skill --skill artifacts
Please help me install this Agent Skill. Skill: artifacts Source: https://github.com/hyophyop/artifacts-skill/tree/main/artifacts Command: npx skills add https://github.com/hyophyop/artifacts-skill --skill artifacts
This Skill enables teams to create a durable, repo-local audit trail for task work by automatically generating a dedicated workspace under .artifacts/artifacts/{request_id} with plan.md, todo.md, and walkthrough.md, and indexing the completed work into a local ChromaDB store at .artifacts/chroma_db/ for 7-day recall.
Run the artifacts init command to create a new artifacts workspace in your target repository.
High-intent search queries and answers about installing and using this skill.
To create a repo-local audit trail for task work, this Skill generates a dedicated workspace under .artifacts/artifacts/{request_id} containing plan.md, todo.md, and walkthrough.md files, then indexes the results into a local ChromaDB store for 7-day recall.
Indexing completed task work into ChromaDB enables Q&A by storing detailed walkthroughs in a local vector database at .artifacts/chroma_db/, allowing you to query the artifacts index and retrieve past task results for up to 7 days.
A confirm-before-execute workflow for repo-local task tracking generates plan and todo files first, then waits for your explicit confirmation before implementing any changes, ensuring you review the proposed work before it is applied.
The retention period for artifacts indexed in a local ChromaDB store is 7 days, managed by TTL-based pruning that automatically removes expired data to maintain repository-local data governance under the .artifacts/ directory.
Yes, the artifacts workspace supports bootstrapping a Python environment automatically under .artifacts/, satisfying repository-local lifecycle requirements by initializing the necessary dependencies for ChromaDB indexing and TTL-based pruning.
Limitations of repo-local artifacts include a strict 7-day TTL-based pruning window for ChromaDB recall, and all byproducts being confined to the .artifacts/ directory, meaning indexed data is not shared across different repositories.
nedaktov-opsInitialize a MemPalace workspace with a ChromaDB backend and project scaffold.
Arry8Ingest documents into a local ChromaDB vector store and query semantically.
doolinCreate Markdown project management templates under a .development directory.
RheasilviaManage vector embeddings and perform semantic similarity searches in chromadb databases.
