agent-skills

Facilitate structured brainstorming sessions as a coach and hybrid thinking partner: run divergent ideation on any topic using a library of ~20 named techniques (SCAMPER, Six Thinking Hats, reversal, analogical thinking, question storming, role playing…), one technique at a time, with the user generating ideas first and the AI building on them with clearly labeled additions — then converge, categorize, and deliver a session document with priorities and next steps. Use this skill whenever the user wants ideas or wants to think out loud together — "brainstorm with me", "give me ideas for…", "help me come up with…", "let's explore options for…", "I'm stuck on the name / the features / the campaign angle" — in any language (e.g. Vietnamese "brainstorm cùng tôi", "cho tôi ý tưởng", "nghĩ cùng tôi xem", "gợi ý phương án giúp tôi"; Spanish "ayúdame a generar ideas"; Japanese 「アイデア出しを手伝って」), even when they never say the word "brainstorm". Trigger for open-ended exploration of a topic, product, name, feature set, camp

Diagnose problems before solving them: a systematic problem-solving facilitator that turns "X is broken and we don't know why" into a precise problem statement, bounds it with Is/Is-Not analysis, finds root causes with the method that fits the problem's shape (Five Whys for linear chains, fishbone for multi-factor tangles, causal loops for systems that fight back), labels every causal claim verified or assumed, designs verification tests, then generates solutions traced to root causes, drives an evidence-cited decision, and plans rollout with pivot triggers. Use this skill whenever the user reports something failing, breaking, slowing, or recurring without a known cause — "sales dropped and we don't know why", "this keeps happening", "orders keep arriving late", "why does X keep failing", "find the root cause", "run a post-mortem", "5 whys" — in any language (e.g. Vietnamese "sao cứ bị vậy hoài", "tìm nguyên nhân gốc", "X đang hỏng mà không rõ vì sao"), even when they ask for solutions directly: "give me idea

Act as a disciplined project-management copilot (PM/PMO) that runs the delivery loop — initiation & charter, planning & scheduling, estimation with reference-class checks, risk management (ROAM), honest status reporting, scope change control, stakeholder communication, meetings turned into tracked actions, lessons learned, and portfolio roll-ups — methodology-agnostic (predictive, agile, hybrid) inside a fixed per-project `_project/` workspace where every status color, percent-complete, and estimate declares its evidence. Use this skill whenever the user wants to start, plan, track, rescue, or report on a project — "kick off this project", "make a project plan / timeline / WBS", "estimate how long this will take", "what date can I commit to", "build a risk register", "run a pre-mortem", "write the weekly status report for the steering committee", "the deadline slipped, what now", "turn this meeting transcript into action items and decisions", "prepare the steering-committee pack", "review my project portfolio

Audit the reasoning of any document or argument — a memo, proposal, investment analysis, board paper, article, or the user's own draft — and return its skeleton: claims, evidence, unstated assumptions, logical gaps, fallacies, and what would falsify it, with every finding anchored to exact quoted text. Runs a commit-first coaching loop that asks for the user's own judgment before revealing the audit, tracks their recurring blind spots in a persistent reasoning profile, and turns every audit into a rep that sharpens the user's thinking instead of replacing it. Use this skill whenever the user wants reasoning examined — "audit this argument", "is this analysis sound", "poke holes in this proposal", "review the logic of my draft", "what's wrong with this reasoning" — in any language (e.g. Vietnamese "phản biện giúp tôi", "soi lập luận này", "tài liệu này có lỗ hổng gì", "đánh giá đề xuất này giúp tôi", "góp ý bản nháp của tôi"; Spanish "analiza los argumentos de esta propuesta"; Chinese "帮我审一下这份提案的论证"; Japanese

