Przejdź do treści
Biblioteka skilli
Dokumenty i biuro · Pisanie

officecraft

/officecraft

Tworzy i poprawia prezentacje PowerPoint oraz dokumenty Word, w tym raporty, propozycje i materiały badawcze.

Licencja
MIT
Ostatnia zmiana repozytorium
04.11.2026

Ocena i bezpieczeństwo

95/ 100Klasa: dobry
Format20 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
101
Skrypty
9
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 04.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co sprawdzić przed instalacją
  • 9 skryptów w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
  • Paczka skrócona: część plików jest zbyt duża albo wykonywalna. Pełny folder jest w repozytorium.

Skrypty: scripts/validate_catalog.py, scripts/validate_repo.py, upstream/powerpoint-skill/powerpoint-skill-main/example/linear_perm_slides/generate_slides.js, upstream/powerpoint-skill/powerpoint-skill-main/powerpoint-slides/scripts/check_overlaps.py, upstream/powerpoint-skill/powerpoint-skill-main/powerpoint-slides/scripts/inject_omml.py, upstream/powerpoint-skill/powerpoint-skill-main/powerpoint-slides/s

Co robi i kiedy

Tworzy i poprawia prezentacje PowerPoint oraz dokumenty Word, w tym raporty, propozycje i materiały badawcze.

Oryginalny opis (EN)

Create, edit, review, automate, and publish professional PowerPoint (.pptx) presentations and Microsoft Word (.docx) documents. Trigger on PowerPoint, PPT, PPTX, Word, DOCX, reports, proposals, research talks, slide decks, document formatting, and office workflows.

Jak działa

  1. Mission
  2. Intake
  3. Universal workflow
  4. PowerPoint rules
  5. Human-centered visual design and typography
  6. Anti-AI failure prevention (mandatory for substantial deliverables)
  7. Word rules
  8. Academic and evidence rules
  9. Quality gates
  10. Detailed production references
Sekcje z nagłówków SKILL.md, w oryginale · 187 linii, 1 792 słów
Podgląd SKILL.md
---
name: officecraft
description: >
  Create, edit, review, automate, and publish professional PowerPoint (.pptx) presentations
  and Microsoft Word (.docx) documents. Trigger on PowerPoint, PPT, PPTX, Word, DOCX,
  reports, proposals, research talks, slide decks, document formatting, and office workflows.
license: MIT
---

# OfficeCraft — PowerPoint & Word Skill

## Mission
Produce accurate, audience-centered, accessible, editable Office deliverables. Communication and
evidence take priority over decorative styling. Never invent facts, source references, quotations,
data, credentials, or user preferences.

## Intake
For substantial work, establish:
- deliverable and intended use;
- audience and their prior knowledge;
- purpose (inform, decide, teach, persuade, document);
- target length, timing, and level of detail;
- source files, data, brand assets, citation style, and constraints;
- required output formats and deadline.

Ask only for essential missing details. If the user wants a quick draft, make reasonable reversible
assumptions and label them.

## Universal workflow
1. Inspect supplied files and identify authoritative source material.
2. Extract facts, numbers, claims, quotations, and assets with provenance.
3. Plan the narrative and structure before polishing.
4. Draft in an editable native format when possible.
5. Apply a consistent design or document system.
6. Validate content, citations, accessibility, layout, and technical integrity.
7. Deliver the editable source and explain any limitations.

## PowerPoint rules
- Use a 16:9 widescreen canvas unless the user specifies otherwise.
- One principal message per slide; use takeaway/action titles for analytical decks.
- Build a logical story, not a pile of topic headings.
- Use charts for quantitative comparisons and diagrams for relationships or processes.
- Label units, periods, baselines, and data sources; do not distort axes.
- Keep typography readable; avoid tiny footnotes and overfilled slides.
- Use color-blind-aware palettes and never rely on color alone.
- Keep layouts varied but systematic; align to a grid and preserve whitespace.
- Use native editable objects where practical; cite third-party images and figures.
- Add useful speaker notes when requested; prepare appendix material for likely questions.
- Export to PDF or images and inspect every slide for clipping, overlap, and rendering issues.


## Human-centered visual design and typography

Treat every deck as a designed communication, not a decorated document. The goal is clear,
credible, audience-aware work that does not resemble a one-click AI template.

