skills.rest
FrogAi
FrogAiCOMMUNITY
Explore all skills by this author →
GitHub

artifact-factory

Coordinates Gemini CLI artifact creation through intake-driven governance and delegated drafting.

1|Updated Apr 16, 2026
Search Tags:#automation#governance#artifact#gemini-cli#audits#intake#artifact-factory
One-click install
npx skills add https://github.com/FrogAi/Xenopus --skill artifact-factory
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: artifact-factory
Source: https://github.com/FrogAi/Xenopus/tree/main/Gemini/Skills/Gemini%203.1%20Pro/artifact-factory
Command: npx skills add https://github.com/FrogAi/Xenopus --skill artifact-factory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The artifact-factory automates the end-to-end creation of Gemini CLI artifacts by enforcing intake-driven governance and routing authoring to the artifact-engineer, ensuring every artifact meets the R1–R17 constitution and is ready for installation.

Core Features & Use Cases

  • Intake-first orchestration: collects type, name, purpose, domain, triggering cues, priority, and cross-references before any drafting.
  • Dispatches authoring to a dedicated subagent: never hand-authors; the artifact-engineer produces the final detail file with references and self-audit.
  • Governance and lifecycle: live-fetches domain references, enforces cross-reference requirements, and records verifiable steps for audits.

Quick Start

Provide the artifact type, name, and purpose to begin the intake and dispatch workflow.

Frequently Asked Questions about artifact-factory

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

FAQPage Schema
How do I automate Gemini CLI artifact creation with governance checks?▼

Automating Gemini CLI artifact creation requires an intake-driven workflow that collects type, name, and purpose before dispatching drafting to a subagent, enforcing governance and producing install-ready drafts.

What is an intake-driven workflow for producing production-grade artifacts?▼

An intake-driven workflow for production-grade artifacts collects type, name, purpose, domain, and cross-references upfront to enforce R1–R17 governance rules before any drafting begins.

How do I enforce cross-reference requirements when generating Gemini artifacts?▼

Enforcing cross-reference requirements during artifact generation involves live-fetching domain references and validating them against R1–R17 constitution rules to ensure compliance and audit readiness.

Do I need to provide artifact type and purpose to start the automated drafting process?▼

Yes, you must provide the artifact type, name, and purpose to begin the intake workflow, which then validates the inputs and routes the authoring task to a dedicated artifact-engineer subagent.

What is the best way to validate artifact requirements before installing a Gemini CLI skill?▼

Validating artifact requirements before installation requires reading ARTIFACT-REQUIREMENTS.md, confirming type and purpose alignment, and running a verification audit to ensure the draft meets production-grade R1–R17 standards.

Why does my Gemini artifact generation fail to meet production-grade governance standards?▼

Artifact generation fails governance standards when it bypasses the structured intake workflow or skips live-fetching domain references, preventing proper cross-reference enforcement and audit verification.

Related Skills

Explore More Software Engineering Skills→
jtrackingaijtrackingai
134

tracking-group

Group pages by business purpose from site-analysis.json for GA4 and GTM tracking.

Community
Intermediate
arcasilesgrouparcasilesgroup
54

governance

Validate AI project integrity, compliance, ownership, and operational readiness via CLI checks.

Official
Advanced
byonk19-svgbyonk19-svg

ask-gemini

Query Gemini via local CLI and save a structured artifact.

Community
Intermediate
VCnoCVCnoC
7

clink-standalone

Bridge external AI CLIs without MCP server for isolated sessions.

Community
Advanced