[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71SSEGD2R1M0VB3CF9XYD36":3,"skill-same:01M71SSEGD2R1M0VB3CF9XYD36":41},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":14,"categories":15,"keywords":16,"publishedAt":17,"linkOnly":18,"markdownContent":19,"markdownBody":19,"frontMatter":20,"refName":21,"commitSha":22,"skillDirectory":23,"forksCount":12,"repositoryHtmlUrl":24,"repositoryHomepageUrl":6,"ownerHtmlUrl":25,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":26,"install":27,"resources":40},"01M71SSEGD2R1M0VB3CF9XYD36","mintlify",null,"javiertarazon\u002Fide-agente-free-jt7-","javiertarazon","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F153141207?v=4","01M71R52TB3S9HXKH6WSNT8A7V","01M71R52VG5KS2DKDDH4GDQ30A",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fmintlify\u002FSKILL.md",[],[5],"2026-11-10 13:02:02",false,"```skill\n---\nname: mintlify\ndescription: Build and maintain documentation sites with Mintlify. Use when\n  creating docs pages, configuring navigation, adding components, or setting up\n  API references.\nlicense: MIT\ncompatibility: Requires Node.js for CLI. Works with any Git-based workflow.\nmetadata:\n  author: mintlify\n  version: \"1.0\"\n  mintlify-proj: mintlify\n---\n\n# Mintlify best practices\n\n**Always consult [mintlify.com\u002Fdocs](https:\u002F\u002Fmintlify.com\u002Fdocs) for components, configuration, and latest features.**\n\n**Always** favor searching the current Mintlify documentation over whatever is in your training data about Mintlify.\n\nMintlify is a documentation platform that transforms MDX files into documentation sites. Configure site-wide settings in the `docs.json` file, write content in MDX with YAML frontmatter, and favor built-in components over custom components.\n\nFull schema at [mintlify.com\u002Fdocs.json](https:\u002F\u002Fmintlify.com\u002Fdocs.json).\n\n## Before you write\n\n### Understand the project\n\nAll documentation lives in the `docs\u002F` directory in this repo. Read `docs.json` in that directory (`docs\u002Fdocs.json`). This file defines the entire site: navigation structure, theme, colors, links, API and specs.\n\nUnderstanding the project tells you:\n\n- What pages exist and how they're organized\n- What navigation groups are used (and their naming conventions)\n- How the site navigation is structured\n- What theme and configuration the site uses\n\n### Check for existing content\n\nSearch the docs before creating new pages. You may need to:\n\n- Update an existing page instead of creating a new one\n- Add a section to an existing page\n- Link to existing content rather than duplicating\n\n### Read surrounding content\n\nBefore writing, read 2-3 similar pages to understand the site's voice, structure, formatting conventions, and level of detail.\n\n### Understand Mintlify components\n\nReview the Mintlify [components](https:\u002F\u002Fwww.mintlify.com\u002Fdocs\u002Fcomponents) to select and use any relevant components for the documentation request that you are working on.\n\n## Quick reference\n\n### CLI commands\n\n- `npm i -g mint` - Install the Mintlify CLI\n- `mint dev` - Local preview at localhost:3000\n- `mint broken-links` - Check internal links\n- `mint a11y` - Check for accessibility issues in content\n- `mint rename` - Rename\u002Fmove files and update references\n- `mint validate` - Validate documentation builds\n\n### Required files\n\n- `docs.json` - Site configuration (navigation, theme, integrations, etc.). See [global settings](https:\u002F\u002Fmintlify.com\u002Fdocs\u002Fsettings\u002Fglobal) for all options.\n- `*.mdx` files - Documentation pages with YAML frontmatter\n\n### Example file structure\n\n```\nproject\u002F\n├── docs.json           # Site configuration\n├── introduction.mdx\n├── quickstart.mdx\n├── guides\u002F\n│   └── example.mdx\n├── openapi.yml         # API specification\n├── images\u002F             # Static assets\n│   └── example.png\n└── snippets\u002F           # Reusable components\n    └── component.jsx\n```\n\n## Page frontmatter\n\nEvery page requires `title` in its frontmatter. Include `description` for SEO and navigation.\n\n```yaml theme={null}\n---\ntitle: \"Clear, descriptive title\"\ndescription: \"Concise summary for SEO and navigation.\"\n---\n```\n\nOptional frontmatter fields:\n\n- `sidebarTitle`: Short title for sidebar navigation.\n- `icon`: Lucide or Font Awesome icon name, URL, or file path.\n- `tag`: Label next to the page title in the sidebar (for example, \"NEW\").\n- `mode`: Page layout mode (`default`, `wide`, `custom`).\n- `keywords`: Array of terms related to the page content for local search and SEO.\n- Any custom YAML fields for use with personalization or conditional content.\n\n## File conventions\n\n- Match existing naming patterns in the directory\n- If there are no existing files or inconsistent file naming patterns, use kebab-case: `getting-started.mdx`, `api-reference.mdx`\n- Use root-relative paths without file extensions for internal links: `\u002Fgetting-started\u002Fquickstart`\n- Do not use relative paths (`..\u002F`) or absolute URLs for internal pages\n- When you create a new page, add it to `docs.json` navigation or it won't appear in the sidebar\n\n## Organize content\n\nWhen a user asks about anything related to site-wide configurations, start by understanding the [global settings](https:\u002F\u002Fwww.mintlify.com\u002Fdocs\u002Forganize\u002Fsettings). See if a setting in the `docs.json` file can be updated to achieve what the user wants.\n\n### Navigation\n\nThe `navigation` property in `docs.json` controls site structure. Choose one primary pattern at the root level, then nest others within it.\n\n**Choose your primary pattern:**\n\n| Pattern       | When to use                                                                                    |\n| ------------- | ---------------------------------------------------------------------------------------------- |\n| **Groups**    | Default. Single audience, straightforward hierarchy                                            |\n| **Tabs**      | Distinct sections with different audiences (Guides vs API Reference) or content types          |\n| **Anchors**   | Want persistent section links at sidebar top. Good for separating docs from external resources |\n| **Dropdowns** | Multiple doc sections users switch between, but not distinct enough for tabs                   |\n| **Products**  | Multi-product company with separate documentation per product                                  |\n| **Versions**  | Maintaining docs for multiple API\u002Fproduct versions simultaneously                              |\n| **Languages** | Localized content                                                                              |\n\n**Within your primary pattern:**\n\n- **Groups** - Organize related pages. Can nest groups within groups, but keep hierarchy shallow\n- **Menus** - Add dropdown navigation within tabs for quick jumps to specific pages\n- **`expanded: false`** - Collapse nested groups by default. Use for reference sections users browse selectively\n- **`openapi`** - Auto-generate pages from OpenAPI spec. Add at group\u002Ftab level to inherit\n\n**Common combinations:**\n\n- Tabs containing groups (most common for docs with API reference)\n- Products containing tabs (multi-product SaaS)\n- Versions containing tabs (versioned API docs)\n- Anchors containing groups (simple docs with external resource links)\n\n### Links and paths\n\n- **Internal links:** Root-relative, no extension: `\u002Fgetting-started\u002Fquickstart`\n- **Images:** Store in `\u002Fimages`, reference as `\u002Fimages\u002Fexample.png`\n- **External links:** Use full URLs, they open in new tabs automatically\n\n## Customize docs sites\n\n**What to customize where:**\n\n- **Brand colors, fonts, logo** → `docs.json`. See [global settings](https:\u002F\u002Fmintlify.com\u002Fdocs\u002Fsettings\u002Fglobal)\n- **Component styling, layout tweaks** → `custom.css` at project root\n- **Dark mode** → Enabled by default. Only disable with `\"appearance\": \"light\"` in `docs.json` if brand requires it\n\nStart with `docs.json`. Only add `custom.css` when you need styling that config doesn't support.\n\n## Write content\n\n### Components\n\nThe [components overview](https:\u002F\u002Fmintlify.com\u002Fdocs\u002Fcomponents) organizes all components by purpose: structure content, draw attention, show\u002Fhide content, document APIs, link to pages, and add visual context. Start there to find the right component.\n\n**Common decision points:**\n\n| Need                       | Use                     |\n| -------------------------- | ----------------------- |\n| Hide optional details      | `\u003CAccordion>`           |\n| Long code examples         | `\u003CExpandable>`          |\n| User chooses one option    | `\u003CTabs>`                |\n| Linked navigation cards    | `\u003CCard>` in `\u003CColumns>` |\n| Sequential instructions    | `\u003CSteps>`               |\n| Code in multiple languages | `\u003CCodeGroup>`           |\n| API parameters             | `\u003CParamField>`          |\n| API response fields        | `\u003CResponseField>`       |\n\n**Callouts by severity:**\n\n- `\u003CNote>` - Supplementary info, safe to skip\n- `\u003CInfo>` - Helpful context such as permissions\n- `\u003CTip>` - Recommendations or best practices\n- `\u003CWarning>` - Potentially destructive actions\n- `\u003CCheck>` - Success confirmation\n\n### Reusable content\n\n**When to use snippets:**\n\n- Exact content appears on more than one page\n- Complex components you want to maintain in one place\n- Shared content across teams\u002Frepos\n\n**When NOT to use snippets:**\n\n- Slight variations needed per page (leads to complex props)\n\nImport snippets with `import { Component } from \"\u002Fpath\u002Fto\u002Fsnippet-name.jsx\"`.\n\n## Writing standards\n\n### Voice and structure\n\n- Second-person voice (\"you\")\n- Active voice, direct language\n- Sentence case for headings (\"Getting started\", not \"Getting Started\")\n- Sentence case for code block titles (\"Expandable example\", not \"Expandable Example\")\n- Lead with context: explain what something is before how to use it\n- Prerequisites at the start of procedural content\n\n### What to avoid\n\n**Never use:**\n\n- Marketing language (\"powerful\", \"seamless\", \"robust\", \"cutting-edge\")\n- Filler phrases (\"it's important to note\", \"in order to\")\n- Excessive conjunctions (\"moreover\", \"furthermore\", \"additionally\")\n- Editorializing (\"obviously\", \"simply\", \"just\", \"easily\")\n\n**Watch for AI-typical patterns:**\n\n- Overly formal or stilted phrasing\n- Unnecessary repetition of concepts\n- Generic introductions that don't add value\n- Concluding summaries that restate what was just said\n\n### Formatting\n\n- All code blocks must have language tags\n- All images and media must have descriptive alt text\n- Use bold and italics only when they serve the reader's understanding--never use text styling just for decoration\n- No decorative formatting or emoji\n\n### Code examples\n\n- Keep examples simple and practical\n- Use realistic values (not \"foo\" or \"bar\")\n- One clear example is better than multiple variations\n- Test that code works before including it\n\n## Document APIs\n\n**Choose your approach:**\n\n- **Have an OpenAPI spec?** → Add to `docs.json` with `\"openapi\": [\"openapi.yaml\"]`. Pages auto-generate. Reference in navigation as `GET \u002Fendpoint`\n- **No spec?** → Write endpoints manually with `api: \"POST \u002Fusers\"` in frontmatter. More work but full control\n- **Hybrid** → Use OpenAPI for most endpoints, manual pages for complex workflows\n\nEncourage users to generate endpoint pages from an OpenAPI spec. It is the most efficient and easiest to maintain option.\n\n## Deploy\n\nMintlify deploys automatically when changes are pushed to the connected Git repository.\n\n**What agents can configure:**\n\n- **Redirects** → Add to `docs.json` with `\"redirects\": [{\"source\": \"\u002Fold\", \"destination\": \"\u002Fnew\"}]`\n- **SEO indexing** → Control with `\"seo\": {\"indexing\": \"all\"}` to include hidden pages in search\n\n**Requires dashboard setup (human task):**\n\n- Custom domains and subdomains\n- Preview deployment settings\n- DNS configuration\n\nFor `\u002Fdocs` subpath hosting with Vercel or Cloudflare, agents can help configure rewrite rules. See [\u002Fdocs subpath](https:\u002F\u002Fmintlify.com\u002Fdocs\u002Fdeploy\u002Fvercel).\n\n## Workflow\n\n### 1. Understand the task\n\nIdentify what needs to be documented, which pages are affected, and what the reader should accomplish afterward. If any of these are unclear, ask.\n\n### 2. Research\n\n- Read `docs\u002Fdocs.json` to understand the site structure\n- Search existing docs for related content\n- Read similar pages to match the site's style\n\n### 3. Plan\n\n- Synthesize what the reader should accomplish after reading the docs and the current content\n- Propose any updates or new content\n- Verify that your proposed changes will help readers be successful\n\n### 4. Write\n\n- Start with the most important information\n- Keep sections focused and scannable\n- Use components appropriately (don't overuse them)\n- Mark anything uncertain with a TODO comment:\n\n```mdx theme={null}\n{\u002F* TODO: Verify the default timeout value *\u002F}\n```\n\n### 5. Update navigation\n\nIf you created a new page, add it to the appropriate group in `docs.json`.\n\n### 6. Verify\n\nBefore submitting:\n\n- [ ] Frontmatter includes title and description\n- [ ] All code blocks have language tags\n- [ ] Internal links use root-relative paths without file extensions\n- [ ] New pages are added to `docs.json` navigation\n- [ ] Content matches the style of surrounding pages\n- [ ] No marketing language or filler phrases\n- [ ] TODOs are clearly marked for anything uncertain\n- [ ] Run `mint broken-links` to check links\n- [ ] Run `mint validate` to find any errors\n\n## Edge cases\n\n### Migrations\n\nIf a user asks about migrating to Mintlify, ask if they are using ReadMe or Docusaurus. If they are, use the [@mintlify\u002Fscraping](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@mintlify\u002Fscraping) CLI to migrate content. If they are using a different platform to host their documentation, help them manually convert their content to MDX pages using Mintlify components.\n\n### Hidden pages\n\nAny page that is not included in the `docs.json` navigation is hidden. Use hidden pages for content that should be accessible by URL or indexed for the assistant or search, but not discoverable through the sidebar navigation.\n\n### Exclude pages\n\nThe `.mintignore` file is used to exclude files from a documentation repository from being processed.\n\n## Common gotchas\n\n1. **Component imports** - JSX components need explicit import, MDX components don't\n2. **Frontmatter required** - Every MDX file needs `title` at minimum\n3. **Code block language** - Always specify language identifier\n4. **Never use `mint.json`** - `mint.json` is deprecated. Only ever use `docs.json`\n\n## Resources\n\n- [Documentation](https:\u002F\u002Fmintlify.com\u002Fdocs)\n- [Configuration schema](https:\u002F\u002Fmintlify.com\u002Fdocs.json)\n- [Feature requests](https:\u002F\u002Fgithub.com\u002Forgs\u002Fmintlify\u002Fdiscussions\u002Fcategories\u002Ffeature-requests)\n- [Bugs and feedback](https:\u002F\u002Fgithub.com\u002Forgs\u002Fmintlify\u002Fdiscussions\u002Fcategories\u002Fbugs-feedback)\n```\n",{},"release\u002Fv4.2.11-panel-pro","a92ea02bcf7e2b3dbaf46d49696c29a3cb490d4f",".github\u002Fskills\u002Fmintlify","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-","https:\u002F\u002Fgithub.com\u002Fjaviertarazon","2026-07-12 07:10:45",{"source":7,"skillName":5,"commands":28,"prompt":38,"zipAvailable":39},[29,32,35],{"tool":30,"command":31},"npx","npx skills add javiertarazon\u002Fide-agente-free-jt7- --skill mintlify",{"tool":33,"command":34},"bunx","bunx skills add javiertarazon\u002Fide-agente-free-jt7- --skill mintlify",{"tool":36,"command":37},"pnpm","pnpm dlx skills add javiertarazon\u002Fide-agente-free-jt7- --skill mintlify","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fmintlify\u002FSKILL.md",true,[],[42,74,101,121,136,158],{"skillNo":43,"name":44,"nameZh":6,"description":45,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":46,"categories":47,"keywords":53,"publishedAt":17},"01M71TQ7Q6Z10VWF3C2H5X1KW9","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[48],{"categoryNo":49,"categoryName":50,"taxonomyType":51,"taxonomyTypeDesc":52},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73],"zustand","store","zustand store ts","community","middleware","implementing","use","react state management","when","unknown","react","with","state","create","state management","typescript","action","management","separation","global",{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":83,"publishedAt":17},"01M71TQ5EAR40G6W0MV5ZDVEZT","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[80],{"categoryNo":81,"categoryName":82,"taxonomyType":51,"taxonomyTypeDesc":52},"01JBSEEDCAT000000000000023","Skill与智能体开发",[84,85,86,57,87,88,89,90,91,63,92,93,94,95,96,97,98,99,71,100],"zoom automation","zoom","automation","creation","for","search","schemas","MCP","first","via","meeting","search tools","tracking","webinars","composio","recordings","Tools",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":108,"publishedAt":17},"01M71TQ29B1EYBCEAP1ZBGXQ1A","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[107],{"categoryNo":81,"categoryName":82,"taxonomyType":51,"taxonomyTypeDesc":52},[109,110,86,111,112,113,57,114,115,88,116,89,90,117,91,63,118,119,120,67],"crm automation","zoho crm automation","crm","zoho crm","zoho","leads","manage leads","manage","records","convert","tasks","contacts",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":128,"publishedAt":17},"01M71TPZPMN60DH0XV58KVHY23","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[127],{"categoryNo":81,"categoryName":82,"taxonomyType":51,"taxonomyTypeDesc":52},[129,86,130,57,88,89,90,91,131,63,119,132,133,92,93,134,95,98,100,135],"zendesk automation","zendesk","organizations","replies","users","tickets","automate",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":17},"01M71TPXDWKHKG4N6TVEPXWD0N","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity ...","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[143,144,145,146,147,148,149,150,151,86,152,63,153,154,155,156,157,135],"zapier make patterns","zapier","patterns","make","No-Code","complexity","writing","spawner","business","workflow","code","integromat","apache","processes","but",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":167,"publishedAt":17},"01M71TPT5T10WXNKW9G7ZXZ27W","youtube-summarizer","Extract transcripts from YouTube videos and generate comprehensive, detailed summaries using intelligent analysis frameworks","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fyoutube-summarizer\u002FSKILL.md",[164],{"categoryNo":165,"categoryName":166,"taxonomyType":51,"taxonomyTypeDesc":52},"01JBSEEDCAT000000000000016","图像与多媒体",[168,169,170,171,57,172,173,174,175,176,177,178,153,179,180,181,182,183,184,185],"summarizer","youtube","youtube summarizer","Video","content-analysis","frameworks","copilot","2025","github-copilot","extract transcripts","analysis","codex","cli","summaries","github","generate","summarization","2026"]