Loading...
Loading...
Found 5 Skills
Use when an HR workshop student kicks off the workshop, uploads a filled brainstorm worksheet (any filename), pastes or attaches an idea document, describes an internal tool, or wants to go from a rough idea to PRD, build slice (今日切片), HTML prototype, a running local app, and local run. This is the generic student entry for every group. Do not require a Group 6 / Group 4 wrapper.
Turn engagement/pulse survey CSV (EmpID, Department, Manager, Q1–Q20) into the standard 8-section Company Pulse PDF team report, composite charts PNG, and per-manager personal PDFs. Use when the user provides pulse/engagement survey raw data, asks for a Pulse Survey Report, rankings, leader deep dives, or output matching the Company Pulse Survey Report template.
Guided 6-step executive presentation deck pipeline from CSV/XLSX or free-text input to HTML slides plus copy-paste prompts for Gamma and Kimi AI. Default visual system is the bundled DAYMARK mood board (navy / teal / gold / bone). Step 5 optionally accepts a PDF/PPTX/HTML layout reference for 排版 and exhibit structure only — never replacing DAYMARK color, type, or logo. Use when building executive decks, year-end performance presentations, pulse survey slides, or any slide deck where the user provides data as a file or text and wants HTML + Gamma + Kimi outputs.
Use when an HR workshop student cannot open a local HTML or Next.js prototype, Node.js is missing, npm run dev fails, the project folder is wrong, localhost will not load, a port is in use, or the Agent is about to build/run a workshop prototype and must check the computer first. Also use for standalone "Node not installed" / "npm run dev 不行" help when the student did not start a product skill.
Help users write high-quality Product Requirements Documents (PRD) from scratch, or evaluate/improve existing requirement documents. It is suitable for non-product manager users in vibe coding scenarios who have product ideas but don't know how to structure them. This skill must be used when users mention keywords such as "requirement document", "PRD", "product requirement", "functional document", "I want to make a product/function/App", "help me organize requirements", "is there any problem with the AI-written requirement document", "help me supplement requirements", "I want to make a tool", etc. Even if the description is very brief, this skill must be triggered, and do not skip directly to outputting the document.