[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K05YVRMTNB2425JDX9RCVG":3,"skill-same:01M6K05YVRMTNB2425JDX9RCVG":83},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":27,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":13,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M6K05YVRMTNB2425JDX9RCVG","update-docs",null,"This skill should be used when the user asks to \"update documentation for my changes\", \"check docs for this PR\", \"what docs need updating\", \"sync docs with code\", \"scaffold docs for this feature\", \"document this feature\", \"review docs completeness\", \"add docs for this change\", \"what documentation is affected\", \"docs impact\", or mentions \"docs\u002F\", \"docs\u002F01-app\", \"docs\u002F02-pages\", \"MDX\", \"documentation update\", \"API reference\", \".mdx files\". Provides guided workflow for updating Next.js documentation based on code changes.","sigitpoerwo\u002Frepoworkspace_zahra","sigitpoerwo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260207224?v=4","01M6K000PB6NA0N6SQ7VFMEAFZ","01M6K000V4N0CEHNPPQA9TNQNX",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsigitpoerwo\u002Frepoworkspace_zahra\u002Fblob\u002Fmain\u002Fskills\u002F01-SIAP-PAKAI\u002Fwriting\u002Fupdate-docs\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"docs","update docs","update","files","my","affected","add","impact","app","check docs","feature","next","change","review","api","code","workflow","pr","documentation","sync","2026-11-10 10:12:30",false,"---\nname: update-docs\ndescription: This skill should be used when the user asks to \"update documentation for my changes\", \"check docs for this PR\", \"what docs need updating\", \"sync docs with code\", \"scaffold docs for this feature\", \"document this feature\", \"review docs completeness\", \"add docs for this change\", \"what documentation is affected\", \"docs impact\", or mentions \"docs\u002F\", \"docs\u002F01-app\", \"docs\u002F02-pages\", \"MDX\", \"documentation update\", \"API reference\", \".mdx files\". Provides guided workflow for updating Next.js documentation based on code changes.\n---\n\n# Next.js Documentation Updater\n\nGuides you through updating Next.js documentation based on code changes on the active branch. Designed for maintainers reviewing PRs for documentation completeness.\n\n## Quick Start\n\n1. **Analyze changes**: Run `git diff canary...HEAD --stat` to see what files changed\n2. **Identify affected docs**: Map changed source files to documentation paths\n3. **Review each doc**: Walk through updates with user confirmation\n4. **Validate**: Run `pnpm lint` to check formatting\n5. **Commit**: Stage documentation changes\n\n## Workflow: Analyze Code Changes\n\n### Step 1: Get the diff\n\n```bash\n# See all changed files on this branch\ngit diff canary...HEAD --stat\n\n# See changes in specific areas\ngit diff canary...HEAD -- packages\u002Fnext\u002Fsrc\u002F\n```\n\n### Step 2: Identify documentation-relevant changes\n\nLook for changes in these areas:\n\n| Source Path                            | Likely Doc Impact           |\n| -------------------------------------- | --------------------------- |\n| `packages\u002Fnext\u002Fsrc\u002Fclient\u002Fcomponents\u002F` | Component API reference     |\n| `packages\u002Fnext\u002Fsrc\u002Fserver\u002F`            | Function API reference      |\n| `packages\u002Fnext\u002Fsrc\u002Fshared\u002Flib\u002F`        | Varies by export            |\n| `packages\u002Fnext\u002Fsrc\u002Fbuild\u002F`             | Configuration or build docs |\n| `packages\u002Fnext\u002Fsrc\u002Flib\u002F`               | Various features            |\n\n### Step 3: Map to documentation files\n\nUse the code-to-docs mapping in `references\u002FCODE-TO-DOCS-MAPPING.md` to find corresponding documentation files.\n\nExample mappings:\n\n- `src\u002Fclient\u002Fcomponents\u002Fimage.tsx` → `docs\u002F01-app\u002F03-api-reference\u002F02-components\u002Fimage.mdx`\n- `src\u002Fserver\u002Fconfig-shared.ts` → `docs\u002F01-app\u002F03-api-reference\u002F05-config\u002F`\n\n## Workflow: Update Existing Documentation\n\n### Step 1: Read the current documentation\n\nBefore making changes, read the existing doc to understand:\n\n- Current structure and sections\n- Frontmatter fields in use\n- Whether it uses `\u003CAppOnly>` \u002F `\u003CPagesOnly>` for router-specific content\n\n### Step 2: Identify what needs updating\n\nCommon updates include:\n\n- **New props\u002Foptions**: Add to the props table and create a section explaining usage\n- **Changed behavior**: Update descriptions and examples\n- **Deprecated features**: Add deprecation notices and migration guidance\n- **New examples**: Add code blocks following conventions\n\n### Step 3: Apply updates with confirmation\n\nFor each change:\n\n1. Show the user what you plan to change\n2. Wait for confirmation before editing\n3. Apply the edit\n4. Move to the next change\n\n### Step 4: Check for shared content\n\nIf the doc uses the `source` field pattern (common for Pages Router docs), the source file is the one to edit. Example:\n\n```yaml\n# docs\u002F02-pages\u002F... file with shared content\n---\nsource: app\u002Fbuilding-your-application\u002Foptimizing\u002Fimages\n---\n```\n\nEdit the App Router source, not the Pages Router file.\n\n### Step 5: Validate changes\n\n```bash\npnpm lint          # Check formatting\npnpm prettier-fix  # Auto-fix formatting issues\n```\n\n## Workflow: Scaffold New Feature Documentation\n\nUse this when adding documentation for entirely new features.\n\n### Step 1: Determine the doc type\n\n| Feature Type        | Doc Location                                        | Template         |\n| ------------------- | --------------------------------------------------- | ---------------- |\n| New component       | `docs\u002F01-app\u002F03-api-reference\u002F02-components\u002F`       | API Reference    |\n| New function        | `docs\u002F01-app\u002F03-api-reference\u002F04-functions\u002F`        | API Reference    |\n| New config option   | `docs\u002F01-app\u002F03-api-reference\u002F05-config\u002F`           | Config Reference |\n| New concept\u002Fguide   | `docs\u002F01-app\u002F02-guides\u002F`                            | Guide            |\n| New file convention | `docs\u002F01-app\u002F03-api-reference\u002F03-file-conventions\u002F` | File Convention  |\n\n### Step 2: Create the file with proper naming\n\n- Use kebab-case: `my-new-feature.mdx`\n- Add numeric prefix if ordering matters: `05-my-new-feature.mdx`\n- Place in the correct directory based on feature type\n\n### Step 3: Use the appropriate template\n\n**API Reference Template:**\n\n```mdx\n---\ntitle: Feature Name\ndescription: Brief description of what this feature does.\n---\n\n{\u002F* The content of this doc is shared between the app and pages router. You can use the `\u003CPagesOnly>Content\u003C\u002FPagesOnly>` component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. *\u002F}\n\nBrief introduction to the feature.\n\n## Reference\n\n### Props\n\n\u003Cdiv style={{ overflowX: 'auto', width: '100%' }}>\n\n| Prop                    | Example            | Type   | Status   |\n| ----------------------- | ------------------ | ------ | -------- |\n| [`propName`](#propname) | `propName=\"value\"` | String | Required |\n\n\u003C\u002Fdiv>\n\n#### `propName`\n\nDescription of the prop.\n\n\\`\\`\\`tsx filename=\"app\u002Fexample.tsx\" switcher\n\u002F\u002F TypeScript example\n\\`\\`\\`\n\n\\`\\`\\`jsx filename=\"app\u002Fexample.js\" switcher\n\u002F\u002F JavaScript example\n\\`\\`\\`\n```\n\n**Guide Template:**\n\n```mdx\n---\ntitle: How to do X in Next.js\nnav_title: X\ndescription: Learn how to implement X in your Next.js application.\n---\n\nIntroduction explaining why this guide is useful.\n\n## Prerequisites\n\nWhat the reader needs to know before starting.\n\n## Step 1: First Step\n\nExplanation and code example.\n\n\\`\\`\\`tsx filename=\"app\u002Fexample.tsx\" switcher\n\u002F\u002F Code example\n\\`\\`\\`\n\n## Step 2: Second Step\n\nContinue with more steps...\n\n## Next Steps\n\nRelated topics to explore.\n```\n\n### Step 4: Add related links\n\nUpdate frontmatter with related documentation:\n\n```yaml\nrelated:\n  title: Next Steps\n  description: Learn more about related features.\n  links:\n    - app\u002Fapi-reference\u002Ffunctions\u002Frelated-function\n    - app\u002Fguides\u002Frelated-guide\n```\n\n## Documentation Conventions\n\nSee `references\u002FDOC-CONVENTIONS.md` for complete formatting rules.\n\n### Quick Reference\n\n**Frontmatter (required):**\n\n```yaml\n---\ntitle: Page Title (2-3 words)\ndescription: One or two sentences describing the page.\n---\n```\n\n**Code blocks:**\n\n```\n\\`\\`\\`tsx filename=\"app\u002Fpage.tsx\" switcher\n\u002F\u002F TypeScript first\n\\`\\`\\`\n\n\\`\\`\\`jsx filename=\"app\u002Fpage.js\" switcher\n\u002F\u002F JavaScript second\n\\`\\`\\`\n```\n\n**Router-specific content:**\n\n```mdx\n\u003CAppOnly>Content only for App Router docs.\u003C\u002FAppOnly>\n\n\u003CPagesOnly>Content only for Pages Router docs.\u003C\u002FPagesOnly>\n```\n\n**Notes:**\n\n```mdx\n> **Good to know**: Single line note.\n\n> **Good to know**:\n>\n> - Multi-line note point 1\n> - Multi-line note point 2\n```\n\n## Validation Checklist\n\nBefore committing documentation changes:\n\n- [ ] Frontmatter has `title` and `description`\n- [ ] Code blocks have `filename` attribute\n- [ ] TypeScript examples use `switcher` with JS variant\n- [ ] Props tables are properly formatted\n- [ ] Related links point to valid paths\n- [ ] `pnpm lint` passes\n- [ ] Changes render correctly (if preview available)\n\n## References\n\n- `references\u002FDOC-CONVENTIONS.md` - Complete frontmatter and formatting rules\n- `references\u002FCODE-TO-DOCS-MAPPING.md` - Source code to documentation mapping\n","# Next.js Documentation Updater\n\nGuides you through updating Next.js documentation based on code changes on the active branch. Designed for maintainers reviewing PRs for documentation completeness.\n\n## Quick Start\n\n1. **Analyze changes**: Run `git diff canary...HEAD --stat` to see what files changed\n2. **Identify affected docs**: Map changed source files to documentation paths\n3. **Review each doc**: Walk through updates with user confirmation\n4. **Validate**: Run `pnpm lint` to check formatting\n5. **Commit**: Stage documentation changes\n\n## Workflow: Analyze Code Changes\n\n### Step 1: Get the diff\n\n```bash\n# See all changed files on this branch\ngit diff canary...HEAD --stat\n\n# See changes in specific areas\ngit diff canary...HEAD -- packages\u002Fnext\u002Fsrc\u002F\n```\n\n### Step 2: Identify documentation-relevant changes\n\nLook for changes in these areas:\n\n| Source Path                            | Likely Doc Impact           |\n| -------------------------------------- | --------------------------- |\n| `packages\u002Fnext\u002Fsrc\u002Fclient\u002Fcomponents\u002F` | Component API reference     |\n| `packages\u002Fnext\u002Fsrc\u002Fserver\u002F`            | Function API reference      |\n| `packages\u002Fnext\u002Fsrc\u002Fshared\u002Flib\u002F`        | Varies by export            |\n| `packages\u002Fnext\u002Fsrc\u002Fbuild\u002F`             | Configuration or build docs |\n| `packages\u002Fnext\u002Fsrc\u002Flib\u002F`               | Various features            |\n\n### Step 3: Map to documentation files\n\nUse the code-to-docs mapping in `references\u002FCODE-TO-DOCS-MAPPING.md` to find corresponding documentation files.\n\nExample mappings:\n\n- `src\u002Fclient\u002Fcomponents\u002Fimage.tsx` → `docs\u002F01-app\u002F03-api-reference\u002F02-components\u002Fimage.mdx`\n- `src\u002Fserver\u002Fconfig-shared.ts` → `docs\u002F01-app\u002F03-api-reference\u002F05-config\u002F`\n\n## Workflow: Update Existing Documentation\n\n### Step 1: Read the current documentation\n\nBefore making changes, read the existing doc to understand:\n\n- Current structure and sections\n- Frontmatter fields in use\n- Whether it uses `\u003CAppOnly>` \u002F `\u003CPagesOnly>` for router-specific content\n\n### Step 2: Identify what needs updating\n\nCommon updates include:\n\n- **New props\u002Foptions**: Add to the props table and create a section explaining usage\n- **Changed behavior**: Update descriptions and examples\n- **Deprecated features**: Add deprecation notices and migration guidance\n- **New examples**: Add code blocks following conventions\n\n### Step 3: Apply updates with confirmation\n\nFor each change:\n\n1. Show the user what you plan to change\n2. Wait for confirmation before editing\n3. Apply the edit\n4. Move to the next change\n\n### Step 4: Check for shared content\n\nIf the doc uses the `source` field pattern (common for Pages Router docs), the source file is the one to edit. Example:\n\n```yaml\n# docs\u002F02-pages\u002F... file with shared content\n---\nsource: app\u002Fbuilding-your-application\u002Foptimizing\u002Fimages\n---\n```\n\nEdit the App Router source, not the Pages Router file.\n\n### Step 5: Validate changes\n\n```bash\npnpm lint          # Check formatting\npnpm prettier-fix  # Auto-fix formatting issues\n```\n\n## Workflow: Scaffold New Feature Documentation\n\nUse this when adding documentation for entirely new features.\n\n### Step 1: Determine the doc type\n\n| Feature Type        | Doc Location                                        | Template         |\n| ------------------- | --------------------------------------------------- | ---------------- |\n| New component       | `docs\u002F01-app\u002F03-api-reference\u002F02-components\u002F`       | API Reference    |\n| New function        | `docs\u002F01-app\u002F03-api-reference\u002F04-functions\u002F`        | API Reference    |\n| New config option   | `docs\u002F01-app\u002F03-api-reference\u002F05-config\u002F`           | Config Reference |\n| New concept\u002Fguide   | `docs\u002F01-app\u002F02-guides\u002F`                            | Guide            |\n| New file convention | `docs\u002F01-app\u002F03-api-reference\u002F03-file-conventions\u002F` | File Convention  |\n\n### Step 2: Create the file with proper naming\n\n- Use kebab-case: `my-new-feature.mdx`\n- Add numeric prefix if ordering matters: `05-my-new-feature.mdx`\n- Place in the correct directory based on feature type\n\n### Step 3: Use the appropriate template\n\n**API Reference Template:**\n\n```mdx\n---\ntitle: Feature Name\ndescription: Brief description of what this feature does.\n---\n\n{\u002F* The content of this doc is shared between the app and pages router. You can use the `\u003CPagesOnly>Content\u003C\u002FPagesOnly>` component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. *\u002F}\n\nBrief introduction to the feature.\n\n## Reference\n\n### Props\n\n\u003Cdiv style={{ overflowX: 'auto', width: '100%' }}>\n\n| Prop                    | Example            | Type   | Status   |\n| ----------------------- | ------------------ | ------ | -------- |\n| [`propName`](#propname) | `propName=\"value\"` | String | Required |\n\n\u003C\u002Fdiv>\n\n#### `propName`\n\nDescription of the prop.\n\n\\`\\`\\`tsx filename=\"app\u002Fexample.tsx\" switcher\n\u002F\u002F TypeScript example\n\\`\\`\\`\n\n\\`\\`\\`jsx filename=\"app\u002Fexample.js\" switcher\n\u002F\u002F JavaScript example\n\\`\\`\\`\n```\n\n**Guide Template:**\n\n```mdx\n---\ntitle: How to do X in Next.js\nnav_title: X\ndescription: Learn how to implement X in your Next.js application.\n---\n\nIntroduction explaining why this guide is useful.\n\n## Prerequisites\n\nWhat the reader needs to know before starting.\n\n## Step 1: First Step\n\nExplanation and code example.\n\n\\`\\`\\`tsx filename=\"app\u002Fexample.tsx\" switcher\n\u002F\u002F Code example\n\\`\\`\\`\n\n## Step 2: Second Step\n\nContinue with more steps...\n\n## Next Steps\n\nRelated topics to explore.\n```\n\n### Step 4: Add related links\n\nUpdate frontmatter with related documentation:\n\n```yaml\nrelated:\n  title: Next Steps\n  description: Learn more about related features.\n  links:\n    - app\u002Fapi-reference\u002Ffunctions\u002Frelated-function\n    - app\u002Fguides\u002Frelated-guide\n```\n\n## Documentation Conventions\n\nSee `references\u002FDOC-CONVENTIONS.md` for complete formatting rules.\n\n### Quick Reference\n\n**Frontmatter (required):**\n\n```yaml\n---\ntitle: Page Title (2-3 words)\ndescription: One or two sentences describing the page.\n---\n```\n\n**Code blocks:**\n\n```\n\\`\\`\\`tsx filename=\"app\u002Fpage.tsx\" switcher\n\u002F\u002F TypeScript first\n\\`\\`\\`\n\n\\`\\`\\`jsx filename=\"app\u002Fpage.js\" switcher\n\u002F\u002F JavaScript second\n\\`\\`\\`\n```\n\n**Router-specific content:**\n\n```mdx\n\u003CAppOnly>Content only for App Router docs.\u003C\u002FAppOnly>\n\n\u003CPagesOnly>Content only for Pages Router docs.\u003C\u002FPagesOnly>\n```\n\n**Notes:**\n\n```mdx\n> **Good to know**: Single line note.\n\n> **Good to know**:\n>\n> - Multi-line note point 1\n> - Multi-line note point 2\n```\n\n## Validation Checklist\n\nBefore committing documentation changes:\n\n- [ ] Frontmatter has `title` and `description`\n- [ ] Code blocks have `filename` attribute\n- [ ] TypeScript examples use `switcher` with JS variant\n- [ ] Props tables are properly formatted\n- [ ] Related links point to valid paths\n- [ ] `pnpm lint` passes\n- [ ] Changes render correctly (if preview available)\n\n## References\n\n- `references\u002FDOC-CONVENTIONS.md` - Complete frontmatter and formatting rules\n- `references\u002FCODE-TO-DOCS-MAPPING.md` - Source code to documentation mapping\n",{"name":5,"description":7},"main","000d804ba753926ec0eca35be68bdb42da72c672","skills\u002F01-SIAP-PAKAI\u002Fwriting\u002Fupdate-docs","https:\u002F\u002Fgithub.com\u002Fsigitpoerwo\u002Frepoworkspace_zahra","https:\u002F\u002Fgithub.com\u002Fsigitpoerwo","2026-04-05 09:27:05",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add sigitpoerwo\u002Frepoworkspace_zahra --skill update-docs",{"tool":65,"command":66},"bunx","bunx skills add sigitpoerwo\u002Frepoworkspace_zahra --skill update-docs",{"tool":68,"command":69},"pnpm","pnpm dlx skills add sigitpoerwo\u002Frepoworkspace_zahra --skill update-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsigitpoerwo\u002Frepoworkspace_zahra\u002Fblob\u002Fmain\u002Fskills\u002F01-SIAP-PAKAI\u002Fwriting\u002Fupdate-docs\u002FSKILL.md",true,[73,79],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002FCODE-TO-DOCS-MAPPING.md","REFERENCE","参考文档",7694,"https:\u002F\u002Fgithub.com\u002Fsigitpoerwo\u002Frepoworkspace_zahra\u002Fblob\u002Fmain\u002Fskills\u002F01-SIAP-PAKAI\u002Fwriting\u002Fupdate-docs\u002Freferences\u002FCODE-TO-DOCS-MAPPING.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002FDOC-CONVENTIONS.md",5807,"https:\u002F\u002Fgithub.com\u002Fsigitpoerwo\u002Frepoworkspace_zahra\u002Fblob\u002Fmain\u002Fskills\u002F01-SIAP-PAKAI\u002Fwriting\u002Fupdate-docs\u002Freferences\u002FDOC-CONVENTIONS.md",[84,119,145,163,174,180],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":100,"publishedAt":48},"01M6K0FJ41XMDT72PK0E3ZJF9P","zahra-workspace-manager","Comprehensive workspace management skill for Zahra Maurita's development environment. Use when managing projects across 8 divisions (Web, App, AI Agent, Bot, Content, Marketing, Research, Business), organizing files, tracking progress, managing memory, or coordinating multi-domain work. Triggers on mentions of workspace organization, project management, division-specific tasks, memory updates, or cross-domain coordination.","https:\u002F\u002Fgithub.com\u002Fsigitpoerwo\u002Frepoworkspace_zahra\u002Fblob\u002Fmain\u002Fskills\u002Fzahra-workspace-manager\u002FSKILL.md",[90,93,96,97],{"categoryNo":91,"categoryName":92,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":94,"categoryName":95,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":98,"categoryName":99,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000035","市场营销",[101,102,103,104,105,106,107,36,108,109,110,31,111,112,113,114,115,116,117,118],"workspace","workspace manager","manager","zahra workspace manager","work","updates","progress","project","across","multi-domain","command","coordination","projects","search","tasks","ai agent","memory","bot",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":126,"publishedAt":48},"01M6K0FBZYXG5M8VBW5R6TPKEP","tinyfish","AI-powered web automation using TinyFish Web Agent. Use when you need to scrape data from websites, automate form filling, extract structured information, or perform any web-based task using natural language instructions. Works with any website including those with JavaScript, dynamic content, and bot protection.","https:\u002F\u002Fgithub.com\u002Fsigitpoerwo\u002Frepoworkspace_zahra\u002Fblob\u002Fmain\u002Fskills\u002F05-CUSTOM-SKILLS\u002Ftinyfish\u002FSKILL.md",[125],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[121,127,128,129,130,131,132,133,134,135,136,137,138,118,139,140,141,142,143,144],"with","natural language","web automation","form","information","scrape","task","language","protection","use","instructions","automate","you","website","web","javascript","automation","data",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":152,"publishedAt":48},"01M6K0F57WDT62QNXTTC6YS34D","tinyfish-openclaw","TinyFish Web Agent integration for OpenClaw. Use this skill to scrape websites, automate web tasks, extract structured data, and perform browser automation using natural language. Works seamlessly with OpenClaw's MCP protocol.","https:\u002F\u002Fgithub.com\u002Fsigitpoerwo\u002Frepoworkspace_zahra\u002Fblob\u002Fmain\u002Fskills\u002F05-CUSTOM-SKILLS\u002Ftinyfish-openclaw\u002FSKILL.md",[151],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[121,153,154,143,155,156,157,141,138,158,127,128,136,132,144,159,160,161,162,115],"openclaw","tinyfish openclaw","structured data","browser automation","MCP","for","integration","mcp protocol","browser","protocol",{"skillNo":164,"name":165,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":173,"publishedAt":48},"01M6K0E9ZWFTG44SK6G2ARS39Z","autoresearchclaw","https:\u002F\u002Fgithub.com\u002Fsigitpoerwo\u002Frepoworkspace_zahra\u002Fblob\u002Fmain\u002Fskills\u002F05-CUSTOM-SKILLS\u002Fautoresearchclaw\u002FSKILL.md",[168,171,172],{"categoryNo":169,"categoryName":170,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":94,"categoryName":95,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[165],{"skillNo":175,"name":176,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":48},"01M6K0E6ZAEJFYDXM4GANCKZY0","researchclaw","https:\u002F\u002Fgithub.com\u002Fsigitpoerwo\u002Frepoworkspace_zahra\u002Fblob\u002Fmain\u002Fskills\u002F05-CUSTOM-SKILLS\u002Fautoresearchclaw\u002F.claude\u002Fskills\u002Fresearchclaw\u002FSKILL.md",[],[176],{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":187,"publishedAt":48},"01M6K0E1B6RZ8T2S7RMWQ6BVWW","academic-research-assistant","Research assistant for management & digital business academics - literature review, paper analysis, citation management, research methodology","https:\u002F\u002Fgithub.com\u002Fsigitpoerwo\u002Frepoworkspace_zahra\u002Fblob\u002Fmain\u002Fskills\u002F05-CUSTOM-SKILLS\u002Facademic-research-assistant\u002FSKILL.md",[186],{"categoryNo":94,"categoryName":95,"taxonomyType":20,"taxonomyTypeDesc":21},[188,189,190,191,192,193,158,194,195,196,197,198,199,200,201,202,203,41],"research assistant","academic research assistant","Academic","assistant","research","paper analysis","literature","paper","Citation","research methodology","business","management","literature review","analysis","citation management","methodology"]