[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BYRDXA3VDRXY27C29K93Y6":3,"skill-same:01M6BYRDXA3VDRXY27C29K93Y6":93},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M6BYRDXA3VDRXY27C29K93Y6","setup-matt-pocock-skills",null,"Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.","Vortex375\u002Fseraph","Vortex375","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5016523?v=4","01M6BYMHA5FQE4EMD6BSZ13M46","Benjamin Schmitz","01M6BYMHEYGQ7DM3Q8A7KBNZ48",2,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"setup","matt pocock","setup matt pocock skills","repo","for","true","layout","domain","tracker","issue","up","use","engineering skills","configure","first","doc","SET","engineering","run","triage","2026-11-10 10:12:30",false,"---\nname: resume-formatter\ndescription: Ensure ATS-friendly formatting and create clean, scannable layouts. Use when the user mentions resume format, layout, template, design, or fixing formatting issues.\n---\n\n# Resume Formatter\n\n## When to Use This Skill\n\nUse this skill when the user:\n- Needs help with resume layout and formatting\n- Has a messy or hard-to-read resume\n- Wants to ensure ATS compatibility through formatting\n- Needs a clean, professional design\n- Mentions: \"format resume\", \"resume layout\", \"resume design\", \"clean resume\", \"professional format\"\n\n## Core Capabilities\n\n- Structure resumes for optimal readability\n- Ensure ATS compatibility through formatting\n- Create visual hierarchy\n- Optimize white space and margins\n- Select appropriate fonts and sizes\n- Balance aesthetic appeal with functionality\n\n## Formatting Fundamentals\n\n### The Dual Audience Challenge\n\nYour resume must work for:\n1. **ATS (Applicant Tracking Systems)** - Robots that parse text\n2. **Human Readers** - Recruiters who scan quickly\n\n**The Solution:** Clean, simple formatting that satisfies both.\n\n## Document Setup\n\n### Page Length\n- **Entry Level (0-5 years):** 1 page\n- **Mid-Level (5-15 years):** 1-2 pages\n- **Senior\u002FExecutive (15+ years):** 2 pages (max 3 for executives)\n\n### Margins\n- **Recommended:** 0.5\" - 1\" all sides\n- **Minimum:** 0.5\" (don't go smaller)\n- **Maximum:** 1\" (don't waste space)\n\n### Font Selection\n\n**Safe, ATS-Friendly Fonts:**\n- **Sans-serif:** Arial, Calibri, Helvetica, Verdana\n- **Serif:** Times New Roman, Georgia, Garamond\n\n**Font Sizes:**\n- **Name:** 16-20pt\n- **Section Headers:** 12-14pt\n- **Body Text:** 10-12pt\n- **Minimum readable:** 10pt\n\n### Spacing\n- **Line spacing:** 1.0 to 1.15\n- **Space after paragraphs:** 6-12pt\n- **Section spacing:** 12-16pt between sections\n\n## ATS-Safe Formatting Rules\n\n### DO:\n- ✅ Use standard fonts\n- ✅ Use simple bullet points (•, -, *)\n- ✅ Use bold and italic sparingly\n- ✅ Use standard section headers\n- ✅ Save as .docx or text-based .pdf\n- ✅ Put contact info in body (not header)\n- ✅ Use single column layout\n- ✅ Use consistent formatting throughout\n\n### DON'T:\n- ❌ Use tables (except simple ones for contact info)\n- ❌ Use text boxes\n- ❌ Use columns (multi-column layouts)\n- ❌ Use headers\u002Ffooters for important info\n- ❌ Use images or graphics\n- ❌ Use unusual fonts\n- ❌ Use skill bars or progress indicators\n- ❌ Use special characters or emojis\n- ❌ Use color for essential information\n\n## Section Organization\n\n### Standard Section Order\n\n```\n1. Contact Information\n2. Professional Summary (optional)\n3. Skills\u002FTechnical Skills\n4. Professional Experience\n5. Education\n6. Certifications (if relevant)\n7. Additional (volunteer, languages, etc.)\n```\n\n### Section Header Formatting\n\n**ATS-Recognized Headers:**\n- PROFESSIONAL EXPERIENCE or WORK EXPERIENCE\n- EDUCATION\n- SKILLS or TECHNICAL SKILLS\n- PROFESSIONAL SUMMARY or SUMMARY\n- CERTIFICATIONS\n- PROJECTS\n\n**Format Options:**\n```\nPROFESSIONAL EXPERIENCE\n━━━━━━━━━━━━━━━━━━━━━━\n\nor\n\nProfessional Experience\n_______________________\n\nor\n\nPROFESSIONAL EXPERIENCE\n```\n\n## Contact Information Layout\n\n### Recommended Format\n```\nJOHN SMITH\njohn.smith@email.com | (555) 123-4567 | linkedin.com\u002Fin\u002Fjohnsmith\nSan Francisco, CA\n```\n\n### Alternative Format\n```\nJOHN SMITH\nSan Francisco, CA\njohn.smith@email.com | (555) 123-4567\nLinkedIn: linkedin.com\u002Fin\u002Fjohnsmith | GitHub: github.com\u002Fjohnsmith\n```\n\n### What to Include\n- ✅ Full name\n- ✅ Professional email\n- ✅ Phone number\n- ✅ City, State (no full address needed)\n- ✅ LinkedIn URL\n- ✅ Portfolio\u002FGitHub (if relevant)\n\n### What to Exclude\n- ❌ Full street address\n- ❌ Photo\n- ❌ Date of birth\n- ❌ Marital status\n- ❌ Multiple phone numbers\n- ❌ Personal social media\n\n## Experience Section Formatting\n\n### Standard Format\n```\nCOMPANY NAME | City, ST\nJob Title | Month Year - Month Year\n\n• Achievement bullet with metrics and results\n• Achievement bullet with metrics and results\n• Achievement bullet with metrics and results\n```\n\n### Alternative Format\n```\nJob Title\nCOMPANY NAME, City, ST                    Month Year - Month Year\n\n• Achievement bullet with metrics and results\n• Achievement bullet with metrics and results\n```\n\n### Date Formatting\n- **Consistent format:** Use same format throughout\n- **Recommended:** Month Year (Jan 2020 - Present)\n- **Also acceptable:** MM\u002FYYYY (01\u002F2020 - Present)\n- **Avoid:** Full dates (January 15, 2020)\n\n### Bullet Point Guidelines\n- **Length:** 1-2 lines each\n- **Format:** Start with action verb, end with result\n- **Quantity:** 3-6 bullets per role (more for recent, fewer for old)\n- **Symbol:** Use standard bullets (•, -, *)\n\n## Skills Section Formatting\n\n### Option 1: Simple List\n```\nSKILLS\nPython, JavaScript, SQL, React, Node.js, AWS, Docker, Git, Agile, JIRA\n```\n\n### Option 2: Categorized\n```\nTECHNICAL SKILLS\nLanguages: Python, JavaScript, TypeScript, SQL\nFrameworks: React, Node.js, Django, Flask\nTools: AWS, Docker, Kubernetes, Git, Jenkins\n```\n\n### Option 3: Columns (Careful with ATS)\n```\nSKILLS\nLanguages        Frameworks       Tools\nPython           React            AWS\nJavaScript       Node.js          Docker\nSQL              Django           Git\n```\n\n**Note:** Multi-column layouts may cause ATS issues. Test before using.\n\n## Education Section Formatting\n\n### Standard Format\n```\nEDUCATION\nBachelor of Science in Computer Science\nUniversity of California, Berkeley | 2018\nGPA: 3.8\u002F4.0 (include if 3.5+)\n```\n\n### With Honors\u002FDetails\n```\nEDUCATION\nMBA, Finance & Strategy | Stanford Graduate School of Business | 2020\n• Graduated with Distinction\n• Relevant Coursework: Corporate Finance, M&A Strategy\n```\n\n## Visual Hierarchy Principles\n\n### Hierarchy Order\n1. **Name** - Largest, most prominent\n2. **Section Headers** - Clear divisions\n3. **Job Titles\u002FCompany Names** - Easy to scan\n4. **Bullet Points** - The details\n\n### Creating Hierarchy\n- Use font SIZE to create levels\n- Use **BOLD** for emphasis (names, titles, headers)\n- Use CAPS for section headers\n- Use consistent spacing to separate sections\n\n## White Space Management\n\n### Good White Space:\n- Between sections (clear separation)\n- After headings (visual breathing room)\n- Between bullets (don't cram)\n- Around margins (frame the content)\n\n### Bad White Space:\n- Huge gaps between sections\n- Inconsistent spacing\n- Half-empty pages\n- Excessive margins eating space\n\n## Common Formatting Mistakes\n\n### Mistake 1: Wall of Text\n**Problem:** Dense paragraphs with no bullets\n**Solution:** Use bullet points, keep paragraphs short\n\n### Mistake 2: Inconsistent Formatting\n**Problem:** Different fonts, sizes, or styles throughout\n**Solution:** Pick one format and stick to it\n\n### Mistake 3: Trying to Be Creative\n**Problem:** Fancy designs that break ATS\n**Solution:** Save creativity for portfolio, not resume\n\n### Mistake 4: Too Much Information\n**Problem:** Cramming everything onto one page\n**Solution:** Edit ruthlessly, prioritize relevance\n\n### Mistake 5: Not Enough Information\n**Problem:** Half-page resume with massive margins\n**Solution:** Add detail, reduce margins (to 0.5\")\n\n## File Format Guidelines\n\n### For Online Applications\n- **.docx** - Best for ATS parsing\n- **.pdf** - Good if created from Word (not scanned)\n\n### For Email\u002FDirect Send\n- **.pdf** - Preserves formatting\n\n### File Naming\n```\nFirstName_LastName_Resume.pdf\nJohnSmith_Resume_ProductManager.pdf\n```\n\n**Avoid:**\n- resume_final_v2_updated_FINAL.docx\n- resume (1).pdf\n- Untitled document.docx\n\n## Output Format\n\nWhen formatting a resume:\n\n```markdown\n# RESUME FORMATTING REVIEW\n\n## Current Issues\n- [ ] [Issue 1]\n- [ ] [Issue 2]\n- [ ] [Issue 3]\n\n## Recommended Changes\n\n### Document Setup\n- Margins: [Current] → [Recommended]\n- Font: [Current] → [Recommended]\n- Font sizes: [Current] → [Recommended]\n\n### Section Order\n**Current:** [Current order]\n**Recommended:** [New order and why]\n\n### Visual Improvements\n- [Specific change 1]\n- [Specific change 2]\n\n### ATS Compatibility Fixes\n- [Fix 1]\n- [Fix 2]\n\n## Before\u002FAfter Preview\n\n### Before:\n[Description or example of current formatting]\n\n### After:\n[Description or example of improved formatting]\n```\n\n## Quick Formatting Checklist\n\nBefore submitting any resume:\n- ✅ One page (or two if warranted)\n- ✅ Standard font (10-12pt body)\n- ✅ Consistent formatting throughout\n- ✅ Clear section headers\n- ✅ Appropriate white space\n- ✅ No tables, text boxes, or columns\n- ✅ Contact info in body (not header)\n- ✅ Saved as .docx or .pdf\n- ✅ Proper file name\n- ✅ Proofread for consistency\n","# Resume Formatter\n\n## When to Use This Skill\n\nUse this skill when the user:\n- Needs help with resume layout and formatting\n- Has a messy or hard-to-read resume\n- Wants to ensure ATS compatibility through formatting\n- Needs a clean, professional design\n- Mentions: \"format resume\", \"resume layout\", \"resume design\", \"clean resume\", \"professional format\"\n\n## Core Capabilities\n\n- Structure resumes for optimal readability\n- Ensure ATS compatibility through formatting\n- Create visual hierarchy\n- Optimize white space and margins\n- Select appropriate fonts and sizes\n- Balance aesthetic appeal with functionality\n\n## Formatting Fundamentals\n\n### The Dual Audience Challenge\n\nYour resume must work for:\n1. **ATS (Applicant Tracking Systems)** - Robots that parse text\n2. **Human Readers** - Recruiters who scan quickly\n\n**The Solution:** Clean, simple formatting that satisfies both.\n\n## Document Setup\n\n### Page Length\n- **Entry Level (0-5 years):** 1 page\n- **Mid-Level (5-15 years):** 1-2 pages\n- **Senior\u002FExecutive (15+ years):** 2 pages (max 3 for executives)\n\n### Margins\n- **Recommended:** 0.5\" - 1\" all sides\n- **Minimum:** 0.5\" (don't go smaller)\n- **Maximum:** 1\" (don't waste space)\n\n### Font Selection\n\n**Safe, ATS-Friendly Fonts:**\n- **Sans-serif:** Arial, Calibri, Helvetica, Verdana\n- **Serif:** Times New Roman, Georgia, Garamond\n\n**Font Sizes:**\n- **Name:** 16-20pt\n- **Section Headers:** 12-14pt\n- **Body Text:** 10-12pt\n- **Minimum readable:** 10pt\n\n### Spacing\n- **Line spacing:** 1.0 to 1.15\n- **Space after paragraphs:** 6-12pt\n- **Section spacing:** 12-16pt between sections\n\n## ATS-Safe Formatting Rules\n\n### DO:\n- ✅ Use standard fonts\n- ✅ Use simple bullet points (•, -, *)\n- ✅ Use bold and italic sparingly\n- ✅ Use standard section headers\n- ✅ Save as .docx or text-based .pdf\n- ✅ Put contact info in body (not header)\n- ✅ Use single column layout\n- ✅ Use consistent formatting throughout\n\n### DON'T:\n- ❌ Use tables (except simple ones for contact info)\n- ❌ Use text boxes\n- ❌ Use columns (multi-column layouts)\n- ❌ Use headers\u002Ffooters for important info\n- ❌ Use images or graphics\n- ❌ Use unusual fonts\n- ❌ Use skill bars or progress indicators\n- ❌ Use special characters or emojis\n- ❌ Use color for essential information\n\n## Section Organization\n\n### Standard Section Order\n\n```\n1. Contact Information\n2. Professional Summary (optional)\n3. Skills\u002FTechnical Skills\n4. Professional Experience\n5. Education\n6. Certifications (if relevant)\n7. Additional (volunteer, languages, etc.)\n```\n\n### Section Header Formatting\n\n**ATS-Recognized Headers:**\n- PROFESSIONAL EXPERIENCE or WORK EXPERIENCE\n- EDUCATION\n- SKILLS or TECHNICAL SKILLS\n- PROFESSIONAL SUMMARY or SUMMARY\n- CERTIFICATIONS\n- PROJECTS\n\n**Format Options:**\n```\nPROFESSIONAL EXPERIENCE\n━━━━━━━━━━━━━━━━━━━━━━\n\nor\n\nProfessional Experience\n_______________________\n\nor\n\nPROFESSIONAL EXPERIENCE\n```\n\n## Contact Information Layout\n\n### Recommended Format\n```\nJOHN SMITH\njohn.smith@email.com | (555) 123-4567 | linkedin.com\u002Fin\u002Fjohnsmith\nSan Francisco, CA\n```\n\n### Alternative Format\n```\nJOHN SMITH\nSan Francisco, CA\njohn.smith@email.com | (555) 123-4567\nLinkedIn: linkedin.com\u002Fin\u002Fjohnsmith | GitHub: github.com\u002Fjohnsmith\n```\n\n### What to Include\n- ✅ Full name\n- ✅ Professional email\n- ✅ Phone number\n- ✅ City, State (no full address needed)\n- ✅ LinkedIn URL\n- ✅ Portfolio\u002FGitHub (if relevant)\n\n### What to Exclude\n- ❌ Full street address\n- ❌ Photo\n- ❌ Date of birth\n- ❌ Marital status\n- ❌ Multiple phone numbers\n- ❌ Personal social media\n\n## Experience Section Formatting\n\n### Standard Format\n```\nCOMPANY NAME | City, ST\nJob Title | Month Year - Month Year\n\n• Achievement bullet with metrics and results\n• Achievement bullet with metrics and results\n• Achievement bullet with metrics and results\n```\n\n### Alternative Format\n```\nJob Title\nCOMPANY NAME, City, ST                    Month Year - Month Year\n\n• Achievement bullet with metrics and results\n• Achievement bullet with metrics and results\n```\n\n### Date Formatting\n- **Consistent format:** Use same format throughout\n- **Recommended:** Month Year (Jan 2020 - Present)\n- **Also acceptable:** MM\u002FYYYY (01\u002F2020 - Present)\n- **Avoid:** Full dates (January 15, 2020)\n\n### Bullet Point Guidelines\n- **Length:** 1-2 lines each\n- **Format:** Start with action verb, end with result\n- **Quantity:** 3-6 bullets per role (more for recent, fewer for old)\n- **Symbol:** Use standard bullets (•, -, *)\n\n## Skills Section Formatting\n\n### Option 1: Simple List\n```\nSKILLS\nPython, JavaScript, SQL, React, Node.js, AWS, Docker, Git, Agile, JIRA\n```\n\n### Option 2: Categorized\n```\nTECHNICAL SKILLS\nLanguages: Python, JavaScript, TypeScript, SQL\nFrameworks: React, Node.js, Django, Flask\nTools: AWS, Docker, Kubernetes, Git, Jenkins\n```\n\n### Option 3: Columns (Careful with ATS)\n```\nSKILLS\nLanguages        Frameworks       Tools\nPython           React            AWS\nJavaScript       Node.js          Docker\nSQL              Django           Git\n```\n\n**Note:** Multi-column layouts may cause ATS issues. Test before using.\n\n## Education Section Formatting\n\n### Standard Format\n```\nEDUCATION\nBachelor of Science in Computer Science\nUniversity of California, Berkeley | 2018\nGPA: 3.8\u002F4.0 (include if 3.5+)\n```\n\n### With Honors\u002FDetails\n```\nEDUCATION\nMBA, Finance & Strategy | Stanford Graduate School of Business | 2020\n• Graduated with Distinction\n• Relevant Coursework: Corporate Finance, M&A Strategy\n```\n\n## Visual Hierarchy Principles\n\n### Hierarchy Order\n1. **Name** - Largest, most prominent\n2. **Section Headers** - Clear divisions\n3. **Job Titles\u002FCompany Names** - Easy to scan\n4. **Bullet Points** - The details\n\n### Creating Hierarchy\n- Use font SIZE to create levels\n- Use **BOLD** for emphasis (names, titles, headers)\n- Use CAPS for section headers\n- Use consistent spacing to separate sections\n\n## White Space Management\n\n### Good White Space:\n- Between sections (clear separation)\n- After headings (visual breathing room)\n- Between bullets (don't cram)\n- Around margins (frame the content)\n\n### Bad White Space:\n- Huge gaps between sections\n- Inconsistent spacing\n- Half-empty pages\n- Excessive margins eating space\n\n## Common Formatting Mistakes\n\n### Mistake 1: Wall of Text\n**Problem:** Dense paragraphs with no bullets\n**Solution:** Use bullet points, keep paragraphs short\n\n### Mistake 2: Inconsistent Formatting\n**Problem:** Different fonts, sizes, or styles throughout\n**Solution:** Pick one format and stick to it\n\n### Mistake 3: Trying to Be Creative\n**Problem:** Fancy designs that break ATS\n**Solution:** Save creativity for portfolio, not resume\n\n### Mistake 4: Too Much Information\n**Problem:** Cramming everything onto one page\n**Solution:** Edit ruthlessly, prioritize relevance\n\n### Mistake 5: Not Enough Information\n**Problem:** Half-page resume with massive margins\n**Solution:** Add detail, reduce margins (to 0.5\")\n\n## File Format Guidelines\n\n### For Online Applications\n- **.docx** - Best for ATS parsing\n- **.pdf** - Good if created from Word (not scanned)\n\n### For Email\u002FDirect Send\n- **.pdf** - Preserves formatting\n\n### File Naming\n```\nFirstName_LastName_Resume.pdf\nJohnSmith_Resume_ProductManager.pdf\n```\n\n**Avoid:**\n- resume_final_v2_updated_FINAL.docx\n- resume (1).pdf\n- Untitled document.docx\n\n## Output Format\n\nWhen formatting a resume:\n\n```markdown\n# RESUME FORMATTING REVIEW\n\n## Current Issues\n- [ ] [Issue 1]\n- [ ] [Issue 2]\n- [ ] [Issue 3]\n\n## Recommended Changes\n\n### Document Setup\n- Margins: [Current] → [Recommended]\n- Font: [Current] → [Recommended]\n- Font sizes: [Current] → [Recommended]\n\n### Section Order\n**Current:** [Current order]\n**Recommended:** [New order and why]\n\n### Visual Improvements\n- [Specific change 1]\n- [Specific change 2]\n\n### ATS Compatibility Fixes\n- [Fix 1]\n- [Fix 2]\n\n## Before\u002FAfter Preview\n\n### Before:\n[Description or example of current formatting]\n\n### After:\n[Description or example of improved formatting]\n```\n\n## Quick Formatting Checklist\n\nBefore submitting any resume:\n- ✅ One page (or two if warranted)\n- ✅ Standard font (10-12pt body)\n- ✅ Consistent formatting throughout\n- ✅ Clear section headers\n- ✅ Appropriate white space\n- ✅ No tables, text boxes, or columns\n- ✅ Contact info in body (not header)\n- ✅ Saved as .docx or .pdf\n- ✅ Proper file name\n- ✅ Proofread for consistency\n",{"name":44,"description":45},"resume-formatter","Ensure ATS-friendly formatting and create clean, scannable layouts. Use when the user mentions resume format, layout, template, design, or fixing formatting issues.","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","app\u002Fseraph_app\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills",0,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph","https:\u002F\u002Fgithub.com\u002FVortex375","2026-11-08 18:46:14",{"source":8,"skillName":44,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add Vortex375\u002Fseraph --skill resume-formatter",{"tool":59,"command":60},"bunx","bunx skills add Vortex375\u002Fseraph --skill resume-formatter",{"tool":62,"command":63},"pnpm","pnpm dlx skills add Vortex375\u002Fseraph --skill resume-formatter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills\u002FSKILL.md",true,[67,73,77,81,85,89],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"agents\u002Fopenai.yaml","REFERENCE","参考文档",152,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fagents\u002Fopenai.yaml",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"domain.md",2033,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fdomain.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"issue-tracker-github.md",3731,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-github.md",{"path":82,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":83,"sourceHtmlUrl":84},"issue-tracker-gitlab.md",3809,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-gitlab.md",{"path":86,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":87,"sourceHtmlUrl":88},"issue-tracker-local.md",1810,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-local.md",{"path":90,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":91,"sourceHtmlUrl":92},"triage-labels.md",1045,"https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Ftriage-labels.md",[94,116,140,162,178,196],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":110,"publishedAt":39},"01M6BYS1QVW7F887EXS5RR34TA","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[100,105],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[111,23,112,113,30,114,115],"writing","writing for agents","when","editing","documents",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":39},"01M6BYRZNREK0C7V6Y43AKDJWW","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fwizard\u002FSKILL.md",[],[118,123,124,125,126,127,128,129,113,130,131,23,132,133,134,135,29,136,30,137,138,139],"provisioning","ci","generate","infrastructure","dashboard","can","running","invoke","party","credentials","human","provisioning infrastructure","migration","only","interactive","Bash","secrets",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":39},"01M6BYRY92S448X31PTG25TCJC","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[142,147,148,149,128,150,24,151,152,153,154,155,28,156,157,158,159,160,161,27],"at","map","agent session","time","shared","more","tickets","as","clear","session","one at a time","work","decision","plan","chunk",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":39},"01M6BYRWXMYWB6PD7E9PAD44M4","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[169,170,171,24,172,173,174,175,176,177],"wait what","wait","re","last","it","pitch","message","stop","land",{"skillNo":179,"name":38,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":39},"01M6BYRTS6JNDYB7BZVAWK7JJ9","Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Ftriage\u002FSKILL.md",[],[38,184,185,186,187,188,189,190,191,192,193,194,24,195],"machine","roles","grill","ready","write","verify","issues","state","move","prs","state machine","briefs",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":202,"publishedAt":39},"01M6BYRRRCDHNXH2YBDTYJPG36","to-tickets","Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).","https:\u002F\u002Fgithub.com\u002FVortex375\u002Fseraph\u002Fblob\u002Fmain\u002Fapp\u002Fseraph_app\u002F.agents\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[203,153,204,205,206,24,207,208,154,209,27,210,160,35,211],"to tickets","spec","links","break","native","ticket","conversation","text","file"]