[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75KBAPP5H8P72TFN7SJ1DPD":3,"skill-same:01M75KBAPP5H8P72TFN7SJ1DPD":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75KBAPP5H8P72TFN7SJ1DPD","update-skill",null,"Create or update skills by generating, editing, or refining SKILL.md files in this repository. Use when authoring new skills or revising the structure, frontmatter, or guidance for existing ones.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fupdate-skill\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: update-skill\ndescription: Create or update skills by generating, editing, or refining SKILL.md files in this repository. Use when authoring new skills or revising the structure, frontmatter, or guidance for existing ones.\n---\n\n# update-skill\n\nThis guide provides instructions for creating or updating skills in this repository. It covers the required structure, frontmatter, and best practices for skills.\n\n## Quick Start\n\nEvery skill is a directory containing a `SKILL.md` file with YAML frontmatter and markdown body:\n\n```markdown\n---\nname: pdf-processing\ndescription: Extract text and tables from PDF files, fill forms, merge documents.\n---\n\n# PDF Processing\n\n## When to use this skill\nUse this skill when the user needs to work with PDF files...\n\n## How to extract text\n1. Use pdfplumber for text extraction...\n\n## How to fill forms\n...\n```\n\n## Requirements\n\n### Frontmatter (Required)\n\nEvery SKILL.md must start with YAML frontmatter containing:\n\n- **name**: Kebab-case identifier (lowercase letters, numbers, hyphens only)\n  - Example: `add-feature-flag`, `pdf-processing`, `update-skill`\n- **description**: Specific description of what the skill does and when to use it\n  - Must be non-empty\n  - Should include key terms for skill discovery\n  - Begin with an action verb to clearly state what the skill accomplishes (e.g., \"Adds feature flags...\" instead of \"Helps with features...\"), and immediately follow with a specific use case or context (e.g., \"Use when working with feature flags\")\n  - Write in third person (e.g., \"Adds feature flags...\" not \"I can help you add...\")\n\n### Writing Effective Descriptions\n\nThe description field is critical for skill discovery. Include both **what** the skill does and **when** to use it. Some good examples:\n\n- `git-commit`: \"Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.\"\n- `pdf-processing`: \"Extract text and tables from PDF files, fill forms, merge documents. Use when working with PDF files or when the user mentions PDFs, forms, or document extraction.\"\n\nAvoid vague descriptions like \"Helps with code\" or \"Does development tasks\". For more context, see \"Description Best Practices\" in [references\u002Fbest-practices.md](references\u002Fbest-practices.md).\n\n### Skill Structure\n\nTypical sections in Warp skills:\n\n1. **Title and brief summary** – Clear title and a concise overview of the skill's purpose and primary use cases. Link to sections, reference files or related skills if useful\n2. **Overview** - Context about the skill's purpose (optional but common), extends the summary with more details and context\n3. **Main content** - Steps, usage instructions, or workflow guidance\n4. **Best Practices** - Guidelines and recommendations (optional)\n5. **Examples \u002F Reference PRs** - Links to real examples (optional)\n\nKeep the structure flexible based on the skill's needs. Simple skills can omit the optional sections.\n\n### Validation\n\nOptionally, use the [skills-ref](https:\u002F\u002Fgithub.com\u002Fagentskills\u002Fagentskills\u002Ftree\u002Fmain\u002Fskills-ref) reference library to validate your skills:\n\n```bash\nskills-ref validate .\u002Fmy-skill\n```\n\nThis checks that your SKILL.md frontmatter is valid and follows all naming conventions. If not installed, use the WebSearch tool to get context around this package.\n\n### Main Content Best Practices\n\n- For guidance on what qualifies as good main content, see \"Conciseness Principles\" in [references\u002Fbest-practices.md](references\u002Fbest-practices.md)\n- When formatting code examples, see \"Code Example Formatting\" in [references\u002Fbest-practices.md](references\u002Fbest-practices.md).\n\n### File Organization\n\n- **Simple skills** (\u003C=200 lines): Keep everything in SKILL.md\n- **Complex skills** (>200 lines): Split detailed content into `references\u002F` subdirectory\n  - Reference files from SKILL.md with clear links\n  - Example: \"See [references\u002Fbest-practices.md](references\u002Fbest-practices.md) for detailed guidance\"\n\n## When to Split Content\n\nCreate `references\u002F` subdirectory when:\n\n- SKILL.md approaches 200+ lines\n- Skill covers multiple domains or workflows that can be loaded independently\n- Detailed reference material would clutter the main instructions\n\nKeep only essential workflow and procedural instructions in SKILL.md. Move detailed reference material, schemas, and extensive examples to `references\u002F` files.\n\n## Examples from Existing Skills\n\nFor reference on structure and style:\n\n- `.agents\u002Fskills\u002Fadd-feature-flag\u002FSKILL.md` - Multi-step workflow with clear sequential steps\n- `.agents\u002Fskills\u002Fremove-feature-flag\u002FSKILL.md` - Cleanup workflow with search commands\n\n## Best Practices\n\nSee [references\u002Fbest-practices.md](references\u002Fbest-practices.md) for detailed authoring guidance including:\n\n- Progressive disclosure patterns\n- Writing concise, effective instructions\n- Code example formatting\n- Common anti-patterns to avoid\n","# update-skill\n\nThis guide provides instructions for creating or updating skills in this repository. It covers the required structure, frontmatter, and best practices for skills.\n\n## Quick Start\n\nEvery skill is a directory containing a `SKILL.md` file with YAML frontmatter and markdown body:\n\n```markdown\n---\nname: pdf-processing\ndescription: Extract text and tables from PDF files, fill forms, merge documents.\n---\n\n# PDF Processing\n\n## When to use this skill\nUse this skill when the user needs to work with PDF files...\n\n## How to extract text\n1. Use pdfplumber for text extraction...\n\n## How to fill forms\n...\n```\n\n## Requirements\n\n### Frontmatter (Required)\n\nEvery SKILL.md must start with YAML frontmatter containing:\n\n- **name**: Kebab-case identifier (lowercase letters, numbers, hyphens only)\n  - Example: `add-feature-flag`, `pdf-processing`, `update-skill`\n- **description**: Specific description of what the skill does and when to use it\n  - Must be non-empty\n  - Should include key terms for skill discovery\n  - Begin with an action verb to clearly state what the skill accomplishes (e.g., \"Adds feature flags...\" instead of \"Helps with features...\"), and immediately follow with a specific use case or context (e.g., \"Use when working with feature flags\")\n  - Write in third person (e.g., \"Adds feature flags...\" not \"I can help you add...\")\n\n### Writing Effective Descriptions\n\nThe description field is critical for skill discovery. Include both **what** the skill does and **when** to use it. Some good examples:\n\n- `git-commit`: \"Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.\"\n- `pdf-processing`: \"Extract text and tables from PDF files, fill forms, merge documents. Use when working with PDF files or when the user mentions PDFs, forms, or document extraction.\"\n\nAvoid vague descriptions like \"Helps with code\" or \"Does development tasks\". For more context, see \"Description Best Practices\" in [references\u002Fbest-practices.md](references\u002Fbest-practices.md).\n\n### Skill Structure\n\nTypical sections in Warp skills:\n\n1. **Title and brief summary** – Clear title and a concise overview of the skill's purpose and primary use cases. Link to sections, reference files or related skills if useful\n2. **Overview** - Context about the skill's purpose (optional but common), extends the summary with more details and context\n3. **Main content** - Steps, usage instructions, or workflow guidance\n4. **Best Practices** - Guidelines and recommendations (optional)\n5. **Examples \u002F Reference PRs** - Links to real examples (optional)\n\nKeep the structure flexible based on the skill's needs. Simple skills can omit the optional sections.\n\n### Validation\n\nOptionally, use the [skills-ref](https:\u002F\u002Fgithub.com\u002Fagentskills\u002Fagentskills\u002Ftree\u002Fmain\u002Fskills-ref) reference library to validate your skills:\n\n```bash\nskills-ref validate .\u002Fmy-skill\n```\n\nThis checks that your SKILL.md frontmatter is valid and follows all naming conventions. If not installed, use the WebSearch tool to get context around this package.\n\n### Main Content Best Practices\n\n- For guidance on what qualifies as good main content, see \"Conciseness Principles\" in [references\u002Fbest-practices.md](references\u002Fbest-practices.md)\n- When formatting code examples, see \"Code Example Formatting\" in [references\u002Fbest-practices.md](references\u002Fbest-practices.md).\n\n### File Organization\n\n- **Simple skills** (\u003C=200 lines): Keep everything in SKILL.md\n- **Complex skills** (>200 lines): Split detailed content into `references\u002F` subdirectory\n  - Reference files from SKILL.md with clear links\n  - Example: \"See [references\u002Fbest-practices.md](references\u002Fbest-practices.md) for detailed guidance\"\n\n## When to Split Content\n\nCreate `references\u002F` subdirectory when:\n\n- SKILL.md approaches 200+ lines\n- Skill covers multiple domains or workflows that can be loaded independently\n- Detailed reference material would clutter the main instructions\n\nKeep only essential workflow and procedural instructions in SKILL.md. Move detailed reference material, schemas, and extensive examples to `references\u002F` files.\n\n## Examples from Existing Skills\n\nFor reference on structure and style:\n\n- `.agents\u002Fskills\u002Fadd-feature-flag\u002FSKILL.md` - Multi-step workflow with clear sequential steps\n- `.agents\u002Fskills\u002Fremove-feature-flag\u002FSKILL.md` - Cleanup workflow with search commands\n\n## Best Practices\n\nSee [references\u002Fbest-practices.md](references\u002Fbest-practices.md) for detailed authoring guidance including:\n\n- Progressive disclosure patterns\n- Writing concise, effective instructions\n- Code example formatting\n- Common anti-patterns to avoid\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fupdate-skill",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill update-skill",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill update-skill",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill update-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fupdate-skill\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fbest-practices.md","REFERENCE","参考文档",7883,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fupdate-skill\u002Freferences\u002Fbest-practices.md",[53,60,67,76,83,90],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":71,"licenseFileUrl":72,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]