### Typography and color
- Default to **near-black or charcoal text** on light backgrounds (for example `202124`,
  `222222`, or `292929`). Do not make ordinary body copy blue. Blue is an optional accent,
  not the default text color. Use it sparingly for links, data series, or a deliberate brand role.
- Use high-contrast text/background combinations. Aim for WCAG AA contrast: 4.5:1 for normal
  text and 3:1 for large text. Never communicate meaning through color alone.
- Choose fonts for the audience, tone, language, and available software. Prefer dependable,
  readable fonts already installed or embedded where licensing permits. Good starting points:
  Aptos or Calibri for a contemporary Office-native look; Arial for broad compatibility;
  Georgia or Cambria for a more editorial or academic voice; Avenir/Source Sans/Inter only
  when availability and embedding rights are confirmed.
- Use one type family for a restrained system, or at most two complementary families
  (typically sans-serif for headings/body, or a serif display face paired with a sans-serif).
  Do not mix fonts slide by slide. Avoid novelty fonts, thin weights, all-caps body text,
  excessive italics, and decorative scripts.
- Establish a deliberate type scale: clear title, section/subhead, body, and caption levels.
  Keep body text comfortably readable at presentation distance; do not shrink text to force
  excess content onto a slide. Split or simplify instead.
- Use bold weight, size, and spacing to establish hierarchy before adding color. Body copy
  should remain dark and calm; reserve accent colors for a small number of meaningful signals.

### Human voice and natural writing
- Write like a knowledgeable person explaining something to this specific audience—not like
  a generic marketing generator. Use concrete nouns, active verbs, varied sentence length,
  and specific evidence.
- Preserve the user's terminology, point of view, and level of formality. Do not invent a
  personal anecdote, opinion, quote, experience, or first-person claim.
- Remove empty hype, filler introductions, repetitive conclusions, and phrases such as
  "in today's fast-paced world", "unlock the power", "game-changer", "delve into", and
  "it is important to note" unless genuinely appropriate to the source.
- Avoid mechanical patterns: identical three-part headings on every slide, repeated
  "problem/solution/impact" cards, every title followed by a subtitle, and bullet lists
  with artificially identical rhythm.
- Make slide titles state the point or finding, not merely label the topic. Use concise,
  natural wording; not every title needs to be a full sentence.
- Do not paraphrase the same point in the title, subtitle, body, chart caption, and speaker
  notes. Give each element a distinct job.
- Keep slide text concise, but do not remove nuance needed for accuracy. Put explanation in
  speaker notes or supporting material when appropriate, not in tiny text.

### Layout, imagery, and visual variety
- Choose a layout because it fits the content. Vary composition naturally: a strong chart,
  one striking image, a comparison, a timeline, a short narrative, a diagram, or a simple
  text slide may each be right. Do not force every slide into cards or columns.
- Avoid repetitive rounded-card grids, gratuitous gradients, decorative title rules,
  random icons, meaningless stock photos, generic 3D illustrations, and ornamental shapes.
  Use these only when they serve a clear communicative purpose or the user's brand.
- Prefer authentic supplied imagery, relevant documentary photography, meaningful diagrams,
  and accurately sourced charts. Never generate or insert an image merely to fill empty space.
  Do not fabricate logos, screenshots, charts, or visual evidence.
- Use whitespace intentionally. Align related objects, keep margins consistent, and make
  the focal point obvious. Do not fill every available inch just to make a slide look busy.
- Use restrained color: a neutral foundation, dark readable text, and one or two purposeful
  accents. Do not default to blue gradients or use a different palette on every slide.
- Make charts readable and honest: label axes and units, show relevant baselines, avoid
  misleading scales, and annotate the takeaway. Keep legends and labels close to the data.

### Human review and anti-slop quality gate
Before delivery, review the deck as both its author and a skeptical audience member:
1. Can a viewer identify the main point of each slide in about five seconds?
2. Does every slide earn its place in the story? Remove or combine filler slides.
3. Is each visual relevant, accurate, legible, and properly attributed?
4. Are the fonts, sizes, colors, margins, alignment, and spacing consistent without looking
   mechanically identical?
5. Is ordinary text dark (near-black/charcoal) unless a brand or accessibility reason says
   otherwise? Is contrast sufficient?
