Docs & Writing

joogy06 Skill

Use when reading, writing, transforming, or converting Word documents from Python — .docx (python-docx, docx2txt, mammoth, pypandoc), .docm (macro-enabled — handled with explicit user intent), .doc legacy (LibreOffice headless or antiword), or generating PDF (docx2pdf on Windows/macOS, LibreOffice headless on Linux, pypandoc + xelatex/wkhtmltopdf). Covers OOXML XXE defence, full-fidelity caveats (python-docx is NOT a 100% renderer), and macro handling. Part of the ms-office-python-* skill family.

joogy06 Skill

Use when a presentation needs architecture diagrams, flowcharts, sequence diagrams, or system visuals — tagged [DIAGRAM] slides from narrative, "add a visual of how X connects to Y", or any system overview visualization for slides. Part of the presentation-* skill family.

joogy06 Skill

Use when project-documentation preferences indicate Confluence export is needed, or when creating Confluence-formatted documentation pages. Covers XHTML storage format, macros (TOC, children, search, panels, code blocks, status badges), REST API page creation, and keeping repo markdown in sync with Confluence.

joogy06 Skill

Use when building standing inside a current employer rather than in the external market — setting goals that survive the review, capturing evidence through the year instead of reconstructing it in December, writing the mid-year and year-end self-assessment, maintaining an internal talent or skills profile in systems like Eightfold that now decide which opportunities surface to you, using Confluence documentation and internal blog or news posts as deliberate visibility, assembling a promotion packet from evidence already recorded, choosing 360 reviewers for rubric coverage and writing feedback about others, and surfacing real scope when the HR record has said the same title for years.

joogy06 Bundle

Use when creating or generating Confluence pages and content — XHTML storage format syntax, macros (TOC, code blocks, panels, status badges, expand, children, info/warning/note, jira issues, drawio), page templates, structured documentation patterns (ADRs, runbooks, project docs), markdown to Confluence conversion, bulk page generation, and content migration strategies.

planifest Bundle

Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes. (gstack) Voice triggers (speech-to-text aliases): "bug report", "just check for bugs".

planifest Bundle

Visual evidence capture workflow for reproducible screenshots in engineering and QA tasks. Use when bug reports, regression checks, or implementation proof require stable screenshot artifacts; do not use for design-source extraction or architecture documentation.

planifest Bundle

Analyse and prioritise product feedback by consolidating similar themes, scoring usefulness, and presenting a ranked Markdown table — use when processing user research, app reviews, or support ticket data.

planifest Bundle

Summarise git changes from the last 7 days into a clean, excited project update — covering key feature changes and upgrades as concise 10-word bullets with a 20-word intro.

planifest Skill

Fresh-context REJECT-default critique of P1 spec and P2 ADR artifacts before the human sees them. Spawned by the orchestrator as a subagent; report-only until promoted.

rweisssieker-xp Skill

Use when Power BI tests should be mined from historical edge cases, anomalies, complaints, postings, CAPAs, returns, failures, tickets, or business exceptions.

rweisssieker-xp Skill

Use when Power BI initiatives must prove business value, expert-hour reduction, report consolidation impact, action completion, cost savings, decision latency, or realized ROI.

rweisssieker-xp Skill

Use when source changes should automatically alert impacts on Power Query, semantic models, DAX, report visuals, data contracts, tests, and documentation.

rweisssieker-xp Skill

Use when Power BI artifacts need German-English or multilingual KPI names, report titles, glossary terms, descriptions, acceptance documents, training material, or global enterprise rollout support.

rweisssieker-xp Skill

Use when measuring how much Power BI expert, designer, data analyst, DAX, M, modeling, QA, governance, and documentation work was replaced by AI/KI skills.

rweisssieker-xp Skill

Use when Power BI documentation should be regenerated from current models, measures, sources, RLS, lineage, report pages, quality gates, and release changes.

rweisssieker-xp Skill

Use when Power BI cockpits need AI-assisted role-based variants for CFO, COO, plant, sales, quality, supply chain, procurement, service, HR, IT, or executive users.

