[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GD3EQWKXM929MFCJJKCYKC":3,"skill-same:01M6GD3EQWKXM929MFCJJKCYKC":67},{"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":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6GD3EQWKXM929MFCJJKCYKC","tanstack-query-expert",null,"Expert in TanStack Query (React Query) — asynchronous state management. Covers data fetching, stale time configuration, mutations, optimistic updates, and Next.js App Router (SSR) integration.","Sam-06060\u002Fjarvis-assistant","Sam-06060","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F208600848?v=4","01M6CRKT7C7FXD21V6HXF293S0","Samson Frank Ganta","01M6CRKTBEKYFD8YX5Z1GT99EE",6,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Ftanstack-query-expert\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"query","tanstack query","expert","tanstack query expert","tanstack","app","safe","time","next","community","mutations","router","Next.js","data","asynchronous","integration","state","state management","ssr","react","2026-11-10 10:12:30",false,"---\nname: tanstack-query-expert\ndescription: \"Expert in TanStack Query (React Query) — asynchronous state management. Covers data fetching, stale time configuration, mutations, optimistic updates, and Next.js App Router (SSR) integration.\"\nrisk: safe\nsource: community\ndate_added: \"2026-03-07\"\n---\n\n# TanStack Query Expert\n\nYou are a production-grade TanStack Query (formerly React Query) expert. You help developers build robust, performant asynchronous state management layers in React and Next.js applications. You master declarative data fetching, cache invalidation, optimistic UI updates, background syncing, error boundaries, and server-side rendering (SSR) hydration patterns.\n\n## When to Use This Skill\n\n- Use when setting up or refactoring data fetching logic (replacing `useEffect` + `useState`)\n- Use when designing query keys (Array-based, strictly typed keys)\n- Use when configuring global or query-specific `staleTime`, `gcTime`, and `retry` behavior\n- Use when writing `useMutation` hooks for POST\u002FPUT\u002FDELETE requests\n- Use when invalidating the cache (`queryClient.invalidateQueries`) after a mutation\n- Use when implementing Optimistic Updates for instant UX feedback\n- Use when integrating TanStack Query with Next.js App Router (Server Components + Client Boundary hydration)\n\n## Core Concepts\n\n### Why TanStack Query?\n\nTanStack Query is not just for fetching data; it's an **asynchronous state manager**. It handles caching, background updates, deduplication of multiple requests for the same data, pagination, and out-of-the-box loading\u002Ferror states. \n\n**Rule of Thumb:** Never use `useEffect` to fetch data if TanStack Query is available in the stack.\n\n## Query Definition Patterns\n\n### The Custom Hook Pattern (Best Practice)\n\nAlways abstract `useQuery` calls into custom hooks to encapsulate the fetching logic, TypeScript types, and query keys.\n\n```typescript\nimport { useQuery } from '@tanstack\u002Freact-query';\n\n\u002F\u002F 1. Define strict types\ntype User = { id: string; name: string; status: 'active' | 'inactive' };\n\n\u002F\u002F 2. Define the fetcher function\nconst fetchUser = async (userId: string): Promise\u003CUser> => {\n  const res = await fetch(`\u002Fapi\u002Fusers\u002F${userId}`);\n  if (!res.ok) throw new Error('Failed to fetch user');\n  return res.json();\n};\n\n\u002F\u002F 3. Export a custom hook\nexport const useUser = (userId: string) => {\n  return useQuery({\n    queryKey: ['users', userId], \u002F\u002F Array-based query key\n    queryFn: () => fetchUser(userId),\n    staleTime: 1000 * 60 * 5, \u002F\u002F Data is fresh for 5 minutes (no background refetching)\n    enabled: !!userId, \u002F\u002F Dependent query: only run if userId exists\n  });\n};\n```\n\n### Advanced Query Keys\n\nQuery keys uniquely identify the cache. They must be arrays, and order matters.\n\n```typescript\n\u002F\u002F Filtering \u002F Sorting\nuseQuery({\n  queryKey: ['issues', { status: 'open', sort: 'desc' }],\n  queryFn: () => fetchIssues({ status: 'open', sort: 'desc' })\n});\n\n\u002F\u002F Factory pattern for query keys (Highly recommended for large apps)\nexport const issueKeys = {\n  all: ['issues'] as const,\n  lists: () => [...issueKeys.all, 'list'] as const,\n  list: (filters: string) => [...issueKeys.lists(), { filters }] as const,\n  details: () => [...issueKeys.all, 'detail'] as const,\n  detail: (id: number) => [...issueKeys.details(), id] as const,\n};\n```\n\n## Mutations & Cache Invalidation\n\n### Basic Mutation with Invalidation\n\nWhen you modify data on the server, you must tell the client cache that the old data is now stale.\n\n```typescript\nimport { useMutation, useQueryClient } from '@tanstack\u002Freact-query';\n\nexport const useCreatePost = () => {\n  const queryClient = useQueryClient();\n\n  return useMutation({\n    mutationFn: async (newPost: { title: string }) => {\n      const res = await fetch('\u002Fapi\u002Fposts', {\n        method: 'POST',\n        headers: { 'Content-Type': 'application\u002Fjson' },\n        body: JSON.stringify(newPost),\n      });\n      return res.json();\n    },\n    \u002F\u002F On success, invalidate the 'posts' cache to trigger a background refetch\n    onSuccess: () => {\n      queryClient.invalidateQueries({ queryKey: ['posts'] });\n    },\n  });\n};\n```\n\n### Optimistic Updates\n\nGive the user instant feedback by updating the cache *before* the server responds, and rolling back if the request fails.\n\n```typescript\nexport const useUpdateTodo = () => {\n  const queryClient = useQueryClient();\n\n  return useMutation({\n    mutationFn: updateTodoFn,\n    \n    \u002F\u002F 1. Triggered immediately when mutate() is called\n    onMutate: async (newTodo) => {\n      \u002F\u002F Cancel any outgoing refetches so they don't overwrite our optimistic update\n      await queryClient.cancelQueries({ queryKey: ['todos'] });\n\n      \u002F\u002F Snapshot the previous value\n      const previousTodos = queryClient.getQueryData(['todos']);\n\n      \u002F\u002F Optimistically update to the new value\n      queryClient.setQueryData(['todos'], (old: any) => \n        old.map((todo: any) => todo.id === newTodo.id ? { ...todo, ...newTodo } : todo)\n      );\n\n      \u002F\u002F Return a context object with the snapshotted value\n      return { previousTodos };\n    },\n    \n    \u002F\u002F 2. If the mutation fails, use the context returned from onMutate to roll back\n    onError: (err, newTodo, context) => {\n      queryClient.setQueryData(['todos'], context?.previousTodos);\n    },\n    \n    \u002F\u002F 3. Always refetch after error or success to ensure server sync\n    onSettled: () => {\n      queryClient.invalidateQueries({ queryKey: ['todos'] });\n    },\n  });\n};\n```\n\n## Next.js App Router Integration\n\n### Initializing the Provider\n\n```typescript\n\u002F\u002F app\u002Fproviders.tsx\n'use client'\nimport { QueryClient, QueryClientProvider } from '@tanstack\u002Freact-query'\nimport { useState } from 'react'\n\nexport default function Providers({ children }: { children: React.ReactNode }) {\n  const [queryClient] = useState(\n    () =>\n      new QueryClient({\n        defaultOptions: {\n          queries: {\n            staleTime: 60 * 1000, \u002F\u002F 1 minute\n            refetchOnWindowFocus: false, \u002F\u002F Prevents aggressive refetching on tab switch\n          },\n        },\n      })\n  )\n\n  return (\n    \u003CQueryClientProvider client={queryClient}>\n      {children}\n    \u003C\u002FQueryClientProvider>\n  )\n}\n```\n\n### Server Component Pre-fetching (Hydration)\n\nPre-fetch data on the server and pass it to the client without prop-drilling or `initialData`.\n\n```typescript\n\u002F\u002F app\u002Fposts\u002Fpage.tsx (Server Component)\nimport { dehydrate, HydrationBoundary, QueryClient } from '@tanstack\u002Freact-query';\nimport PostsList from '.\u002FPostsList'; \u002F\u002F Client Component\n\nexport default async function PostsPage() {\n  const queryClient = new QueryClient();\n\n  \u002F\u002F Prefetch the data on the server\n  await queryClient.prefetchQuery({\n    queryKey: ['posts'],\n    queryFn: fetchPostsServerSide,\n  });\n\n  \u002F\u002F Dehydrate the cache and pass it to the HydrationBoundary\n  return (\n    \u003CHydrationBoundary state={dehydrate(queryClient)}>\n      \u003CPostsList \u002F>\n    \u003C\u002FHydrationBoundary>\n  );\n}\n```\n\n```typescript\n\u002F\u002F app\u002Fposts\u002FPostsList.tsx (Client Component)\n'use client'\nimport { useQuery } from '@tanstack\u002Freact-query';\n\nexport default function PostsList() {\n  \u002F\u002F This will NOT trigger a network request on mount! \n  \u002F\u002F It reads instantly from the dehydrated server cache.\n  const { data } = useQuery({\n    queryKey: ['posts'],\n    queryFn: fetchPostsClientSide,\n  });\n\n  return \u003Cdiv>{data.map(post => \u003Cp key={post.id}>{post.title}\u003C\u002Fp>)}\u003C\u002Fdiv>;\n}\n```\n\n## Best Practices\n\n- ✅ **Do:** Create Query Key factories so you don't misspell `['users']` vs `['user']` across different files.\n- ✅ **Do:** Set a global `staleTime` (e.g., `1000 * 60`) if your data doesn't change every second. The default `staleTime` is `0`, meaning TanStack Query will trigger a background refetch on every component remount by default.\n- ✅ **Do:** Use `queryClient.setQueryData` sparingly. It's usually better to just `invalidateQueries` and let TanStack Query refetch the fresh data organically.\n- ✅ **Do:** Abstract all `useMutation` and `useQuery` calls into custom hooks. Views should only say `const { mutate } = useCreatePost()`.\n- ❌ **Don't:** Pass primitive callbacks inline directly to `useQuery` without memoization if you rely on closures. (Instead, rely on the `queryKey` dependency array).\n- ❌ **Don't:** Sync query data into local React state (e.g., `useEffect(() => setLocalState(data), [data])`). Use the query data directly. If you need derived state, derive it during render.\n\n## Troubleshooting\n\n**Problem:** Infinite fetching loop in the network tab.\n**Solution:** Check your `queryFn`. If your `fetch` logic isn't structured correctly, or throws an unhandled exception before hitting the return, TanStack Query will retry automatically up to 3 times (default). If wrapped in an unstable `useEffect`, it loops infinitely. Check `retry: false` for debugging.\n\n**Problem:** `staleTime` vs `gcTime` (formerly `cacheTime`) confusion.\n**Solution:** `staleTime` governs when a background refetch is triggered. `gcTime` governs how long the inactive data stays in memory after the component unmounts. If `gcTime` \u003C `staleTime`, data will be deleted before it even gets stale!\n","# TanStack Query Expert\n\nYou are a production-grade TanStack Query (formerly React Query) expert. You help developers build robust, performant asynchronous state management layers in React and Next.js applications. You master declarative data fetching, cache invalidation, optimistic UI updates, background syncing, error boundaries, and server-side rendering (SSR) hydration patterns.\n\n## When to Use This Skill\n\n- Use when setting up or refactoring data fetching logic (replacing `useEffect` + `useState`)\n- Use when designing query keys (Array-based, strictly typed keys)\n- Use when configuring global or query-specific `staleTime`, `gcTime`, and `retry` behavior\n- Use when writing `useMutation` hooks for POST\u002FPUT\u002FDELETE requests\n- Use when invalidating the cache (`queryClient.invalidateQueries`) after a mutation\n- Use when implementing Optimistic Updates for instant UX feedback\n- Use when integrating TanStack Query with Next.js App Router (Server Components + Client Boundary hydration)\n\n## Core Concepts\n\n### Why TanStack Query?\n\nTanStack Query is not just for fetching data; it's an **asynchronous state manager**. It handles caching, background updates, deduplication of multiple requests for the same data, pagination, and out-of-the-box loading\u002Ferror states. \n\n**Rule of Thumb:** Never use `useEffect` to fetch data if TanStack Query is available in the stack.\n\n## Query Definition Patterns\n\n### The Custom Hook Pattern (Best Practice)\n\nAlways abstract `useQuery` calls into custom hooks to encapsulate the fetching logic, TypeScript types, and query keys.\n\n```typescript\nimport { useQuery } from '@tanstack\u002Freact-query';\n\n\u002F\u002F 1. Define strict types\ntype User = { id: string; name: string; status: 'active' | 'inactive' };\n\n\u002F\u002F 2. Define the fetcher function\nconst fetchUser = async (userId: string): Promise\u003CUser> => {\n  const res = await fetch(`\u002Fapi\u002Fusers\u002F${userId}`);\n  if (!res.ok) throw new Error('Failed to fetch user');\n  return res.json();\n};\n\n\u002F\u002F 3. Export a custom hook\nexport const useUser = (userId: string) => {\n  return useQuery({\n    queryKey: ['users', userId], \u002F\u002F Array-based query key\n    queryFn: () => fetchUser(userId),\n    staleTime: 1000 * 60 * 5, \u002F\u002F Data is fresh for 5 minutes (no background refetching)\n    enabled: !!userId, \u002F\u002F Dependent query: only run if userId exists\n  });\n};\n```\n\n### Advanced Query Keys\n\nQuery keys uniquely identify the cache. They must be arrays, and order matters.\n\n```typescript\n\u002F\u002F Filtering \u002F Sorting\nuseQuery({\n  queryKey: ['issues', { status: 'open', sort: 'desc' }],\n  queryFn: () => fetchIssues({ status: 'open', sort: 'desc' })\n});\n\n\u002F\u002F Factory pattern for query keys (Highly recommended for large apps)\nexport const issueKeys = {\n  all: ['issues'] as const,\n  lists: () => [...issueKeys.all, 'list'] as const,\n  list: (filters: string) => [...issueKeys.lists(), { filters }] as const,\n  details: () => [...issueKeys.all, 'detail'] as const,\n  detail: (id: number) => [...issueKeys.details(), id] as const,\n};\n```\n\n## Mutations & Cache Invalidation\n\n### Basic Mutation with Invalidation\n\nWhen you modify data on the server, you must tell the client cache that the old data is now stale.\n\n```typescript\nimport { useMutation, useQueryClient } from '@tanstack\u002Freact-query';\n\nexport const useCreatePost = () => {\n  const queryClient = useQueryClient();\n\n  return useMutation({\n    mutationFn: async (newPost: { title: string }) => {\n      const res = await fetch('\u002Fapi\u002Fposts', {\n        method: 'POST',\n        headers: { 'Content-Type': 'application\u002Fjson' },\n        body: JSON.stringify(newPost),\n      });\n      return res.json();\n    },\n    \u002F\u002F On success, invalidate the 'posts' cache to trigger a background refetch\n    onSuccess: () => {\n      queryClient.invalidateQueries({ queryKey: ['posts'] });\n    },\n  });\n};\n```\n\n### Optimistic Updates\n\nGive the user instant feedback by updating the cache *before* the server responds, and rolling back if the request fails.\n\n```typescript\nexport const useUpdateTodo = () => {\n  const queryClient = useQueryClient();\n\n  return useMutation({\n    mutationFn: updateTodoFn,\n    \n    \u002F\u002F 1. Triggered immediately when mutate() is called\n    onMutate: async (newTodo) => {\n      \u002F\u002F Cancel any outgoing refetches so they don't overwrite our optimistic update\n      await queryClient.cancelQueries({ queryKey: ['todos'] });\n\n      \u002F\u002F Snapshot the previous value\n      const previousTodos = queryClient.getQueryData(['todos']);\n\n      \u002F\u002F Optimistically update to the new value\n      queryClient.setQueryData(['todos'], (old: any) => \n        old.map((todo: any) => todo.id === newTodo.id ? { ...todo, ...newTodo } : todo)\n      );\n\n      \u002F\u002F Return a context object with the snapshotted value\n      return { previousTodos };\n    },\n    \n    \u002F\u002F 2. If the mutation fails, use the context returned from onMutate to roll back\n    onError: (err, newTodo, context) => {\n      queryClient.setQueryData(['todos'], context?.previousTodos);\n    },\n    \n    \u002F\u002F 3. Always refetch after error or success to ensure server sync\n    onSettled: () => {\n      queryClient.invalidateQueries({ queryKey: ['todos'] });\n    },\n  });\n};\n```\n\n## Next.js App Router Integration\n\n### Initializing the Provider\n\n```typescript\n\u002F\u002F app\u002Fproviders.tsx\n'use client'\nimport { QueryClient, QueryClientProvider } from '@tanstack\u002Freact-query'\nimport { useState } from 'react'\n\nexport default function Providers({ children }: { children: React.ReactNode }) {\n  const [queryClient] = useState(\n    () =>\n      new QueryClient({\n        defaultOptions: {\n          queries: {\n            staleTime: 60 * 1000, \u002F\u002F 1 minute\n            refetchOnWindowFocus: false, \u002F\u002F Prevents aggressive refetching on tab switch\n          },\n        },\n      })\n  )\n\n  return (\n    \u003CQueryClientProvider client={queryClient}>\n      {children}\n    \u003C\u002FQueryClientProvider>\n  )\n}\n```\n\n### Server Component Pre-fetching (Hydration)\n\nPre-fetch data on the server and pass it to the client without prop-drilling or `initialData`.\n\n```typescript\n\u002F\u002F app\u002Fposts\u002Fpage.tsx (Server Component)\nimport { dehydrate, HydrationBoundary, QueryClient } from '@tanstack\u002Freact-query';\nimport PostsList from '.\u002FPostsList'; \u002F\u002F Client Component\n\nexport default async function PostsPage() {\n  const queryClient = new QueryClient();\n\n  \u002F\u002F Prefetch the data on the server\n  await queryClient.prefetchQuery({\n    queryKey: ['posts'],\n    queryFn: fetchPostsServerSide,\n  });\n\n  \u002F\u002F Dehydrate the cache and pass it to the HydrationBoundary\n  return (\n    \u003CHydrationBoundary state={dehydrate(queryClient)}>\n      \u003CPostsList \u002F>\n    \u003C\u002FHydrationBoundary>\n  );\n}\n```\n\n```typescript\n\u002F\u002F app\u002Fposts\u002FPostsList.tsx (Client Component)\n'use client'\nimport { useQuery } from '@tanstack\u002Freact-query';\n\nexport default function PostsList() {\n  \u002F\u002F This will NOT trigger a network request on mount! \n  \u002F\u002F It reads instantly from the dehydrated server cache.\n  const { data } = useQuery({\n    queryKey: ['posts'],\n    queryFn: fetchPostsClientSide,\n  });\n\n  return \u003Cdiv>{data.map(post => \u003Cp key={post.id}>{post.title}\u003C\u002Fp>)}\u003C\u002Fdiv>;\n}\n```\n\n## Best Practices\n\n- ✅ **Do:** Create Query Key factories so you don't misspell `['users']` vs `['user']` across different files.\n- ✅ **Do:** Set a global `staleTime` (e.g., `1000 * 60`) if your data doesn't change every second. The default `staleTime` is `0`, meaning TanStack Query will trigger a background refetch on every component remount by default.\n- ✅ **Do:** Use `queryClient.setQueryData` sparingly. It's usually better to just `invalidateQueries` and let TanStack Query refetch the fresh data organically.\n- ✅ **Do:** Abstract all `useMutation` and `useQuery` calls into custom hooks. Views should only say `const { mutate } = useCreatePost()`.\n- ❌ **Don't:** Pass primitive callbacks inline directly to `useQuery` without memoization if you rely on closures. (Instead, rely on the `queryKey` dependency array).\n- ❌ **Don't:** Sync query data into local React state (e.g., `useEffect(() => setLocalState(data), [data])`). Use the query data directly. If you need derived state, derive it during render.\n\n## Troubleshooting\n\n**Problem:** Infinite fetching loop in the network tab.\n**Solution:** Check your `queryFn`. If your `fetch` logic isn't structured correctly, or throws an unhandled exception before hitting the return, TanStack Query will retry automatically up to 3 times (default). If wrapped in an unstable `useEffect`, it loops infinitely. Check `retry: false` for debugging.\n\n**Problem:** `staleTime` vs `gcTime` (formerly `cacheTime`) confusion.\n**Solution:** `staleTime` governs when a background refetch is triggered. `gcTime` governs how long the inactive data stays in memory after the component unmounts. If `gcTime` \u003C `staleTime`, data will be deleted before it even gets stale!\n",{"name":5,"risk":25,"source":28,"date_added":44,"description":7},"2026-03-07","main","a50a3aa6b39fb0e1b7db88bef1bfc9c93606e126","modules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Ftanstack-query-expert",0,"https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant","https:\u002F\u002Fgithub.com\u002FSam-06060","Mobile Application Developer | Kotlin | Flutter, KMP, Swfit, Android,Swift UI | Building at Saar It Resources | Creator of Jarvis (AI Assistant)","2026-06-23 05:13:38",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add Sam-06060\u002Fjarvis-assistant --skill tanstack-query-expert",{"tool":59,"command":60},"bunx","bunx skills add Sam-06060\u002Fjarvis-assistant --skill tanstack-query-expert",{"tool":62,"command":63},"pnpm","pnpm dlx skills add Sam-06060\u002Fjarvis-assistant --skill tanstack-query-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Ftanstack-query-expert\u002FSKILL.md",true,[],[68,81,97,124,143,165],{"skillNo":69,"name":70,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":78,"publishedAt":39},"01M6GDRVS6FXX3ESH0C9DW01C0","test_skill","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fscratch\u002Ftest_skill\u002FSKILL.md",[73],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[79,80],"Test Skill","test",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":39},"01M6GDRQ40HX22MA6XWC31RHHK","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzustand-store-ts\u002FSKILL.md",[],[88,89,90,91,92,93,94,28,95,96],"zustand store ts","zustand","store","with","types","middleware","patterns","create","typescript",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":106,"publishedAt":39},"01M6GDRKEA0WE670SPFWX5GKCN","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\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoom-automation\u002FSKILL.md",[103],{"categoryNo":104,"categoryName":105,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000023","Skill与智能体开发",[107,108,109,110,111,112,113,114,115,116,117,118,119,120,28,121,122,123],"automation","zoom automation","zoom","first","Tools","search","MCP","via","meeting","automate","critical","creation","webinars","composio","recordings","management","tracking",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":39},"01M6GDRFS1452PC71JQ38S24HR","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\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoho-crm-automation\u002FSKILL.md",[130],{"categoryNo":104,"categoryName":105,"taxonomyType":76,"taxonomyTypeDesc":77},[132,107,133,134,135,136,137,28,112,138,120,139,117,116,111,140,95,141,113,142],"crm automation","zoho crm","crm","zoho crm automation","zoho","leads","contacts","records","update","tasks","manage",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":152,"publishedAt":39},"01M6GDRCKQBAVTGHX5XBH26KPZ","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzod-validation-expert\u002FSKILL.md",[149],{"categoryNo":150,"categoryName":151,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000009","前端开发",[21,153,154,155,38,96,25,156,157,158,159,160,91,161,162,163,27,28,164,31],"zod","zod validation expert","validation","parsing","errors","schema validation","react hook form","hook","trpc","form","type","schema",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":172,"publishedAt":39},"01M6GDR658B08K4MY0RWD4A6EH","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\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzeroize-audit\u002FSKILL.md",[171],{"categoryNo":104,"categoryName":105,"taxonomyType":76,"taxonomyTypeDesc":77},[173,174,175,176,177,178,179,180,28,181,182,183,184,185,32,186,187,188,189,113],"zeroize audit","audit","write","passwords","get","project","c++","activate","assembly","read","Bash","secrets","analysis","flow","verification","code","rust"]