2.5천건 · 관련도순
Draft content in Google Docs, organize and upload assets in Drive, announce finished work in Chat, and request reviews through Gmail. It supports content creation and sharing across Google Workspace.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Compare repository documentation with current code, tests, and settings to find missing, incorrect, or outdated guidance. Update affected pages, prioritize problems that block readers, and check examples and navigation for consistency.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
VitePress documentation workflow for Software Metrics Machine docs under docs/vitepress. Use when creating, updating, reviewing, or restyling SMM documentation pages, especially feature docs that must keep CLI terminal examples and dashboard views/screenshots in sync. Covers Markdown style, VitePress tabs, command examples, dashboard screenshots, sidebar links, and docs validation. USE FOR: docs/vitepress, VitePress docs, documentation style, CLI docs, dashboard docs, screenshots, feature pages. DO NOT USE FOR: application code changes unless needed to verify documented behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scan recent git commits for changes that affect user-facing behavior, then draft or update the corresponding documentation pages. Use when docs have fallen behind code changes, after a batch of features lands, or when preparing a release. Trigger keywords - update docs, draft docs, docs from commits, sync docs, catch up docs, doc debt, docs behind, docs drift.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create and edit Google Docs, Sheets, and Slides in Google Drive. Keep existing file links while updating text, formatting cells, adding tabs or charts, and checking the results through the appropriate Google connectors.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Append plain text to the end of an existing Google Docs document using its document ID. Use it to add notes, follow-up information, or extra paragraphs through the gws command-line tool.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Fill documentation gaps identified by a CARLA documentation audit, following the project's writing style. Work through one category at a time, assess which findings deserve entries, update source files, and report changes and skipped findings.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review generated or changed documentation before it ships — READMEs, API references, docstrings, PHPDoc/JSDoc, changelogs, tutorials, and doc sites. Best used reactively after an agent writes or edits docs, after code changes documented behavior, or before publishing docs. Use when the user says 'review the docs', 'is this documentation accurate', 'update the docs', 'write a README', 'document this API', 'add a docstring', or 'add a changelog entry'. Core job: verify every referenced function, flag, endpoint, config key, and code sample against the source; catch docs-vs-code drift; strip filler and unverifiable claims. DO NOT USE for production code review (use clean-code-guard), test review (use test-guard), marketing copy or blog posts, prose style editing of non-technical writing, or documentation site theming.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Updates tdmcp docs and roadmap for newly shipped or newly merged capabilities. Use when asked to update docs, update the roadmap, reconcile release docs, document new features, sync docs with CHANGELOG/package release, refresh cookbook examples after a feature wave, re-run/continue/fix a docs-roadmap pass, or check whether docs/ROADMAP.md is current. Runs a sub-agent workflow: release audit -> roadmap/docs edit + cookbook sync -> QA.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scaffold, validate, and maintain Johnny.Decimal documentation structure for software projects. Use when user mentions "Johnny Decimal", "J.D docs", "docs structure", "organize docs", "documentation layout", "scaffold docs", "docs migration", "generate index", "docs index", "add area", "classify docs", "move doc", editing files in numbered directories (00-*, 10-*, 20-*), or discussing documentation organization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit and maintain the learnings in `docs/solutions/` against the current codebase — fix drifted paths and links, merge overlapping docs, replace guidance the code no longer supports, delete obsolete docs, reconcile the `CONCEPTS.md` glossary, then report and commit. Also bootstraps `CONCEPTS.md` on request and, when asked, culls docs whose reasoning the code already explains. Use for "refresh the learnings", "audit docs/solutions", "are our solution docs still accurate", "clean up / prune the learnings", "create a CONCEPTS.md", or after a refactor, rename, migration, or dependency upgrade that likely invalidated documented solutions. Not for capturing a new learning — use `learn-with-docs`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Updates tdmcp docs and roadmap for newly shipped or newly merged capabilities. Use when asked to update docs, update the roadmap, reconcile release docs, document new features, sync docs with CHANGELOG/package release, refresh cookbook examples after a feature wave, re-run/continue/fix a docs-roadmap pass, or check whether docs/ROADMAP.md is current. Runs a sub-agent workflow: release audit -> roadmap/docs edit + cookbook sync -> QA.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Launch the Remotion documentation site locally and open it in the Codex in-app browser. The workflow installs dependencies, builds the project, starts Docusaurus, and reports the actual preview URL and server status.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Set up a new Remotion Element for development in the documentation’s Remotion Studio. It follows the design and contribution guides, creates the starting structure, and offers to launch Docs Studio for a preview.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Compare documentation with actual code, configuration, and commands to find outdated instructions or missing information. Produce a read-only audit with evidence, severity levels, and specific guidance on which documents need updating.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Read data from Google Sheets and turn it into a Google Docs report. The workflow covers creating the document, writing report sections, and granting a stakeholder permission to read the finished file.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Find a Google Docs document by name, give a collaborator editing access, and email them its link. This skill connects document sharing and notification in one workflow so the recipient can open the shared document.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare an incident review by creating a Google Docs report template, scheduling a review meeting in Google Calendar, and notifying the team through Chat. The template covers the summary, timeline, root cause, and action items.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Organize research papers and notes in Drive, write summaries in Docs, and log data in Sheets. Share findings with collaborators and send peer review requests through Gmail to support research teamwork.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide AI agents through Zoom MCP, a tool connection for searching meeting content and retrieving recordings, related assets, and transcript resources. Covers tool selection, authentication requirements, troubleshooting, and routing Docs or Whiteboard requests to separate services.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Compare SDK implementation with English documentation to find missing features, incorrect defaults, and outdated behavior descriptions. Report evidence and suggested locations, or make requested updates while keeping navigation consistent and following the repository’s documentation checks.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Find and read files across Google Drive, including shared drives, and export useful formats. With approval, edit Docs, Sheets, and Slides, upload generated files, or reorganize existing content using the connected Google account.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use this skill to run a holistic regrounding pass on the entire microsoft/apm documentation corpus against current source code, page-by-page, and emit surgical fixes for stale claims. Activate when the maintainer wants a WHOLE-CORPUS audit (not per-PR review) -- typical triggers include "audit the docs", "reground the corpus", "check every page against code", "pre-release docs sweep", "the docs have drifted everywhere", or "we just reshaped the TOC, find dead links". Wave-batched and S7-verified; scales to the full ~112-page corpus in ~10 minutes wall-time. This is a SIBLING to docs-sync, not a replacement: docs-sync is per-PR (triggered by a diff); this skill is per-corpus (triggered by a maintainer ask). They share agent personas, schemas, and the docs index, but their triggers MUST NOT collide. Does NOT auto-merge, does NOT push without maintainer review, and does NOT replace per-PR drift detection.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Update website docs to match recent code changes, cross-validating every flag against source. Use this skill whenever the user asks to: update documentation, sync docs with code, document a new flag or command, fix stale docs, or update the README. This skill covers all website/docs/ categories (commands, reference, understand, how-to, troubleshooting, getting-started) plus the built-in skill description and README. If you just implemented a feature and need to update docs, this is the skill to use. Never manually edit website docs without cross-validating flags against Go source first.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.