rweisssieker-xp Skill

Use when Power BI usage telemetry, report views, page views, load times, audience behavior, dead reports, unused pages, or adoption should drive report optimization and portfolio cleanup.

rweisssieker-xp Skill

Use when consolidating duplicate Power BI reports, finding retirement candidates, identifying target semantic models, and planning migration away from report sprawl.

knuckles-team Skill

Create professional Marp presentation slides using Markdown. Use when the user requests slide creation, presentations, pitch decks, lecture materials, or Marp documents. Triggers include "create slides", "make a presentation", "Marp document", or requests to "make it look good" for slides. Do NOT use for web- based interactive presentations — use web-artifacts instead.

richfrem Skill

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

richfrem Bundle

Coding conventions and documentation standards across Python, TypeScript/JavaScript, and C#/.NET codebases. Use when: (1) writing new code files or functions, (2) reviewing code for style and documentation compliance, (3) adding file headers or docstrings, (4) creating new tools that need inventory registration, (5) refactoring code that exceeds complexity thresholds, (6) setting up module structure. Covers file headers, function documentation, naming conventions, and tool inventory integration.

richfrem Bundle

Converts Markdown files to one MS Word document per file using plugin-local scripts. V2 includes L5 Delegated Constraint Verification for strict binary artifact linting.

kienbui1995 Skill

Use when designing quality assurance processes — defining quality standards, integrating QA checkpoints into SDLC, creating process documentation, onboarding teams to quality practices, and building a quality-first engineering culture.

kienbui1995 Skill

Use when writing documentation, READMEs, API docs, changelogs, ADRs, or user guides — ensures clarity, structure, and project consistency

kienbui1995 Skill

Use when writing API documentation, creating developer tutorials, building devrel content, or engaging the developer community

kienbui1995 Skill

Use when writing or improving CLAUDE.md files — project context that Claude Code reads every session, global vs project rules, what to include for maximum AI effectiveness, and memory-aware documentation patterns.

williamcorrea23 Skill

Creates an L2 slice in the abap_wiki knowledge base: a business process on which to build functional documentation. Writes the manifest (curated anchors + mandatory real owner) and derives the membership from the dependency graph (BFS hop<=2). Use this skill to start the L2 process on a custom domain. Does not promote anything to L2: it only prepares the slice for research-l2.

williamcorrea23 Skill

SAP API documentation standards — OData API documentation guidelines, REST API style guide, OpenAPI/Swagger specs for SAP services, API naming conventions, SAP API Business Hub documentation requirements. Use when documenting SAP APIs, creating OpenAPI specs for SAP services, or reviewing API documentation against SAP standards.

williamcorrea23 Skill

SAP Fiori Tools — Fiori Elements List Report, Object Page, Overview Page configuration, manifest.json settings, annotation-driven UI, custom actions, custom columns, visual filters, flexible column layout, side drawer navigation. Use when configuring Fiori Elements apps, adding custom actions to List Reports, or setting up Fiori application layouts.

williamcorrea23 Skill

Use the curated ABAP skill set for design, implementation, review, testing, and documentation tasks in Claude-compatible workflows.

williamcorrea23 Skill

Evidence-backed analysis of custom ABAP codebases, including object search, dependency and where-used analysis, usage evidence, migration findings, retirement candidates, and technical documentation. Adapted from jonathanbernsteiner/sap-code-agents.

williamcorrea23 Skill

Generate evidence-based functional and technical documentation for SAP ABAP developments, with object inventory, diagrams, optional SAP GUI screenshots, chapter rendering, and safe cleanup. Adapted from mario-andreschak/docs-sap-abap-automated-documentation-prompts.

kienbui1995 Skill

Use when writing API docs, runbooks, user guides, architecture docs, or internal wikis

garyld1962 Bundle

Search one or more repos for a code pattern or behavior and produce a versioned Markdown investigation report. Supports literal, regex, and semantic (behavioral) search across multi-repo scope.

garyld1962 Skill

Write structured investigation matches to a versioned Markdown report under docs/code-investigations/ and update report pointers.