excrtx-produce-artifacts

Create, export, and publish final artifacts to Google Drive with manifests and receipts.

1|Updated May 26, 2026
One-click install
npx skills add https://github.com/elderbernardi/exocortex.saas --skill excrtx-produce-artifacts-elderbernardi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: excrtx-produce-artifacts
Source: https://github.com/elderbernardi/exocortex.saas/tree/main/skills/excrtx-produce-artifacts
Command: npx skills add https://github.com/elderbernardi/exocortex.saas --skill excrtx-produce-artifacts-elderbernardi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires google-api-python-client, google-auth-oauthlib, google-auth-httplib2, and includes references (resource) components.

What problem does it solve? Final deliverables like reports, PDFs, HTML dashboards, and slide decks often end up scattered without traceable sources, hashes, or proof of publication. This Skill organizes every deliverable into a reproducible artifact package in the Acervo and publishes verified exports to the user's private Google Drive. ## Core Features & Use Cases - Structured Artifact Packages: Creates self-contained packages under _artifacts/items/{artifact_id}/ with source, assets, exports, evaluations, manifest, and receipts. - Deterministic Drive Publishing: Resolves Drive destinations by explicit precedence (user instruction, manifest target, then exocortex/inbox), creates folders, uploads exports, and writes receipts with file IDs, links, SHA-256, and sizes. - Quality and Governance Gates: Applies anti-slop and visual taste gates before marking artifacts ready, and enforces Draft-First approval for any public link, sharing, or email sending. - Use Case: After finishing an audit report for a client, ask the agent to organize it as a ready-to-publish artifact; it preserves the Markdown source, exports PDF/HTML, records hashes in the manifest, uploads to Drive, and hands you the link with a local receipt. ## Quick Start Organize my finalized audit report for the client into a publishable artifact package and upload the PDF to my private Drive.

Frequently Asked Questions about excrtx-produce-artifacts

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

FAQPage Schema
How do I publish a Markdown report to Google Drive?

Preserve the Markdown source in the artifact package, generate final exports like PDF or HTML, then publish to a resolved Drive folder. The flow writes a manifest with hashes and a receipt with the Drive file ID and web link.

What is the difference between GitHub and Drive for artifact delivery?

Use GitHub for versionable code, branches, and technical releases. Use Google Drive for human-consumption artifacts like PDFs, reports, spreadsheets, presentations, images, and final ZIP packages.

How is the Google Drive destination folder decided?

Destination follows strict precedence: an explicit path from the user, then an existing drive_target.folder_path in the manifest, then the fallback exocortex/inbox. The Drive path is never inferred from the local filesystem path.

Why does Drive upload fail with a 403 error despite valid OAuth?

A valid OAuth token does not guarantee the Google Drive API is enabled in the Cloud project. Enable the Drive API, wait for propagation, and republish; record the failure in a failed receipt for audit.

Can the agent share a public link or email the artifact automatically?

No. Private upload to the user's own Drive is allowed as personal delivery, but public links, third-party sharing, and email sending require explicit Draft-First approval before execution.

When should artifacts not use this publishing workflow?

Avoid it for raw inbox intake, semantic knowledge pages without a deliverable, and versionable code whose primary destination is GitHub. Those follow intake, memory, or code workflows instead.