Menü
Reads internal documents and creates a summary.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | summarize_google_docs |
| description | Reads internal documents and creates a summary. |
Use the provided python script to read recent google docs from the last 7 days and summarize the output. the required credentials are stored as an environment variable.
Don't mention upcoming milestones or DRI's.
Make note of important themes across the documents. if there are potential conflicts, also make note of that.
reports/google_doc_summaries/google_doc_summary_YYYY-MM-DD.md, then create a PR.
Here are instructions for using the google docs python scripts:A Python service that connects to the Google Docs API and retrieves documents modified in the last week.
Install dependencies:
pip install -r requirements.txt
Run the service:
python google_docs_service.py
The credential to run the service can be found in the environment variable GOOGLE_OAUTH_TOKEN
from google_docs_service import GoogleDocsService
# Initialize service
service = GoogleDocsService()
# Get documents from last 7 days
recent_docs = service.get_recent_documents(days=7)
for doc in recent_docs:
print(f"Document: {doc['name']}")
print(f"Link: {doc['webViewLink']}")
# Get full document content
document_content = service.get_document_content(document_id)
# Extract plain text
text = service.extract_text_from_document(document_content)
print(text)
# Get documents from last 30 days
recent_docs = service.get_recent_documents(days=30)
google_docs_service.py - Main service implementationrequirements.txt - Python dependenciesThe service requests the following scopes:
drive.readonly - Read-only access to Drive filesdocuments.readonly - Read-only access to Google Docsanalyzes customer feedback across Email, GitHub, NPS, and churn cancellations.
Analyzes git history from a repository to summarize recent development activity, features in progress, and engineering priorities. Use when asked about what the team is working on, recent code changes, development velocity, or to prepare for planning/roadmap discussions.
Projects a customer's cost from prior usage data across seat-based, usage-based, and hybrid SaaS pricing models. Use when asked to "project cost", "estimate BYO cost", "estimate spend", "how much will this cost", "size a deal", or to build an enterprise-style usage/cost projection.
Does research on competitive features and creates a report.
Reads the most recent weekly product briefing, identifies P0 issues, researches them in the codebase, and spawns cloud coding agents to fix each one. Use when asked to "fix P0s", "address critical issues", or "work on top priorities from the briefing."
Posts messages to Slack via webhook.