[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-minimax-verification-loop":3,"mdc-qe3681-key":28,"related-org-minimax-verification-loop":349,"related-repo-minimax-verification-loop":552},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":17,"repoUrl":18,"updatedAt":19,"license":20,"forks":21,"topics":22,"repo":23,"sourceUrl":26,"mdContent":27},"verification-loop","enforce claim-to-proof verification workflows","Enforce a claim-to-proof workflow before declaring work complete. Use this Skill when a task involves implementation, debugging, review, or any other work that could be claimed complete without concrete evidence.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"minimax","MiniMax","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fminimax.jpg","MiniMax-AI",[13],{"name":14,"slug":15,"type":16},"QA","qa","tag",5,"https:\u002F\u002Fgithub.com\u002FMiniMax-AI\u002FMiniMax-Code-Plugins","2026-08-18T03:49:41.671661",null,2,[],{"repoUrl":18,"stars":17,"forks":21,"topics":24,"description":25},[],"Community registry and contribution toolkit for MiniMax Code plugins.","https:\u002F\u002Fgithub.com\u002FMiniMax-AI\u002FMiniMax-Code-Plugins\u002Ftree\u002FHEAD\u002Fplugins\u002FHylouis233\u002Fverification-loop\u002Fskills\u002Fverification-loop","---\nname: verification-loop\ndescription: Enforce a claim-to-proof workflow before declaring work complete. Use this Skill when a task involves implementation, debugging, review, or any other work that could be claimed complete without concrete evidence.\n---\n\n# Verification Loop\n\nUse this skill when a task involves implementation, debugging, review, or any other work that\ncould be claimed complete without concrete evidence.\n\n## Core rule\n\nDo not treat a change as done until the relevant claim has been verified with the smallest\nmeaningful evidence.\n\n## Workflow\n\n1. Enumerate every independent claim that must be true for the task to be complete, including each\n   user requirement and acceptance criterion.\n2. For each claim, decide what evidence would prove or disprove it.\n3. Run the smallest meaningful verification for each claim.\n4. Read and record the actual result, not the expected result. For a command, preserve the\n   command, exit status, and concise non-sensitive observation. For a manual user-facing action,\n   preserve the action and its observed outcome; do not invent a process exit status.\n5. If a claim is disproven and the task calls for a fix, iterate when a safe, relevant change\n   remains. Otherwise, stop and hand off the negative result honestly; never declare success.\n6. Before completion or handoff, account for every claim as Verified, Failed, Not verified, or\n   Could not verify.\n\n## Verification categories\n\n- Behavior: run the user-facing flow or a minimal reproduction.\n- Tests: run the most relevant targeted tests first, then broader coverage if needed.\n- Types\u002Fbuild: confirm typecheck, build, or lint only when they are relevant to the claim.\n- Review claims: tie review conclusions to concrete code or tool output.\n- Environment limits: distinguish product failures from setup limitations.\n\n## Priorities\n\n- Prefer evidence over confidence.\n- Prefer the smallest proof that closes the relevant uncertainty.\n- Distinguish verified, unverified, and unverifiable outcomes explicitly.\n- Do not rely on \"it should work\" when a check can be run.\n- When an end-to-end flow matters, test the golden path before reporting completion.\n- Any selected host command may retain its own network behavior, even when described as a local\n  test or check. Inspect its script, configuration, and documentation before running it. If its\n  network behavior cannot be determined, treat it as a remote action and do not run it until the\n  destination and data flow are explicitly confirmed under the rules below.\n- Before any verification that would contact a remote endpoint, state the exact destination, the\n  minimal data to be sent, and whether the action may mutate remote state. The destination must be\n  supplied by the user or explicitly confirmed by the user before proceeding. Any potentially\n  mutating remote check also requires explicit user confirmation, even when its destination was\n  already supplied. Host policy must permit the action. Never send credentials, personal data,\n  private endpoints, or unrelated repository content.\n- If network access is unavailable or unsafe, do not substitute confidence for proof; report the\n  remote behavior as Could not verify, state why it was blocked, and give the next safe proof step.\n\n## Completion evidence format\n\nThe final report must include every completion claim enumerated in step 1. Every successful\nverification entry must include both the claim and the evidence actually observed. Do not write a\nbare statement such as `Verified: targeted tests`, and do not omit an untested requirement.\n\n- Verified: \u003Cthe claim that was proved>\n  - Evidence (command): \u003Ccommand> — \u003Cexit status and concise observed result>\n  - Evidence (manual): \u003Cuser-facing action> — \u003Cobserved outcome>\n- Failed: \u003Cthe claim that was disproven>\n  - Evidence: \u003Ccommand\u002Faction> — \u003Cstatus or outcome and concise observed result>\n- Not verified: \u003Cwhat was not checked>\n- Could not verify: \u003Cwhy verification was blocked>\n- Next proof step: \u003Cthe most useful remaining check>\n\nQuote or summarize only the output needed to prove the claim. Redact credentials, personal data,\nprivate endpoints, and unrelated repository content from completion reports.\n\n## Good outcomes\n\n- Fewer premature completion claims.\n- Clearer handoffs between implementation and review.\n- Lower regression risk.\n- Better distinction between confirmed facts and assumptions.\n\n## Notes\n\n- This is a workflow skill only.\n- It must not modify hooks, settings, plugins, or global configuration on its own.\n",{"data":29,"body":30},{"name":4,"description":6},{"type":31,"children":32},"root",[33,41,47,54,59,65,100,106,135,141,184,190,204,296,301,307,330,336],{"type":34,"tag":35,"props":36,"children":37},"element","h1",{"id":4},[38],{"type":39,"value":40},"text","Verification Loop",{"type":34,"tag":42,"props":43,"children":44},"p",{},[45],{"type":39,"value":46},"Use this skill when a task involves implementation, debugging, review, or any other work that\ncould be claimed complete without concrete evidence.",{"type":34,"tag":48,"props":49,"children":51},"h2",{"id":50},"core-rule",[52],{"type":39,"value":53},"Core rule",{"type":34,"tag":42,"props":55,"children":56},{},[57],{"type":39,"value":58},"Do not treat a change as done until the relevant claim has been verified with the smallest\nmeaningful evidence.",{"type":34,"tag":48,"props":60,"children":62},{"id":61},"workflow",[63],{"type":39,"value":64},"Workflow",{"type":34,"tag":66,"props":67,"children":68},"ol",{},[69,75,80,85,90,95],{"type":34,"tag":70,"props":71,"children":72},"li",{},[73],{"type":39,"value":74},"Enumerate every independent claim that must be true for the task to be complete, including each\nuser requirement and acceptance criterion.",{"type":34,"tag":70,"props":76,"children":77},{},[78],{"type":39,"value":79},"For each claim, decide what evidence would prove or disprove it.",{"type":34,"tag":70,"props":81,"children":82},{},[83],{"type":39,"value":84},"Run the smallest meaningful verification for each claim.",{"type":34,"tag":70,"props":86,"children":87},{},[88],{"type":39,"value":89},"Read and record the actual result, not the expected result. For a command, preserve the\ncommand, exit status, and concise non-sensitive observation. For a manual user-facing action,\npreserve the action and its observed outcome; do not invent a process exit status.",{"type":34,"tag":70,"props":91,"children":92},{},[93],{"type":39,"value":94},"If a claim is disproven and the task calls for a fix, iterate when a safe, relevant change\nremains. Otherwise, stop and hand off the negative result honestly; never declare success.",{"type":34,"tag":70,"props":96,"children":97},{},[98],{"type":39,"value":99},"Before completion or handoff, account for every claim as Verified, Failed, Not verified, or\nCould not verify.",{"type":34,"tag":48,"props":101,"children":103},{"id":102},"verification-categories",[104],{"type":39,"value":105},"Verification categories",{"type":34,"tag":107,"props":108,"children":109},"ul",{},[110,115,120,125,130],{"type":34,"tag":70,"props":111,"children":112},{},[113],{"type":39,"value":114},"Behavior: run the user-facing flow or a minimal reproduction.",{"type":34,"tag":70,"props":116,"children":117},{},[118],{"type":39,"value":119},"Tests: run the most relevant targeted tests first, then broader coverage if needed.",{"type":34,"tag":70,"props":121,"children":122},{},[123],{"type":39,"value":124},"Types\u002Fbuild: confirm typecheck, build, or lint only when they are relevant to the claim.",{"type":34,"tag":70,"props":126,"children":127},{},[128],{"type":39,"value":129},"Review claims: tie review conclusions to concrete code or tool output.",{"type":34,"tag":70,"props":131,"children":132},{},[133],{"type":39,"value":134},"Environment limits: distinguish product failures from setup limitations.",{"type":34,"tag":48,"props":136,"children":138},{"id":137},"priorities",[139],{"type":39,"value":140},"Priorities",{"type":34,"tag":107,"props":142,"children":143},{},[144,149,154,159,164,169,174,179],{"type":34,"tag":70,"props":145,"children":146},{},[147],{"type":39,"value":148},"Prefer evidence over confidence.",{"type":34,"tag":70,"props":150,"children":151},{},[152],{"type":39,"value":153},"Prefer the smallest proof that closes the relevant uncertainty.",{"type":34,"tag":70,"props":155,"children":156},{},[157],{"type":39,"value":158},"Distinguish verified, unverified, and unverifiable outcomes explicitly.",{"type":34,"tag":70,"props":160,"children":161},{},[162],{"type":39,"value":163},"Do not rely on \"it should work\" when a check can be run.",{"type":34,"tag":70,"props":165,"children":166},{},[167],{"type":39,"value":168},"When an end-to-end flow matters, test the golden path before reporting completion.",{"type":34,"tag":70,"props":170,"children":171},{},[172],{"type":39,"value":173},"Any selected host command may retain its own network behavior, even when described as a local\ntest or check. Inspect its script, configuration, and documentation before running it. If its\nnetwork behavior cannot be determined, treat it as a remote action and do not run it until the\ndestination and data flow are explicitly confirmed under the rules below.",{"type":34,"tag":70,"props":175,"children":176},{},[177],{"type":39,"value":178},"Before any verification that would contact a remote endpoint, state the exact destination, the\nminimal data to be sent, and whether the action may mutate remote state. The destination must be\nsupplied by the user or explicitly confirmed by the user before proceeding. Any potentially\nmutating remote check also requires explicit user confirmation, even when its destination was\nalready supplied. Host policy must permit the action. Never send credentials, personal data,\nprivate endpoints, or unrelated repository content.",{"type":34,"tag":70,"props":180,"children":181},{},[182],{"type":39,"value":183},"If network access is unavailable or unsafe, do not substitute confidence for proof; report the\nremote behavior as Could not verify, state why it was blocked, and give the next safe proof step.",{"type":34,"tag":48,"props":185,"children":187},{"id":186},"completion-evidence-format",[188],{"type":39,"value":189},"Completion evidence format",{"type":34,"tag":42,"props":191,"children":192},{},[193,195,202],{"type":39,"value":194},"The final report must include every completion claim enumerated in step 1. Every successful\nverification entry must include both the claim and the evidence actually observed. Do not write a\nbare statement such as ",{"type":34,"tag":196,"props":197,"children":199},"code",{"className":198},[],[200],{"type":39,"value":201},"Verified: targeted tests",{"type":39,"value":203},", and do not omit an untested requirement.",{"type":34,"tag":107,"props":205,"children":206},{},[207,249,269,279,288],{"type":34,"tag":70,"props":208,"children":209},{},[210,212],{"type":39,"value":211},"Verified: ",{"type":34,"tag":213,"props":214,"children":216},"the",{"claim":215,"that":215,"was":215,"proved":215},"",[217],{"type":34,"tag":107,"props":218,"children":219},{},[220,235],{"type":34,"tag":70,"props":221,"children":222},{},[223,225],{"type":39,"value":224},"Evidence (command): ",{"type":34,"tag":226,"props":227,"children":228},"command",{},[229,231],{"type":39,"value":230}," — ",{"type":34,"tag":232,"props":233,"children":234},"exit",{"status":215,"and":215,"concise":215,"observed":215,"result":215},[],{"type":34,"tag":70,"props":236,"children":237},{},[238,240],{"type":39,"value":239},"Evidence (manual): ",{"type":34,"tag":241,"props":242,"children":243},"user-facing",{"action":215},[244,245],{"type":39,"value":230},{"type":34,"tag":246,"props":247,"children":248},"observed",{"outcome":215},[],{"type":34,"tag":70,"props":250,"children":251},{},[252,254],{"type":39,"value":253},"Failed: ",{"type":34,"tag":213,"props":255,"children":256},{"claim":215,"that":215,"was":215,"disproven":215},[257],{"type":34,"tag":107,"props":258,"children":259},{},[260],{"type":34,"tag":70,"props":261,"children":262},{},[263,265],{"type":39,"value":264},"Evidence: \u003Ccommand\u002Faction> — ",{"type":34,"tag":266,"props":267,"children":268},"status",{"or":215,"outcome":215,"and":215,"concise":215,"observed":215,"result":215},[],{"type":34,"tag":70,"props":270,"children":271},{},[272,274],{"type":39,"value":273},"Not verified: ",{"type":34,"tag":275,"props":276,"children":278},"what",{"was":215,"not":215,"checked":277},true,[],{"type":34,"tag":70,"props":280,"children":281},{},[282,284],{"type":39,"value":283},"Could not verify: ",{"type":34,"tag":285,"props":286,"children":287},"why",{"verification":215,"was":215,"blocked":215},[],{"type":34,"tag":70,"props":289,"children":290},{},[291,293],{"type":39,"value":292},"Next proof step: ",{"type":34,"tag":213,"props":294,"children":295},{"most":215,"useful":215,"remaining":215,"check":215},[],{"type":34,"tag":42,"props":297,"children":298},{},[299],{"type":39,"value":300},"Quote or summarize only the output needed to prove the claim. Redact credentials, personal data,\nprivate endpoints, and unrelated repository content from completion reports.",{"type":34,"tag":48,"props":302,"children":304},{"id":303},"good-outcomes",[305],{"type":39,"value":306},"Good outcomes",{"type":34,"tag":107,"props":308,"children":309},{},[310,315,320,325],{"type":34,"tag":70,"props":311,"children":312},{},[313],{"type":39,"value":314},"Fewer premature completion claims.",{"type":34,"tag":70,"props":316,"children":317},{},[318],{"type":39,"value":319},"Clearer handoffs between implementation and review.",{"type":34,"tag":70,"props":321,"children":322},{},[323],{"type":39,"value":324},"Lower regression risk.",{"type":34,"tag":70,"props":326,"children":327},{},[328],{"type":39,"value":329},"Better distinction between confirmed facts and assumptions.",{"type":34,"tag":48,"props":331,"children":333},{"id":332},"notes",[334],{"type":39,"value":335},"Notes",{"type":34,"tag":107,"props":337,"children":338},{},[339,344],{"type":34,"tag":70,"props":340,"children":341},{},[342],{"type":39,"value":343},"This is a workflow skill only.",{"type":34,"tag":70,"props":345,"children":346},{},[347],{"type":39,"value":348},"It must not modify hooks, settings, plugins, or global configuration on its own.",{"items":350,"total":551},[351,375,391,410,425,445,463,481,496,512,531,541],{"slug":352,"name":352,"fn":353,"description":354,"org":355,"tags":356,"stars":372,"repoUrl":373,"updatedAt":374},"android-native-dev","develop Android native applications","Android native application development and UI design guide. Covers Material Design 3, Kotlin\u002FCompose development, project configuration, accessibility, and build troubleshooting. Read this before Android native application development.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[357,360,363,366,369],{"name":358,"slug":359,"type":16},"Accessibility","accessibility",{"name":361,"slug":362,"type":16},"Android","android",{"name":364,"slug":365,"type":16},"Kotlin","kotlin",{"name":367,"slug":368,"type":16},"Mobile","mobile",{"name":370,"slug":371,"type":16},"UI Components","ui-components",13030,"https:\u002F\u002Fgithub.com\u002FMiniMax-AI\u002Fskills","2026-07-13T06:16:54.247834",{"slug":376,"name":376,"fn":377,"description":378,"org":379,"tags":380,"stars":372,"repoUrl":373,"updatedAt":390},"buddy-sings","generate singing performances for AI companions","Use when user wants their Claude Code pet (\u002Fbuddy) to sing a song. Triggers on any request that combines the concept of their Claude Code buddy, pet, or companion with singing or music. Supports multilingual triggers — match equivalent phrases in any language.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[381,384,387],{"name":382,"slug":383,"type":16},"Agents","agents",{"name":385,"slug":386,"type":16},"Audio","audio",{"name":388,"slug":389,"type":16},"Creative","creative","2026-07-13T06:16:35.130644",{"slug":392,"name":392,"fn":393,"description":394,"org":395,"tags":396,"stars":372,"repoUrl":373,"updatedAt":409},"color-font-skill","select color palettes and font pairings","Choose presentation-ready color palettes and font pairings for PPT\u002Fdesign tasks. Use when users ask for visual theme choices, brand-safe palettes, or font recommendations. Triggers include: 配色, 色板, 字体, color palette, font, PPT配色, 字体搭配.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[397,400,403,406],{"name":398,"slug":399,"type":16},"Design","design",{"name":401,"slug":402,"type":16},"Presentations","presentations",{"name":404,"slug":405,"type":16},"Themes","themes",{"name":407,"slug":408,"type":16},"Typography","typography","2026-07-13T06:17:02.785587",{"slug":411,"name":411,"fn":412,"description":413,"org":414,"tags":415,"stars":372,"repoUrl":373,"updatedAt":424},"design-style-skill","select visual design systems for presentations","Select a consistent visual design system for PPT slides using radius\u002Fspacing style recipes. Use when users ask for overall style direction or component styling consistency. Includes Sharp\u002FSoft\u002FRounded\u002FPill recipes, component mappings, typography\u002Fspacing rules, and mixing guidance. Triggers: 风格, style, radius, spacing, 圆角, 间距, PPT风格, 视觉风格, design style, component style.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[416,417,420,423],{"name":398,"slug":399,"type":16},{"name":418,"slug":419,"type":16},"Design System","design-system",{"name":421,"slug":422,"type":16},"PowerPoint","powerpoint",{"name":401,"slug":402,"type":16},"2026-07-13T06:17:10.398389",{"slug":426,"name":426,"fn":427,"description":428,"org":429,"tags":430,"stars":372,"repoUrl":373,"updatedAt":444},"flutter-dev","build cross-platform apps with Flutter","Flutter cross-platform development guide covering widget patterns, Riverpod\u002FBloc state management, GoRouter navigation, performance optimization, and platform-specific implementations. Includes const optimization, responsive layouts, testing strategies, and DevTools profiling.\nUse when: building Flutter apps, implementing state management (Riverpod\u002FBloc), setting up GoRouter navigation, creating custom widgets, optimizing performance, writing widget tests, cross-platform development.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[431,434,437,438,441],{"name":432,"slug":433,"type":16},"Dart","dart",{"name":435,"slug":436,"type":16},"Flutter","flutter",{"name":367,"slug":368,"type":16},{"name":439,"slug":440,"type":16},"Performance","performance",{"name":442,"slug":443,"type":16},"State Management","state-management","2026-07-13T06:16:36.626679",{"slug":446,"name":446,"fn":447,"description":448,"org":449,"tags":450,"stars":372,"repoUrl":373,"updatedAt":462},"frontend-dev","build visually striking frontend web pages","Full-stack frontend development combining premium UI design, cinematic animations,\nAI-generated media assets, persuasive copywriting, and visual art. Builds complete,\nvisually striking web pages with real media, advanced motion, and compelling copy.\nUse when: building landing pages, marketing sites, product pages, dashboards,\ngenerating media assets (image\u002Fvideo\u002Faudio\u002Fmusic), writing conversion copy,\ncreating generative art, or implementing cinematic scroll animations.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[451,454,455,456,459],{"name":452,"slug":453,"type":16},"Animation","animation",{"name":388,"slug":389,"type":16},{"name":398,"slug":399,"type":16},{"name":457,"slug":458,"type":16},"Frontend","frontend",{"name":460,"slug":461,"type":16},"Web Development","web-development","2026-07-13T06:16:39.108827",{"slug":464,"name":464,"fn":465,"description":466,"org":467,"tags":468,"stars":372,"repoUrl":373,"updatedAt":480},"fullstack-dev","build full-stack web applications","Full-stack backend architecture and frontend-backend integration guide.\nTRIGGER when: building a full-stack app, creating REST API with frontend, scaffolding backend service,\nbuilding todo app, building CRUD app, building real-time app, building chat app,\nExpress + React, Next.js API, Node.js backend, Python backend, Go backend,\ndesigning service layers, implementing error handling, managing config\u002Fauth,\nsetting up API clients, implementing auth flows, handling file uploads,\nadding real-time features (SSE\u002FWebSocket), hardening for production.\nDO NOT TRIGGER when: pure frontend UI work, pure CSS\u002Fstyling, database schema only.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[469,472,473,476,479],{"name":470,"slug":471,"type":16},"Backend","backend",{"name":457,"slug":458,"type":16},{"name":474,"slug":475,"type":16},"Full-stack","full-stack",{"name":477,"slug":478,"type":16},"REST API","rest-api",{"name":460,"slug":461,"type":16},"2026-07-13T06:16:43.219005",{"slug":482,"name":482,"fn":483,"description":484,"org":485,"tags":486,"stars":372,"repoUrl":373,"updatedAt":495},"gif-sticker-maker","create animated GIF stickers from photos","Convert photos (people, pets, objects, logos) into 4 animated GIF stickers with captions.\nUse when: user wants to create cartoon stickers, GIF expressions, emoji packs, animated avatars,\nor convert photos to Funko Pop \u002F Pop Mart blind box style animations.\nTriggers: sticker, GIF, cartoon, emoji, expression pack, avatar animation.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[487,488,489,492],{"name":452,"slug":453,"type":16},{"name":388,"slug":389,"type":16},{"name":490,"slug":491,"type":16},"Images","images",{"name":493,"slug":494,"type":16},"Media","media","2026-07-13T06:16:51.74461",{"slug":497,"name":497,"fn":498,"description":499,"org":500,"tags":501,"stars":372,"repoUrl":373,"updatedAt":511},"ios-application-dev","develop iOS applications with SwiftUI and UIKit","iOS application development guide covering UIKit, SnapKit, and SwiftUI. Includes touch targets, safe areas, navigation patterns, Dynamic Type, Dark Mode, accessibility, collection views, common UI components, and SwiftUI design guidelines. For detailed references on specific topics, see the reference files.\nUse when: developing iOS apps, implementing UI, reviewing iOS code, working with UIKit\u002FSnapKit\u002FSwiftUI layouts, building iPhone interfaces, Swift mobile development, Apple HIG compliance, iOS accessibility implementation.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[502,503,506,507,510],{"name":358,"slug":359,"type":16},{"name":504,"slug":505,"type":16},"iOS","ios",{"name":367,"slug":368,"type":16},{"name":508,"slug":509,"type":16},"SwiftUI","swiftui",{"name":370,"slug":371,"type":16},"2026-07-13T06:16:55.686092",{"slug":513,"name":513,"fn":514,"description":515,"org":516,"tags":517,"stars":372,"repoUrl":373,"updatedAt":530},"minimax-docx","create and edit DOCX documents","Professional DOCX document creation, editing, and formatting using OpenXML SDK (.NET). Three pipelines: (A) create new documents from scratch, (B) fill\u002Fedit content in existing documents, (C) apply template formatting with XSD validation gate-check. MUST use this skill whenever the user wants to produce, modify, or format a Word document — including when they say \"write a report\", \"draft a proposal\", \"make a contract\", \"fill in this form\", \"reformat to match this template\", or any task whose final output is a .docx file. Even if the user doesn't mention \"docx\" explicitly, if the task implies a printable\u002Fformal document, use this skill.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[518,521,524,527],{"name":519,"slug":520,"type":16},"Documents","documents",{"name":522,"slug":523,"type":16},"DOCX","docx",{"name":525,"slug":526,"type":16},"Office","office",{"name":528,"slug":529,"type":16},"Templates","templates","2026-07-13T06:16:40.461868",{"slug":532,"name":532,"fn":533,"description":534,"org":535,"tags":536,"stars":372,"repoUrl":373,"updatedAt":540},"minimax-music-gen","generate music and audio tracks","Use when user wants to generate music, songs, or audio tracks. Triggers on any request involving music creation, song writing, lyrics generation, audio production, or covers. Also triggers when user provides lyrics and wants them turned into a song, or describes a mood\u002Fscene and wants background music. Supports multilingual triggers — match equivalent phrases in any language. Do NOT use for music playback of existing files, music theory questions, or music recommendation without generation.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[537,538,539],{"name":385,"slug":386,"type":16},{"name":388,"slug":389,"type":16},{"name":493,"slug":494,"type":16},"2026-07-13T06:16:50.381758",{"slug":542,"name":542,"fn":543,"description":544,"org":545,"tags":546,"stars":372,"repoUrl":373,"updatedAt":550},"minimax-music-playlist","generate personalized music playlists","Generate personalized music playlists by analyzing the user's music taste and generation feedback history. Triggers on any request involving playlist generation, music taste profiling, or personalized music recommendations. Supports multilingual triggers — match equivalent phrases in any language.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[547,548,549],{"name":385,"slug":386,"type":16},{"name":388,"slug":389,"type":16},{"name":493,"slug":494,"type":16},"2026-07-13T06:16:57.002997",56,{"items":553,"total":649},[554,570,582,598,609,625,639],{"slug":555,"name":555,"fn":556,"description":557,"org":558,"tags":559,"stars":17,"repoUrl":18,"updatedAt":569},"article2tasks","convert articles into Dida365 tasks","将技术周报（批量）或单篇文章整理为滴答清单待办事项，自动分类到已有清单并打标签，全程通过 MCP 写入，跨平台无需任何本地脚本。当用户提供周报内容、文章链接，或提及「周报」「文章汇总」「添加到滴答」时，使用此技能。",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[560,563,566],{"name":561,"slug":562,"type":16},"Content Creation","content-creation",{"name":564,"slug":565,"type":16},"MCP","mcp",{"name":567,"slug":568,"type":16},"Task Management","task-management","2026-08-18T03:49:38.751656",{"slug":571,"name":571,"fn":572,"description":573,"org":574,"tags":575,"stars":17,"repoUrl":18,"updatedAt":581},"dida365","manage Dida365 tasks and habits","Manage 滴答清单 (Dida365 China) tasks, lists, habits, focus records and countdowns through the official Dida365 MCP server at mcp.dida365.com. Use when the user asks to check, plan, create, update, complete or review tasks and habits on dida365.com, or asks about focus history and countdowns.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[576,577,580],{"name":564,"slug":565,"type":16},{"name":578,"slug":579,"type":16},"Scheduling","scheduling",{"name":567,"slug":568,"type":16},"2026-08-18T03:49:37.126385",{"slug":583,"name":583,"fn":584,"description":585,"org":586,"tags":587,"stars":17,"repoUrl":18,"updatedAt":597},"github-explore","explore and audit GitHub repositories","Use when the user wants to search\u002Fdiscover\u002Fsummarize\u002Faudit GitHub (find repos about X, explore a topic's landscape, what's trending, repo overview, similar projects, code search, issue\u002FPR search, org audit) or run gh CLI operations. Prefer scripts\u002F for discovery; raw gh commands for management ops.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[588,591,594],{"name":589,"slug":590,"type":16},"Code Analysis","code-analysis",{"name":592,"slug":593,"type":16},"GitHub","github",{"name":595,"slug":596,"type":16},"Research","research","2026-08-18T03:49:39.302333",{"slug":599,"name":599,"fn":600,"description":601,"org":602,"tags":603,"stars":17,"repoUrl":18,"updatedAt":608},"mcp-server-patterns","design and debug MCP servers","Reference patterns for designing, evaluating, integrating, and debugging MCP servers. Use this Skill whenever the task involves deciding whether to add an MCP server, reviewing a server design, integrating one into a workflow, or diagnosing why one fails.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[604,607],{"name":605,"slug":606,"type":16},"Architecture","architecture",{"name":564,"slug":565,"type":16},"2026-08-18T03:49:42.711595",{"slug":610,"name":610,"fn":611,"description":612,"org":613,"tags":614,"stars":17,"repoUrl":18,"updatedAt":624},"minimax-code-trajectory","visualize MiniMax code session trajectories","Inspect or visualize privacy-aware timelines for local MiniMax Code sessions. Use when the user asks to show, draw, open, review, or diagnose a task trajectory, summarize tool or token activity, inspect compaction or failure events, or compare recent session metadata without opening raw ledger files.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[615,618,621],{"name":616,"slug":617,"type":16},"Debugging","debugging",{"name":619,"slug":620,"type":16},"Observability","observability",{"name":622,"slug":623,"type":16},"Tracing","tracing","2026-08-18T03:49:38.218712",{"slug":626,"name":626,"fn":627,"description":628,"org":629,"tags":630,"stars":17,"repoUrl":18,"updatedAt":638},"search-first","enforce search-before-edit code workflows","Enforce a search-before-edit workflow for code changes. Use this Skill whenever a task involves changing code, tracing behavior, or understanding an unfamiliar area, so the agent searches and reads the relevant files before proposing or implementing edits.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[631,634,635],{"name":632,"slug":633,"type":16},"Best Practices","best-practices",{"name":589,"slug":590,"type":16},{"name":636,"slug":637,"type":16},"Engineering","engineering","2026-08-18T03:49:37.673989",{"slug":640,"name":640,"fn":641,"description":642,"org":643,"tags":644,"stars":17,"repoUrl":18,"updatedAt":648},"ticktick","manage TickTick tasks and habits","Manage TickTick (international, ticktick.com) tasks, lists, habits, focus records and countdowns through the official TickTick MCP server at mcp.ticktick.com. Use when the user asks to check, plan, create, update, complete or review tasks and habits on TickTick, or asks about focus history and countdowns.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[645,646,647],{"name":564,"slug":565,"type":16},{"name":578,"slug":579,"type":16},{"name":567,"slug":568,"type":16},"2026-08-18T03:49:42.187465",8]