This skill is for operating shared docs, spreadsheets, and decks as working systems, not just editing one file in isolation.
When to Use
User needs to find a doc, sheet, or deck and update it in place
Consolidating plans, trackers, notes, or customer lists stored in Google Drive
Cleaning or restructuring a shared spreadsheet
Importing, repairing, or reformatting a Google Slides deck
Producing summaries from Docs, Sheets, or Slides for decision-making
Preferred Tool Surface
Use Google Drive as the entry point, then switch to the right specialist:
Google Docs for text-heavy docs
Google Sheets for tabular work, formulas, and charts
Google Slides for decks, imports, template migration, and cleanup
Do not guess structure from filenames alone. Inspect first.
Workflow
1. Find the asset
Start with the Drive search surface to locate:
the exact file
sibling assets
likely duplicates
recently modified versions
If several documents look similar, confirm by title, owner, modified time, or folder.
2. Inspect before editing
Before making changes:
summarize current structure
identify tabs, headings, or slide count
detect whether the task is local cleanup or structural surgery
Pick the smallest tool that can safely perform the work.
3. Edit with precision
For Docs: use index-aware edits, not vague rewrites
For Sheets: operate on explicit tabs and ranges
For Slides: distinguish content edits from visual cleanup or template migration
If the requested work is visual or layout-sensitive, iterate with inspection and verification instead of one giant blind update.
4. Keep the working system clean
When the file is part of a larger workflow, also surface:
duplicate trackers
outdated decks
stale docs vs canonical docs
whether the asset should be archived, merged, or renamed
Output Format
Use:
ASSET
- file name
- type
- why this is the right file
CURRENT STATE
- structure summary
- key problems or blockers
ACTION
- edits made or recommended
FOLLOW-UPS
- archive / merge / duplicate cleanup / next file to update
Good Use Cases
"Find the active planning doc and condense it"
"Clean up this customer spreadsheet and show me the churn-risk rows"
"Import this deck into Slides and make it presentable"
"Find the current tracker, not the stale duplicate"
docker-patternsaffaan-mDocker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration. Use when setting up containerized development environments or reviewing Docker configurations.4,8004,800 instalaciones en skills.sh0
security-reviewaffaan-mUse this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.4,8004,800 instalaciones en skills.sh0
backend-patternsaffaan-mBackend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access.4,7004,700 instalaciones en skills.sh0
frontend-patternsaffaan-mFrontend development patterns for React, Next.js, state management, performance optimization, and UI best practices. Use when building or reviewing React or Next.js components, state, or render performance.4,7004,700 instalaciones en skills.sh0
coding-standardsaffaan-mBaseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns. Use when reviewing code quality or naming with no framework-specific skill that applies.4,5004,500 instalaciones en skills.sh0
