- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add feimacode/open-design-agent-kit --skill open-design-deck-from-source -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add feimacode/open-design-agent-kit --skill open-design-deck-from-source -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add feimacode/open-design-agent-kit --skill open-design-deck-from-source -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add feimacode/open-design-agent-kit --skill open-design-deck-from-source -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/feimacode/open-design-agent-kit/tree/HEAD/.agents/skills/open-design-deck-from-source게시자 제공
Build a deck (or a one-pager) from existing documents with Open Design, storyline first, keeping every fact traceable to its source.
Request: the rest of the user's message (if there is none, ask the user: "Which document should the deck be built from, and for whom?")
How to talk to the user. Many people using Open Design don't write code, so:
od:prototype:poster-hero, no internal files (.artifact.json, .comments.json, config.json), and not the words "register", "manifest", "sidecar", "entry" or "surface", unless the user used them first.Identify the workspace files the request is based on. If it names none, ask which documents to use before doing anything else. Repository files count: CHANGELOG.md for a release deck, docs/adr/*.md for an architecture review, a metrics CSV or spreadsheet for a board update. Use up to 10 files; for a folder, pick the relevant files.
If you're unsure what a document contains, call read_open_design_source with its path. It returns an outline, and you can read the extracted Markdown by line range.
Call list_open_design_skills with mode: "deck" (or a query such as "pitch deck", "weekly report", "board") and choose the skill whose style fits the audience. For a single page instead of slides, choose a page or report skill.
Call prepare_open_design_brief with the skillId, the user's request as brief, and the document paths as sources. Pass designSystemId only if the user names a brand or style.
Follow the returned instructions. Read the parts of the extracted text you need, then write the outline at outlinePath, with one entry per slide giving a takeaway headline, supporting points, a visual type and a source reference. Show the outline to the user and stop until they approve or change it, unless they already said to just build it.
Build from the approved outline. Use numbers, names and quotes exactly as in the sources, never invent a statistic, and put the detail you cut from each slide into its speaker notes, ending with a Source: line.
Call register_open_design_artifact with the same sources. For every number its result says it couldn't find in the sources, check it: fix it, or say in that slide's notes how it was derived. Register again after fixing.
Tell the user where the deck and its outline are, mention any images reused from the documents, and offer to export it as PowerPoint or PDF with export_open_design_artifact. PowerPoint exports include the speaker notes. Offer both PowerPoint versions: the default, which looks exactly like the deck, and editable: true, which people can edit in PowerPoint, Keynote, Google Slides or Canva.
Turn a document (a report, spec, spreadsheet, PDF, existing deck, or repository files such as a CHANGELOG) into a deck or one-pager, storyline first, with every number traced back to the source — use
---name: open-design-deck-from-sourcedescription: Turn a document (a report, spec, spreadsheet, PDF, existing deck, or repository files such as a CHANGELOG)…---# .agents/skills/open-design-deck-from-source/SKILL.md개요
Turn a document (a report, spec, spreadsheet, PDF, existing deck, or repository files such as a CHANGELOG) into a deck or one-pager, storyline first, with every number traced back to the source — use whenever the user wants slides, a deck, a presentation or a one-pager made from an existing document, spreadsheet, PDF or deck, or from repository files (CHANGELOG, RFCs, architecture decision records, metrics CSVs), even if they don't mention Open Design
FAQ
게시자에게서 .agents/skills/open-design-deck-from-source/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/feimacode/open-design-agent-kit에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.