Act as a disciplined product manager copilot that turns evidence into product decisions and operating artifacts: opportunity backlogs, RICE prioritization with sensitivity analysis, PRDs with story maps and user stories, north-star metrics and OKRs, experiment designs, launch plans with rollback criteria, feedback triage, platform-vs-feature decisions, and light pricing/packaging — all inside a persistent per-product workspace where every number declares its origin. Use this skill whenever the user wants to decide what to build, spec it, or ship it — "write a PRD for…", "prioritize our backlog / these features", "what should we build next", "plan OKRs for the quarter", "define our north star metric", "design an A/B test for…", "plan the launch of…", "triage this pile of customer feedback", "should this be a platform or a feature", "help me manage this product" — in any language ("viết PRD", "ưu tiên tính năng nào", "quản lý sản phẩm", "lập kế hoạch ra mắt", "プロダクト管理", "产品经理"), even when the user never says "p

Facilitate a full design-thinking engagement — Empathize, Define, Ideate, Prototype, Test — as a disciplined facilitator and thinking partner that never fabricates user insight: it designs the research (interview guides, observation plans, experiments with pass/fail criteria), the user brings back real data, and every insight traces to registered evidence. Use this skill whenever the user wants to understand users deeply and design a solution or experience for them — "run design thinking", "understand our users", "design user interviews", "synthesize these interview notes", "build personas", "write How-Might-We questions", "brainstorm solutions for…", "prototype this concept", "design an experiment / usability test to validate…", "our users are churning and we don't know why" — in any language ("tư duy thiết kế", "nghiên cứu người dùng", "phỏng vấn khách hàng", "デザイン思考", "设计思维"), even when the user never says "design thinking". Also trigger when the user drops raw interview notes, transcripts, or survey expor

A C-level strategy advisory board, run as a team of named specialist agents, that takes an executive from a raw strategic question to a defended, board-ready recommendation. Use this skill whenever the user faces a significant business decision or wants strategic analysis — market entry, build-vs-buy, M&A, digital transformation, annual planning, portfolio prioritization, pricing, a big investment, a competitive threat, a turnaround. Trigger on requests like "should we invest in / build / buy / enter…", "develop a strategy for…", "evaluate this opportunity", "make the business case", "stress-test this plan", "run a pre-mortem", or "prepare a board presentation" — in any language, even when the user doesn't say the word "strategy". Also trigger when the user names a board member (Drucker, Porter, Christensen, Graham, Grove, Wack, Taleb, Minto) or asks to convene the board / open a boardroom session.

Conduct rigorous, citation-backed desk market research: quick go/no-go market scans, market sizing (TAM/SAM/SOM), competitor analysis, customer demand signals, and trend/macro (PESTEL) analysis. Use this skill whenever the user wants to research, size, validate, or enter a market — "is there a market for…", "how big is the market for…", "who are the competitors of…", "should I build/launch/sell…", "validate this business idea", "market research for…", "market entry" — in any language and for any country's market (e.g. "nghiên cứu thị trường", "étude de marché", "市場調査", "análisis de mercado"), even when the user never says the words "market research". Also use it when another skill or workflow (strategy-board, design-thinking, a product brief) needs external market facts delivered into its fact base or research folder.

Act as a rigorous, end-to-end Data Scientist: frame a business question as a data problem, explore and audit datasets, run defensible statistical analysis, build and validate predictive models, and turn results into decision-ready reports. Use this skill whenever the user asks to analyze, explore, or profile a dataset or CSV/Parquet/Excel file; asks what drives a metric or why a number changed ("why did churn go up?"); wants to test whether a difference is real (A/B tests, experiments, "is this significant?", "how many samples do I need?"); wants a predictive model (churn, forecast, scoring, segmentation, classification, regression); asks to review an existing analysis, notebook, or model for flaws; or needs analysis results written up for decision-makers — in any language ("phân tích dữ liệu", "xây model dự đoán", "kiểm định A/B"), even when they never say "data science" or "statistics".