6. Does the wording sound natural when read aloud? Remove generic AI phrasing and repetition.
7. Are claims, statistics, dates, quotations, and citations verified against source material?
8. Are there any clipping, overlap, awkward line breaks, orphaned labels, tiny footnotes,
   inconsistent page numbers, or broken editable objects?
9. Does the file remain editable and render correctly in the target presentation software?
10. Would a human presenter feel comfortable explaining and defending every slide?

Do not claim a deck is human-made or guarantee that nobody will recognize AI assistance.
The standard is thoughtful human review, not disguising authorship.

## Anti-AI failure prevention (mandatory for substantial deliverables)
- Apply `docs/ANTI_AI_OUTPUT_FAILURES.md` as the production and red-team review standard.
- Do not confuse polish with quality: remove filler, unsupported claims, generic visuals, repeated layouts, and unnecessary slides/pages.
- Build a story and evidence trail before styling. Verify sources and calculations rather than trusting generated summaries.
- Make every visual earn its place; never use generated imagery as factual evidence.
- Preserve native editability where practical and test the actual exported file in the target Office-compatible application.
- Review from the audience's perspective and document any unverified facts, assumptions, compatibility limits, or missing sources.

## Word rules
- Use semantic built-in heading styles in logical order.
- Use paragraph and character styles rather than manual formatting.
- Use page/section breaks intentionally; avoid repeated blank paragraphs for layout.
- Use real numbered/bulleted lists and accessible tables with header rows.
- Add captions, cross-references, citations, footnotes, and a table of contents where appropriate.
- Use descriptive hyperlinks and meaningful alt text.
- Check headers, footers, page numbers, widows/orphans, tables crossing pages, and section settings.
- Inspect the exported PDF and verify that the DOCX remains editable.

## Academic and evidence rules
- Separate research question, contribution, method, evidence, interpretation, limitations, and implications.
- Do not overstate causality or generalizability.
- Cite borrowed figures, tables, claims, and quotations close to their use.
- Distinguish the author's results from prior work and your synthesis.
- Include references and preserve source traceability.

## Quality gates
A deliverable is not complete until:
- names, dates, numbers, units, and citations are checked;
- there are no unintended placeholders or broken links;
- no text or object is clipped or overlapping;
- hierarchy and typography are consistent;
- accessibility basics are addressed;
- final files open successfully and match the requested format.

## Detailed production references
- `docs/ANTI_AI_OUTPUT_FAILURES.md` — recurring AI-output complaints, prevention rules, and red-team questions.
- `docs/POWERPOINT_WORKFLOW.md` — slide-story, design, chart, and export workflow.
- `docs/WORD_WORKFLOW.md` — document structure, typography, tables, and pagination workflow.
- `docs/QUALITY_GATES.md` and `templates/REVIEW_CHECKLIST.md` — release criteria.

## Catalog
The companion catalog contains 1,200 task-specific workflows across 30 domains. Consult
`catalog/INDEX.md` or `catalog/skills.json` to select the most relevant recipe. Each recipe has
an ID, objective, workflow, acceptance criteria, and tags.

## Tooling
For PowerPoint automation, the included upstream implementation uses PptxGenJS and includes
scripts and references. Follow its own README and prerequisites. For Word automation, choose a
suitable DOCX library or Microsoft Word automation interface available in the runtime; validate
the final document in Word-compatible software. Do not claim to have executed software or checked
visual output unless that actually happened.


## Regression prevention and complaint-driven quality
Before delivery, explicitly test the failure modes most likely for the artifact:
- **PowerPoint:** open the saved PPTX in the target app; inspect every slide for overflow, overlap, font substitution, missing media, broken charts, animation loss and off-slide objects; compare a PDF export.
- **Word:** use named styles rather than manual formatting; inspect section breaks, list numbering, captions, footnotes/endnotes, fields, table widths/repeating headers, image anchoring, page numbers and page breaks after edits and export.
- **Human quality:** reject generic stock layouts, repetitive card grids, filler copy, unsupported claims and decorative images without a communicative purpose. Explain the audience-specific rationale for major design choices.
- **Accessibility:** verify semantic headings, reading order, contrast, meaningful links, alt text, table headers and non-color cues.
- **Handoff:** include editable source, required assets, font/dependency notes, version information, known limitations and a clean reopen test.

