artifact-pack

Package repository artifacts into shareable packets with regenerated document formats.

Updated Jun 17, 2025
One-click install
npx skills add https://github.com/necatiincekara/Quanvolutional-Neural-Network --skill artifact-pack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: artifact-pack
Source: https://github.com/necatiincekara/Quanvolutional-Neural-Network/tree/main/.agents/skills/artifact-pack
Command: npx skills add https://github.com/necatiincekara/Quanvolutional-Neural-Network --skill artifact-pack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Assemble advisor, submission, or sharing packets from current repo artifacts without introducing stale claims.

Core Features & Use Cases

  • Packet assembly: Bundle advisor updates, submission artifacts, benchmark snapshots, and Word exports into coherent, shareable packets.
  • Consistency and provenance: Reconcile current benchmark truth before packaging to preserve thesis continuity.
  • Automation triggers: Regenerate .docx versions for touched docs; optionally trigger paper_sync and paper_consistency_reviewer for multi-document coherence.

Quick Start

Pack the latest repo artifacts into a shareable packet by triggering the artifact-pack workflow.

Frequently Asked Questions about artifact-pack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bundle repository artifacts into shareable packets for advisor updates?

Bundle repository artifacts into shareable packets by triggering the artifact-pack workflow, which consolidates advisor updates, benchmark snapshots, and touched document formats into one cohesive packet for reproducible sharing.

What is the best way to package benchmark snapshots and Word exports without introducing stale claims?

Package benchmark snapshots and Word exports by reconciling current benchmark truth before packaging, regenerating touched .docx versions, and optionally triggering paper_sync and paper_consistency_reviewer for multi-document coherence.

Can I automate regenerating .docx files for submission artifacts across active repositories?

Automate .docx regeneration for submission artifacts by triggering the artifact-pack workflow, which reads preferred docs like paper/draft.md and experiments/*.json, then regenerates touched document formats for packaging.

Does artifact packaging require reading AGENTS.md before consolidating repository outputs?

Artifact packaging requires reading AGENTS.md and preferred docs such as docs/SUBMISSION_BENCHMARK_2026-03-25.md, docs/BENCHMARK_SUMMARY.md, paper/draft.md, and experiments/*.json to satisfy reproducibility requirements before assembling packets.

How to ensure thesis continuity when assembling submission packets from current repo artifacts?

Ensure thesis continuity during submission packet assembly by reconciling current benchmark truth before packaging and optionally invoking paper_consistency_reviewer to validate multi-document coherence across the bundled artifacts.

When should I not use automated artifact packaging for repository outputs?

Avoid automated artifact packaging when preferred docs like docs/BENCHMARK_SUMMARY.md or experiments/*.json are missing, since the workflow depends on reading these files to reconcile benchmark truth and prevent stale claims in the packet.