[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77VBHRS6R2XBW9SD1FS9E9R":3,"skill-same:01M77VBHRS6R2XBW9SD1FS9E9R":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77VBHRS6R2XBW9SD1FS9E9R","prd",null,"Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fprd\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.\"\nlicense: \"MIT\"\n---\n# Product Requirements Document (PRD)\n\n## Overview\n\nDesign comprehensive, production-grade Product Requirements Documents (PRDs) that bridge the gap between business vision and technical execution. This skill works for modern software systems, ensuring that requirements are clearly defined.\n\n## When to Use\n\nUse this skill when:\n\n- Starting a new product or feature development cycle\n- Translating a vague idea into a concrete technical specification\n- Defining requirements for AI-powered features\n- Stakeholders need a unified \"source of truth\" for project scope\n- User asks to \"write a PRD\", \"document requirements\", or \"plan a feature\"\n\n---\n\n## Operational Workflow\n\n### Phase 1: Discovery (The Interview)\n\nBefore writing a single line of the PRD, you **MUST** interrogate the user to fill knowledge gaps. Do not assume context.\n\n**Ask about:**\n\n- **The Core Problem**: Why are we building this now?\n- **Success Metrics**: How do we know it worked?\n- **Constraints**: Budget, tech stack, or deadline?\n\n### Phase 2: Analysis & Scoping\n\nSynthesize the user's input. Identify dependencies and hidden complexities.\n\n- Map out the **User Flow**.\n- Define **Non-Goals** to protect the timeline.\n\n### Phase 3: Technical Drafting\n\nGenerate the document using the **Strict PRD Schema** below.\n\n---\n\n## PRD Quality Standards\n\n### Requirements Quality\n\nUse concrete, measurable criteria. Avoid \"fast\", \"easy\", or \"intuitive\".\n\n```diff\n# Vague (BAD)\n- The search should be fast and return relevant results.\n- The UI must look modern and be easy to use.\n\n# Concrete (GOOD)\n+ The search must return results within 200ms for a 10k record dataset.\n+ The search algorithm must achieve >= 85% Precision@10 in benchmark evals.\n+ The UI must follow the 'Vercel\u002FNext.js' design system and achieve 100% Lighthouse Accessibility score.\n```\n\n---\n\n## Strict PRD Schema\n\nYou **MUST** follow this exact structure for the output:\n\n### 1. Executive Summary\n\n- **Problem Statement**: 1-2 sentences on the pain point.\n- **Proposed Solution**: 1-2 sentences on the fix.\n- **Success Criteria**: 3-5 measurable KPIs.\n\n### 2. User Experience & Functionality\n\n- **User Personas**: Who is this for?\n- **User Stories**: `As a [user], I want to [action] so that [benefit].`\n- **Acceptance Criteria**: Bulleted list of \"Done\" definitions for each story.\n- **Non-Goals**: What are we NOT building?\n\n### 3. AI System Requirements (If Applicable)\n\n- **Tool Requirements**: What tools and APIs are needed?\n- **Evaluation Strategy**: How to measure output quality and accuracy.\n\n### 4. Technical Specifications\n\n- **Architecture Overview**: Data flow and component interaction.\n- **Integration Points**: APIs, DBs, and Auth.\n- **Security & Privacy**: Data handling and compliance.\n\n### 5. Risks & Roadmap\n\n- **Phased Rollout**: MVP -> v1.1 -> v2.0.\n- **Technical Risks**: Latency, cost, or dependency failures.\n\n---\n\n## Implementation Guidelines\n\n### DO (Always)\n\n- **Define Testing**: For AI systems, specify how to test and validate output quality.\n- **Iterate**: Present a draft and ask for feedback on specific sections.\n\n### DON'T (Avoid)\n\n- **Skip Discovery**: Never write a PRD without asking at least 2 clarifying questions first.\n- **Hallucinate Constraints**: If the user didn't specify a tech stack, ask or label it as `TBD`.\n\n---\n\n## Example: Intelligent Search System\n\n### 1. Executive Summary\n\n**Problem**: Users struggle to find specific documentation snippets in massive repositories.\n**Solution**: An intelligent search system that provides direct answers with source citations.\n**Success**:\n\n- Reduce search time by 50%.\n- Citation accuracy >= 95%.\n\n### 2. User Stories\n\n- **Story**: As a developer, I want to ask natural language questions so I don't have to guess keywords.\n- **AC**:\n  - Supports multi-turn clarification.\n  - Returns code blocks with \"Copy\" button.\n\n### 3. AI System Architecture\n\n- **Tools Required**: `codesearch`, `grep`, `webfetch`.\n\n### 4. Evaluation\n\n- **Benchmark**: Test with 50 common developer questions.\n- **Pass Rate**: 90% must match expected citations.\n","# Product Requirements Document (PRD)\n\n## Overview\n\nDesign comprehensive, production-grade Product Requirements Documents (PRDs) that bridge the gap between business vision and technical execution. This skill works for modern software systems, ensuring that requirements are clearly defined.\n\n## When to Use\n\nUse this skill when:\n\n- Starting a new product or feature development cycle\n- Translating a vague idea into a concrete technical specification\n- Defining requirements for AI-powered features\n- Stakeholders need a unified \"source of truth\" for project scope\n- User asks to \"write a PRD\", \"document requirements\", or \"plan a feature\"\n\n---\n\n## Operational Workflow\n\n### Phase 1: Discovery (The Interview)\n\nBefore writing a single line of the PRD, you **MUST** interrogate the user to fill knowledge gaps. Do not assume context.\n\n**Ask about:**\n\n- **The Core Problem**: Why are we building this now?\n- **Success Metrics**: How do we know it worked?\n- **Constraints**: Budget, tech stack, or deadline?\n\n### Phase 2: Analysis & Scoping\n\nSynthesize the user's input. Identify dependencies and hidden complexities.\n\n- Map out the **User Flow**.\n- Define **Non-Goals** to protect the timeline.\n\n### Phase 3: Technical Drafting\n\nGenerate the document using the **Strict PRD Schema** below.\n\n---\n\n## PRD Quality Standards\n\n### Requirements Quality\n\nUse concrete, measurable criteria. Avoid \"fast\", \"easy\", or \"intuitive\".\n\n```diff\n# Vague (BAD)\n- The search should be fast and return relevant results.\n- The UI must look modern and be easy to use.\n\n# Concrete (GOOD)\n+ The search must return results within 200ms for a 10k record dataset.\n+ The search algorithm must achieve >= 85% Precision@10 in benchmark evals.\n+ The UI must follow the 'Vercel\u002FNext.js' design system and achieve 100% Lighthouse Accessibility score.\n```\n\n---\n\n## Strict PRD Schema\n\nYou **MUST** follow this exact structure for the output:\n\n### 1. Executive Summary\n\n- **Problem Statement**: 1-2 sentences on the pain point.\n- **Proposed Solution**: 1-2 sentences on the fix.\n- **Success Criteria**: 3-5 measurable KPIs.\n\n### 2. User Experience & Functionality\n\n- **User Personas**: Who is this for?\n- **User Stories**: `As a [user], I want to [action] so that [benefit].`\n- **Acceptance Criteria**: Bulleted list of \"Done\" definitions for each story.\n- **Non-Goals**: What are we NOT building?\n\n### 3. AI System Requirements (If Applicable)\n\n- **Tool Requirements**: What tools and APIs are needed?\n- **Evaluation Strategy**: How to measure output quality and accuracy.\n\n### 4. Technical Specifications\n\n- **Architecture Overview**: Data flow and component interaction.\n- **Integration Points**: APIs, DBs, and Auth.\n- **Security & Privacy**: Data handling and compliance.\n\n### 5. Risks & Roadmap\n\n- **Phased Rollout**: MVP -> v1.1 -> v2.0.\n- **Technical Risks**: Latency, cost, or dependency failures.\n\n---\n\n## Implementation Guidelines\n\n### DO (Always)\n\n- **Define Testing**: For AI systems, specify how to test and validate output quality.\n- **Iterate**: Present a draft and ask for feedback on specific sections.\n\n### DON'T (Avoid)\n\n- **Skip Discovery**: Never write a PRD without asking at least 2 clarifying questions first.\n- **Hallucinate Constraints**: If the user didn't specify a tech stack, ask or label it as `TBD`.\n\n---\n\n## Example: Intelligent Search System\n\n### 1. Executive Summary\n\n**Problem**: Users struggle to find specific documentation snippets in massive repositories.\n**Solution**: An intelligent search system that provides direct answers with source citations.\n**Success**:\n\n- Reduce search time by 50%.\n- Citation accuracy >= 95%.\n\n### 2. User Stories\n\n- **Story**: As a developer, I want to ask natural language questions so I don't have to guess keywords.\n- **AC**:\n  - Supports multi-turn clarification.\n  - Returns code blocks with \"Copy\" button.\n\n### 3. AI System Architecture\n\n- **Tools Required**: `codesearch`, `grep`, `webfetch`.\n\n### 4. Evaluation\n\n- **Benchmark**: Test with 50 common developer questions.\n- **Pass Rate**: 90% must match expected citations.\n",{"license":15,"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fprd",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill prd",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill prd",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill prd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fprd\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]