Treat public social feedback as anecdotal signal, not proof of prevalence. Convert each credible complaint into a sanitized reproduction, a preventive workflow or test, and a linked release note. Never expose confidential user files or secrets in public issues.
Pliki w paczce (101)
  • CHANGELOG.md 3 KB
  • CODE_OF_CONDUCT.md 1 KB
  • CONTRIBUTING.md 1 KB
  • LICENSE 1 KB
  • README.md 10 KB
  • ROADMAP.md 1 KB
  • SECURITY.md 1 KB
  • SKILL.md 13 KB
  • THIRD_PARTY_NOTICES.md 1 KB
  • .github/CODEOWNERS 1 KB
  • .github/PULL_REQUEST_TEMPLATE.md 1 KB
  • .github/dependabot.yml 1 KB
  • .github/DISCUSSION_TEMPLATE/feedback.yml 1 KB
  • .github/ISSUE_TEMPLATE/bug_report.yml 1 KB
  • .github/ISSUE_TEMPLATE/config.yml 1 KB
  • .github/ISSUE_TEMPLATE/skill_request.yml 1 KB
  • .github/workflows/ci.yml 1 KB
  • .github/workflows/release.yml 1 KB
  • README_LANGUAGES/README.ar.md 1 KB
  • README_LANGUAGES/README.de.md 1 KB
  • README_LANGUAGES/README.en.md 1 KB
  • README_LANGUAGES/README.es.md 1 KB
  • README_LANGUAGES/README.fr.md 1 KB
  • README_LANGUAGES/README.hi.md 2 KB
  • README_LANGUAGES/README.it.md 1 KB
  • README_LANGUAGES/README.ja.md 1 KB
  • README_LANGUAGES/README.ko.md 1 KB
  • README_LANGUAGES/README.md 1 KB
  • README_LANGUAGES/README.nl.md 1 KB
  • README_LANGUAGES/README.pl.md 1 KB
  • README_LANGUAGES/README.pt-BR.md 1 KB
  • README_LANGUAGES/README.ru.md 2 KB
  • README_LANGUAGES/README.tr.md 1 KB
  • README_LANGUAGES/README.zh-CN.md 1 KB
  • README_LANGUAGES/README.zh-TW.md 1 KB
  • catalog/INDEX.md 3 KB
  • catalog/domains/office_workflow.md 67 KB
  • catalog/domains/pptx_academic.md 68 KB
  • catalog/domains/pptx_accessibility.md 68 KB
  • catalog/domains/pptx_animation.md 67 KB
  • catalog/domains/pptx_automation.md 68 KB
  • catalog/domains/pptx_brand.md 65 KB
  • catalog/domains/pptx_business.md 68 KB
  • catalog/domains/pptx_charts.md 67 KB
  • catalog/domains/pptx_conversion.md 68 KB
  • catalog/domains/pptx_diagrams.md 67 KB
  • catalog/domains/pptx_media.md 65 KB
  • catalog/domains/pptx_quality.md 67 KB
  • catalog/domains/pptx_sales.md 68 KB
  • catalog/domains/pptx_slide_design.md 66 KB
  • catalog/domains/pptx_storytelling.md 66 KB
  • catalog/domains/pptx_training.md 68 KB
  • catalog/domains/word_academic.md 67 KB
  • catalog/domains/word_accessibility.md 67 KB
  • catalog/domains/word_automation.md 67 KB
  • catalog/domains/word_business.md 67 KB
  • catalog/domains/word_conversion.md 67 KB
  • catalog/domains/word_documents.md 67 KB
  • catalog/domains/word_formatting.md 67 KB
  • catalog/domains/word_legal.md 66 KB
  • catalog/domains/word_references.md 67 KB
  • catalog/domains/word_resume.md 67 KB
  • catalog/domains/word_review.md 67 KB
  • catalog/domains/word_tables.md 66 KB
  • catalog/domains/word_templates.md 67 KB
  • catalog/domains/word_writing.md 67 KB
  • docs/ANTI_AI_OUTPUT_FAILURES.md 16 KB
  • docs/FAQ.md 1 KB
  • docs/GITHUB_SETUP.md 2 KB
  • docs/HUMAN_DESIGN_TYPOGRAPHY.md 6 KB
  • docs/POWERPOINT_WORKFLOW.md 2 KB
  • docs/QUALITY_GATES.md 1 KB
  • docs/USER_PAIN_POINTS_AND_PREVENTION.md 4 KB
  • docs/WORD_WORKFLOW.md 2 KB
  • scripts/validate_catalog.py 2 KB
  • scripts/validate_repo.py 1 KB
  • skills/officecraft/SKILL.md 11 KB
  • skills/officecraft/catalog-reference.md 1 KB
  • templates/PROJECT_BRIEF.md 1 KB
  • templates/REVIEW_CHECKLIST.md 1 KB
  • templates/SLIDE_STORYBOARD.md 1 KB
  • upstream/README.md 1 KB
  • upstream/powerpoint-skill/powerpoint-skill-main/.gitignore 1 KB
  • upstream/powerpoint-skill/powerpoint-skill-main/LICENSE 1 KB
  • upstream/powerpoint-skill/powerpoint-skill-main/README.md 9 KB
  • upstream/powerpoint-skill/powerpoint-skill-main/example/B├╝nz τ¡ë - 2025 - Linear-Time Permutation Check.pdf 819 KB
  • upstream/powerpoint-skill/powerpoint-skill-main/example/linear_perm_slides/diagrams.json 2 KB
  • upstream/powerpoint-skill/powerpoint-skill-main/example/linear_perm_slides/formulas.json 4 KB
  • upstream/powerpoint-skill/powerpoint-skill-main/example/linear_perm_slides/generate_slides.js 31 KB
  • upstream/powerpoint-skill/powerpoint-skill-main/example/linear_perm_slides/linear_perm_slides.pptx 386 KB
  • upstream/powerpoint-skill/powerpoint-skill-main/powerpoint-slides/SKILL.md 51 KB
  • upstream/powerpoint-skill/powerpoint-skill-main/powerpoint-slides/diagram-rendering.md 9 KB
  • upstream/powerpoint-skill/powerpoint-skill-main/powerpoint-slides/formula-rendering.md 7 KB
  • upstream/powerpoint-skill/powerpoint-skill-main/powerpoint-slides/pptxgenjs-reference.md 20 KB
  • upstream/powerpoint-skill/powerpoint-skill-main/powerpoint-slides/references/themes.md 20 KB
  • upstream/powerpoint-skill/powerpoint-skill-main/powerpoint-slides/scripts/check_overlaps.py 15 KB
  • upstream/powerpoint-skill/powerpoint-skill-main/powerpoint-slides/scripts/inject_omml.py 10 KB
  • upstream/powerpoint-skill/powerpoint-skill-main/powerpoint-slides/scripts/render_diagrams.py 13 KB
  • upstream/powerpoint-skill/powerpoint-skill-main/powerpoint-slides/scripts/render_latex.py 8 KB
  • upstream/powerpoint-skill/powerpoint-skill-main/powerpoint-slides/scripts/soffice.py 1 KB
  • upstream/powerpoint-skill/powerpoint-skill-main/powerpoint-slides/scripts/thumbnail.py 3 KB