Deep-read long books and papers using Mortimer Adler's inspectional / analytical / syntopical method, the Recite step from SQ3R, and S. Keshav's three-pass method for papers, with page-anchored notes as external memory so the agent never has to load the whole text into one context window. Use this skill whenever the user asks to read, study, summarize, analyze, review, or answer questions about a long book, textbook, PDF, EPUB, thesis, dissertation, survey paper, or any document of roughly 50+ pages. Also use it when a `<slug>-notes/` workspace from a previous session already sits next to a source file and the user asks a follow-up question about that book — search the existing notes before re-reading anything. Trigger on these requests in whatever language the user writes them — for example Vietnamese "đọc sách", "tóm tắt sách", "phân tích luận án", or equivalent phrasing in any other language. Do not use this skill for short documents (under ~30 pages) that fit comfortably in context — read those directly i

Score candidate CVs on a 100-point scale against a Job Description. Use this skill when the user wants to evaluate, score, rank, or screen candidate CVs/resumes against a JD. Also trigger when the user mentions 'review CV', 'screen resume', 'rate candidates', 'shortlist', or any context involving matching resumes to job requirements.

Write, restructure, classify, and review documentation using the Diataxis framework. Use this skill whenever the user asks to create, improve, audit, or reorganize docs, documentation, knowledge bases, help centers, onboarding guides, internal process docs, manuals, runbooks, product docs, API/developer docs, tutorials, how-to guides, references, or explanations. Also use it when the user mentions Diataxis, tutorial, how-to, reference, explanation, docs taxonomy, documentation architecture, or asks why a document feels confusing. Do not use it for marketing copy, legal contracts, fiction, sales proposals, press releases, or persuasion-first writing unless the user explicitly wants a Diataxis-style documentation analysis.

A complete fiction-writing studio, run as a team of named specialist agents, that guides an author from a bare idea to a polished prose manuscript. Use this skill whenever the user wants to write, plan, or revise fiction — a novel, novella, short story, or series. Trigger on requests like "help me write a novel", "I have an idea for a story", "develop my characters", "build a world for my fantasy", "outline my plot", "fix this scene", "my dialogue feels flat", "give me beta-reader feedback", or any time the user is doing creative storytelling and would benefit from structured, craft-aware guidance. Also trigger when the user names a studio member (Homer, Aristotle, Fyodor, Tolkien, Scheherazade, Oscar, Max, Virginia, Borges, Bloom) or asks to switch creative roles / bring in a specialist.

Build interactive presentation websites — slide decks projected to a room, controlled by one presenter. Use this skill WHENEVER the user wants to create, build, or design a presentation, slide deck, talk, or "bài thuyết trình / slide / trình chiếu", and also when they ask to add/edit slides, restyle a deck, scaffold a new presentation project, reuse their presentation setup in another repo, or export slides to PDF — even if they don't say the word "slide" but clearly need projected talk visuals (e.g. "I'm giving a talk next week and need visuals", "dựng deck cho buổi chia sẻ", "làm mấy trang chiếu cho hội thảo"). Supports two tracks: a zero-build single HTML file, or a Vite + React project. Do NOT use it for printable documents, normal web apps, or dashboards meant for individual users to interact with.

Socratic questioning partner named Gadfly for deep learning through dialogue. Use this skill when the user wants to learn, understand, or explore a topic through questions rather than explanations. Trigger when the user says "teach me about...", "help me understand...", "I want to learn...", "ask me questions about...", "quiz me", "Socratic method", "Gadfly", or wants to deeply understand something through dialogue rather than passive reading. Also trigger when the user provides a text or document and wants to be questioned about it, or wants to check their own understanding of a concept.

Create high-quality, model-aware system prompts for any LLM (Claude, GPT, Gemini, open-source, etc.). Use this skill whenever the user wants to create, write, build, design, draft, or improve a system prompt, system instructions, or custom instructions for any AI model. Also trigger when the user asks about prompt engineering, prompt design, prompt optimization, or wants to define behavior for an AI assistant, chatbot, agent, or any LLM-powered application — even if they don't explicitly say "system prompt". Covers all use cases including chatbots, agentic systems, tool-use workflows, content generation, data extraction, code assistants, and multi-turn conversations.