Docs Pipeline Automation

Build repeatable data-to-Docs pipelines from Sheets and Drive sources. Use for automated status reports, template-based document assembly, and scheduled publ...

Security Scan

The skill is internally consistent: it provides an instruction-only pipeline composer and a small local script that generates pipeline specification artifacts without network access or credential requests.

Purpose & Capability

The name/description promise 'data-to-Docs pipelines from Sheets and Drive' but the bundled script only composes a pipeline specification from a local JSON payload and writes an artifact; it does not integrate with Google Sheets/Drive or require any credentials. This is plausible (a design tool rather than an executor) but users should understand it only produces specs, not automatic Google-side publishing.

Instruction Scope

SKILL.md instructs the agent to run the bundled script and read the included guide. The instructions are scoped to composing pipeline artifacts and do not ask the agent to read unrelated files, environment variables, or call external endpoints.

Install Mechanism

No install spec; the skill is instruction-only with a local Python script. Nothing is downloaded from external URLs and no archives are extracted.

Credentials

The skill requests no environment variables, no credentials, and accesses only a user-supplied input file and a user-specified output path. No secret access is requested or implied.

Persistence & Privilege

always is false, autonomous invocation is allowed (platform default). The skill does not modify other skills or system configuration and only writes to the specified output path when run.

Assessment

This skill appears to be a safe, local 'pipeline spec' composer rather than an executor that connects to Google services. Before installing/running: (1) Understand it only reads a JSON input file you provide and writes an artifact to the output path — it will not automatically read your Google Sheets/Drive or publish documents. (2) Verify the input file and output path you pass are correct and from trusted sources; the script limits input size but will process whatever JSON you give it. (3) If you expect automatic publishing to Google Docs/Drive, additional code and credentials would be required — review or add those integrations separately and only grant third-party credentials when necessary. (4) As with any code, inspect bundled scripts (scripts/compose_docs_pipeline.py) before executing in sensitive environments.

Overview

Create deterministic pipelines that transform Workspace data sources into generated Docs outputs.

Workflow

1. Define pipeline name, sources, template, and destination.
2. Normalize source extraction and section mapping steps.
3. Build report assembly sequence and publish target.
4. Export implementation-ready pipeline artifact.

Use Bundled Resources

• Run scripts/compose_docs_pipeline.py for deterministic pipeline output.
• Read references/docs-pipeline-guide.md for document assembly guidance.

Guardrails

• Keep source mapping explicit and versioned.
• Include fallback behavior for missing sections.