Pominięte w paczce: 3 (zbyt duże albo wykonywalne), są w repozytorium.

Wersje

RepozytoriumWynikLicencja
Ta strona · notweirdguy4212/officecraft-skills95MIT
notweirdguy4212/officecraft-skills100MIT
notweirdguy4212/officecraft-skills100MIT
notweirdguy4212/officecraft-skills95MIT

Migawka bazy z 13.11.2026 · wersja paczki 46539a6fc51c (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 85office-parser
    Odczytuje dokumenty Word, PowerPoint i Excel strumieniowo, dzieląc je na fragmenty do dalszej pracy z treścią i danymi.
  • 100powerpoint
    Tworzy profesjonalne prezentacje PowerPoint i pliki pptx na prośbę o slajdy lub prezentację.
  • 90Presentations
    Czyta, tworzy i edytuje prezentacje PowerPoint lub Google Slides, gdy użytkownik prosi o slajdy, deck albo plik PPTX.
  • 95document-processing
    Tworzy, edytuje i analizuje dokumenty biurowe (PDF, DOCX, PPTX, XLSX): wyciąga tekst, wypełnia formularze, tworzy dokumenty i analizuje dane.
  • 100working-with-documents
    Tworzy i edytuje dokumenty Word, PDF i PowerPoint, obsługuje śledzenie zmian oraz konwersję między formatami.
  • 100pptx
    Tworzy, czyta, edytuje i łączy prezentacje PowerPoint (.pptx), w tym układy, notatki, komentarze i szablony.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.