report-to-google-doc Skill
Narrow conversion skill. Invoke only when the user explicitly asks to convert an existing local or blob-hosted HTML analytics report into a Google Doc, DOCX, or shareable document. Published by openai in role-specific-plugins.
Decision snapshot
Is this a fit?
Documentation, Data analysis, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is report-to-google-doc Skill?
Narrow conversion skill. Invoke only when the user explicitly asks to convert an existing local or blob-hosted HTML analytics report into a Google Doc, DOCX, or shareable document. Published by openai in role-specific-plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Data analysis
- Documentation use cases
- Data analysis use cases
Declared skill metadata
- Source file: plugins/data-analytics/skills/build-report/report-to-google-doc/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use report-to-google-doc Skill
- Use it for documentation.
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/role-specific-plugins
- Skill file: plugins/data-analytics/skills/build-report/report-to-google-doc/SKILL.md
What it does
Narrow conversion skill. Invoke only when the user explicitly asks to convert an existing local or blob-hosted HTML analytics report into a Google Doc, DOCX, or shareable document.
Skill instructions
Report To Google Doc Use this skill only when the user explicitly needs a shareable Google Drive document from an existing HTML analytics report. The source must be an HTML report: a local file, a downloaded blob-hosted report, or a report produced by $build-report HTML mode. This skill does not convert a live MCP app report directly. The expected path is HTML - DOCX - Drive upload. It is acceptable for Drive to host the upload as a DOCX-backed viewer file rather than a native Google Docs MIME type. Do not use the old Google Docs batch-update request path. Workflow 1. Resolve the HTML report. Use an absolute local path. If the user provides a remote report, retrieve it first and pass the local HTML file to the helper. If the file is a sign-in page, redirect page, or tiny stub, stop and obtain the real report. 2. Run the bundled helper. bash python3 <REPORTTOGOOGLEDOCSKILLDIR/scripts/reporttogoogledocplan.py \ /absolute/path/to/report.html \ --out-dir /tmp/reporttogoogledocplan Omit --r
Verified compatibility and discovery
Frequently asked questions
What is report-to-google-doc?
report-to-google-doc is a open-source AI agent skill with Copy skill directory. Narrow conversion skill. Invoke only when the user explicitly asks to convert an existing local or blob-hosted HTML analytics report into a Google Doc, DOCX, or shareable document.
Who is report-to-google-doc best for?
report-to-google-doc is best for reusing agent instructions, scripts, and references, documentation workflows, data analysis workflows.
How do I install report-to-google-doc?
Install or run report-to-google-doc using Copy skill directory. Check report-to-google-doc for the latest setup command.
Is report-to-google-doc actively maintained?
report-to-google-doc may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
