Word, Excel, PowerPoint, PDF, meeting notes, and manuals (3.6K skills)
Analyze a codebase and produce a hierarchical wiki catalogue with file references. Plan onboarding guides for contributors, senior engineers, executives, and product managers, alongside setup material and deeper architecture documentation.
Turn project wiki pages into llms.txt files that summarize the project and organize documentation links for language models. Also generate llms-full.txt with page content included, preserving diagrams, tables, and source citations.
Create technical wiki pages grounded in actual source code. It organizes architecture, components, and data flow into Markdown with source citations, dark-mode Mermaid diagrams, summary tables, and links to related pages for deeper exploration.
Helps build Python workflows to translate Word, PDF, Excel, PowerPoint, and other documents while preserving formatting. Covers batch translation into multiple languages, glossary use, progress tracking, and checks for individual document failures.
Rebuild slide images, PDF decks, and image-based PowerPoint files as editable .pptx presentations. Reconstruct text and visual elements as separate objects, preserve supplied speaker notes, and validate the assembled deck before delivery.
Create reusable templates for documenting design system components, patterns, and foundational guidelines. Standardize headings and content fields, including usage, examples, behavior, accessibility, and status, so teams have a consistent structure for writing and maintaining documentation.
Integrate source documents into a wiki by extracting key facts, people, organizations, and concepts. Create or update pages, connect related entries, record sources, and maintain indexes and an activity log.
Check a wiki for conflicting claims, outdated information, unlinked pages, and missing references. Produce a structured report with suggested corrections, links to add, and questions or sources worth investigating next.
Fill existing LaTeX projects with sample sections, tables, and explanatory text based on chapter topics and available figures, code, and references. Preview or apply the content while checking formatting and protecting the template structure.
Move text and references from older LaTeX projects, Word documents, PDFs, or mixed materials into an existing ChineseResearchLaTeX template. The skill preserves template structure and styles, reports gaps, and checks the build when possible.
Capture reusable writing decisions from a conversation in an existing project guide. The skill turns insights into a few focused rules, places them in appropriate sections, and preserves established headings, terminology, numbering, and order.
Refine application, paper, thesis, and CV templates in ChineseResearchLaTeX. Compare layouts with reference PDFs, adjust headings and styles at the appropriate project or shared package level, and validate changes through the designated build tools.
Turn a pro-workflow wiki into one self-contained HTML file with pages, sources, claims, queued research topics, search, and a page-link graph. Browse the results locally or share a snapshot through static hosting.
Export Apple Notes into Markdown, JSON, HTML, or SQLite for backups and searchable archives. The workflow covers folder organized Markdown files, conversion from note HTML, record checks, and handling exported data carefully.
Map and review an Abridge clinical documentation workflow from consent and recording through draft review, evidence checks, edits, and final disposition. Keep clinician approval explicit, identify failure exits, and separate verified facts from tenant-specific details and pending approvals.
Run an approved Adobe PDF Services job for document conversion, extraction, or generation. Track asset custody and asynchronous status, verify the returned file, and record cleanup and retention evidence for the operation.
Audit how clinician-reviewed Abridge note sections map into Epic templates and downstream workflows. Use approved test records to document destinations, exceptions, evidence, rollback steps, and a go or no-go decision for a specific environment.
Update website documentation, the built-in skill description, and README to match code changes. It cross-checks documented CLI flags against Go source, revises relevant guides and examples, and builds the website to check for broken links or errors.
After Python API changes, identify the changed files and compare old and new signatures. Find stale references across documentation, examples, and docstrings, then update them and report whether any public API changes need documentation work.
Use the officecli command-line tool to create, inspect, proofread, and edit Word, Excel, and PowerPoint files. Review document structure and issues, change content or formatting, add elements such as charts, and validate files before delivery.
Use this skill to write or review technical documentation, RFCs, READMEs, pull request descriptions, and commit messages. It helps choose a document structure for the reader’s goal and apply clear, concise sentence rules with consistent terminology.
Draft working-group specifications, research findings, and glossaries as clear, fact-based descriptions of a domain. Keep documents focused on why and what, so they remain useful across programming languages and implementations.
Route documentation work to the right family before drafting: SDK and developer references, user-facing product guides, or working-group design documents. Clarify the intended audience, purpose, and home, then hand off to the relevant specialized guidance.
Create and update user guides for the Grida Canvas editor, with guidance on clear writing, page structure, screenshots, and demo setup. Use it to explain editor features to users and keep documentation visuals aligned with the product interface.