[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DBZDGV98EQ4PYCSZN96BF5":3,"skill-same:01M6DBZDGV98EQ4PYCSZN96BF5":58},{"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":23,"publishedAt":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":14,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":43,"install":44,"resources":57},"01M6DBZDGV98EQ4PYCSZN96BF5","source-command-resume-session",null,"Load the most recent session file from ~\u002F.claude\u002Fsessions\u002F and resume work with full context from where the last session ended.","Prekzursil\u002Fagent-skills-toolchain","Prekzursil","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54636077?v=4","01M6DACZ1PCQHD99SCR1YXG28B","Andrei Mihai Visalon","01M6DACZ670WZF535V3WYYSS4Z",0,"MIT","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsource-command-resume-session\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32],"command","session","resume","source command resume session","sessions","file","work","context","full","2026-11-10 10:12:30",false,"---\nname: \"source-command-resume-session\"\ndescription: \"Load the most recent session file from ~\u002F.claude\u002Fsessions\u002F and resume work with full context from where the last session ended.\"\n---\n\n# source-command-resume-session\n\nUse this skill when the user asks to run the migrated source command `resume-session`.\n\n## Command Template\n\n# Resume Session Command\n\nLoad the last saved session state and orient fully before doing any work.\nThis command is the counterpart to `\u002Fsave-session`.\n\n## When to Use\n\n- Starting a new session to continue work from a previous day\n- After starting a fresh session due to context limits\n- When handing off a session file from another source (just provide the file path)\n- Any time you have a session file and want Codex to fully absorb it before proceeding\n\n## Usage\n\n```\n\u002Fresume-session                                                      # loads most recent file in ~\u002F.claude\u002Fsessions\u002F\n\u002Fresume-session 2024-01-15                                           # loads most recent session for that date\n\u002Fresume-session ~\u002F.claude\u002Fsessions\u002F2024-01-15-session.tmp           # loads a specific legacy-format file\n\u002Fresume-session ~\u002F.claude\u002Fsessions\u002F2024-01-15-abc123de-session.tmp  # loads a current short-id session file\n```\n\n## Process\n\n### Step 1: Find the session file\n\nIf no argument provided:\n\n1. Check `~\u002F.claude\u002Fsessions\u002F`\n2. Pick the most recently modified `*-session.tmp` file\n3. If the folder does not exist or has no matching files, tell the user:\n   ```\n   No session files found in ~\u002F.claude\u002Fsessions\u002F\n   Run \u002Fsave-session at the end of a session to create one.\n   ```\n   Then stop.\n\nIf an argument is provided:\n\n- If it looks like a date (`YYYY-MM-DD`), search `~\u002F.claude\u002Fsessions\u002F` for files matching\n  `YYYY-MM-DD-session.tmp` (legacy format) or `YYYY-MM-DD-\u003Cshortid>-session.tmp` (current format)\n  and load the most recently modified variant for that date\n- If it looks like a file path, read that file directly\n- If not found, report clearly and stop\n\n### Step 2: Read the entire session file\n\nRead the complete file. Do not summarize yet.\n\n### Step 3: Confirm understanding\n\nRespond with a structured briefing in this exact format:\n\n```\nSESSION LOADED: [actual resolved path to the file]\n════════════════════════════════════════════════\n\nPROJECT: [project name \u002F topic from file]\n\nWHAT WE'RE BUILDING:\n[2-3 sentence summary in your own words]\n\nCURRENT STATE:\n✅ Working: [count] items confirmed\n? In Progress: [list files that are in progress]\n?️ Not Started: [list planned but untouched]\n\nWHAT NOT TO RETRY:\n[list every failed approach with its reason — this is critical]\n\nOPEN QUESTIONS \u002F BLOCKERS:\n[list any blockers or unanswered questions]\n\nNEXT STEP:\n[exact next step if defined in the file]\n[if not defined: \"No next step defined — recommend reviewing 'What Has NOT Been Tried Yet' together before starting\"]\n\n════════════════════════════════════════════════\nReady to continue. What would you like to do?\n```\n\n### Step 4: Wait for the user\n\nDo NOT start working automatically. Do NOT touch any files. Wait for the user to say what to do next.\n\nIf the next step is clearly defined in the session file and the user says \"continue\" or \"yes\" or similar — proceed with that exact next step.\n\nIf no next step is defined — ask the user where to start, and optionally suggest an approach from the \"What Has NOT Been Tried Yet\" section.\n\n---\n\n## Edge Cases\n\n**Multiple sessions for the same date** (`2024-01-15-session.tmp`, `2024-01-15-abc123de-session.tmp`):\nLoad the most recently modified matching file for that date, regardless of whether it uses the legacy no-id format or the current short-id format.\n\n**Session file references files that no longer exist:**\nNote this during the briefing — \"⚠️ `path\u002Fto\u002Ffile.ts` referenced in session but not found on disk.\"\n\n**Session file is from more than 7 days ago:**\nNote the gap — \"⚠️ This session is from N days ago (threshold: 7 days). Things may have changed.\" — then proceed normally.\n\n**User provides a file path directly (e.g., forwarded from a teammate):**\nRead it and follow the same briefing process — the format is the same regardless of source.\n\n**Session file is empty or malformed:**\nReport: \"Session file found but appears empty or unreadable. You may need to create a new one with \u002Fsave-session.\"\n\n---\n\n## Example Output\n\n```\nSESSION LOADED: \u002FUsers\u002Fyou\u002F.claude\u002Fsessions\u002F2024-01-15-abc123de-session.tmp\n════════════════════════════════════════════════\n\nPROJECT: my-app — JWT Authentication\n\nWHAT WE'RE BUILDING:\nUser authentication with JWT tokens stored in httpOnly cookies.\nRegister and login endpoints are partially done. Route protection\nvia middleware hasn't been started yet.\n\nCURRENT STATE:\n✅ Working: 3 items (register endpoint, JWT generation, password hashing)\n? In Progress: app\u002Fapi\u002Fauth\u002Flogin\u002Froute.ts (token works, cookie not set yet)\n?️ Not Started: middleware.ts, app\u002Flogin\u002Fpage.tsx\n\nWHAT NOT TO RETRY:\n❌ Next-Auth — conflicts with custom Prisma adapter, threw adapter error on every request\n❌ localStorage for JWT — causes SSR hydration mismatch, incompatible with Next.js\n\nOPEN QUESTIONS \u002F BLOCKERS:\n- Does cookies().set() work inside a Route Handler or only Server Actions?\n\nNEXT STEP:\nIn app\u002Fapi\u002Fauth\u002Flogin\u002Froute.ts — set the JWT as an httpOnly cookie using\ncookies().set('token', jwt, { httpOnly: true, secure: true, sameSite: 'strict' })\nthen test with Postman for a Set-Cookie header in the response.\n\n════════════════════════════════════════════════\nReady to continue. What would you like to do?\n```\n\n---\n\n## Notes\n\n- Never modify the session file when loading it — it's a read-only historical record\n- The briefing format is fixed — do not skip sections even if they are empty\n- \"What Not To Retry\" must always be shown, even if it just says \"None\" — it's too important to miss\n- After resuming, the user may want to run `\u002Fsave-session` again at the end of the new session to create a new dated file\n","# source-command-resume-session\n\nUse this skill when the user asks to run the migrated source command `resume-session`.\n\n## Command Template\n\n# Resume Session Command\n\nLoad the last saved session state and orient fully before doing any work.\nThis command is the counterpart to `\u002Fsave-session`.\n\n## When to Use\n\n- Starting a new session to continue work from a previous day\n- After starting a fresh session due to context limits\n- When handing off a session file from another source (just provide the file path)\n- Any time you have a session file and want Codex to fully absorb it before proceeding\n\n## Usage\n\n```\n\u002Fresume-session                                                      # loads most recent file in ~\u002F.claude\u002Fsessions\u002F\n\u002Fresume-session 2024-01-15                                           # loads most recent session for that date\n\u002Fresume-session ~\u002F.claude\u002Fsessions\u002F2024-01-15-session.tmp           # loads a specific legacy-format file\n\u002Fresume-session ~\u002F.claude\u002Fsessions\u002F2024-01-15-abc123de-session.tmp  # loads a current short-id session file\n```\n\n## Process\n\n### Step 1: Find the session file\n\nIf no argument provided:\n\n1. Check `~\u002F.claude\u002Fsessions\u002F`\n2. Pick the most recently modified `*-session.tmp` file\n3. If the folder does not exist or has no matching files, tell the user:\n   ```\n   No session files found in ~\u002F.claude\u002Fsessions\u002F\n   Run \u002Fsave-session at the end of a session to create one.\n   ```\n   Then stop.\n\nIf an argument is provided:\n\n- If it looks like a date (`YYYY-MM-DD`), search `~\u002F.claude\u002Fsessions\u002F` for files matching\n  `YYYY-MM-DD-session.tmp` (legacy format) or `YYYY-MM-DD-\u003Cshortid>-session.tmp` (current format)\n  and load the most recently modified variant for that date\n- If it looks like a file path, read that file directly\n- If not found, report clearly and stop\n\n### Step 2: Read the entire session file\n\nRead the complete file. Do not summarize yet.\n\n### Step 3: Confirm understanding\n\nRespond with a structured briefing in this exact format:\n\n```\nSESSION LOADED: [actual resolved path to the file]\n════════════════════════════════════════════════\n\nPROJECT: [project name \u002F topic from file]\n\nWHAT WE'RE BUILDING:\n[2-3 sentence summary in your own words]\n\nCURRENT STATE:\n✅ Working: [count] items confirmed\n? In Progress: [list files that are in progress]\n?️ Not Started: [list planned but untouched]\n\nWHAT NOT TO RETRY:\n[list every failed approach with its reason — this is critical]\n\nOPEN QUESTIONS \u002F BLOCKERS:\n[list any blockers or unanswered questions]\n\nNEXT STEP:\n[exact next step if defined in the file]\n[if not defined: \"No next step defined — recommend reviewing 'What Has NOT Been Tried Yet' together before starting\"]\n\n════════════════════════════════════════════════\nReady to continue. What would you like to do?\n```\n\n### Step 4: Wait for the user\n\nDo NOT start working automatically. Do NOT touch any files. Wait for the user to say what to do next.\n\nIf the next step is clearly defined in the session file and the user says \"continue\" or \"yes\" or similar — proceed with that exact next step.\n\nIf no next step is defined — ask the user where to start, and optionally suggest an approach from the \"What Has NOT Been Tried Yet\" section.\n\n---\n\n## Edge Cases\n\n**Multiple sessions for the same date** (`2024-01-15-session.tmp`, `2024-01-15-abc123de-session.tmp`):\nLoad the most recently modified matching file for that date, regardless of whether it uses the legacy no-id format or the current short-id format.\n\n**Session file references files that no longer exist:**\nNote this during the briefing — \"⚠️ `path\u002Fto\u002Ffile.ts` referenced in session but not found on disk.\"\n\n**Session file is from more than 7 days ago:**\nNote the gap — \"⚠️ This session is from N days ago (threshold: 7 days). Things may have changed.\" — then proceed normally.\n\n**User provides a file path directly (e.g., forwarded from a teammate):**\nRead it and follow the same briefing process — the format is the same regardless of source.\n\n**Session file is empty or malformed:**\nReport: \"Session file found but appears empty or unreadable. You may need to create a new one with \u002Fsave-session.\"\n\n---\n\n## Example Output\n\n```\nSESSION LOADED: \u002FUsers\u002Fyou\u002F.claude\u002Fsessions\u002F2024-01-15-abc123de-session.tmp\n════════════════════════════════════════════════\n\nPROJECT: my-app — JWT Authentication\n\nWHAT WE'RE BUILDING:\nUser authentication with JWT tokens stored in httpOnly cookies.\nRegister and login endpoints are partially done. Route protection\nvia middleware hasn't been started yet.\n\nCURRENT STATE:\n✅ Working: 3 items (register endpoint, JWT generation, password hashing)\n? In Progress: app\u002Fapi\u002Fauth\u002Flogin\u002Froute.ts (token works, cookie not set yet)\n?️ Not Started: middleware.ts, app\u002Flogin\u002Fpage.tsx\n\nWHAT NOT TO RETRY:\n❌ Next-Auth — conflicts with custom Prisma adapter, threw adapter error on every request\n❌ localStorage for JWT — causes SSR hydration mismatch, incompatible with Next.js\n\nOPEN QUESTIONS \u002F BLOCKERS:\n- Does cookies().set() work inside a Route Handler or only Server Actions?\n\nNEXT STEP:\nIn app\u002Fapi\u002Fauth\u002Flogin\u002Froute.ts — set the JWT as an httpOnly cookie using\ncookies().set('token', jwt, { httpOnly: true, secure: true, sameSite: 'strict' })\nthen test with Postman for a Set-Cookie header in the response.\n\n════════════════════════════════════════════════\nReady to continue. What would you like to do?\n```\n\n---\n\n## Notes\n\n- Never modify the session file when loading it — it's a read-only historical record\n- The briefing format is fixed — do not skip sections even if they are empty\n- \"What Not To Retry\" must always be shown, even if it just says \"None\" — it's too important to miss\n- After resuming, the user may want to run `\u002Fsave-session` again at the end of the new session to create a new dated file\n",{"name":5,"description":7},"main","a298c929b6cbd662e1fce54302ce520d5ceea1a5",".agents\u002Fskills\u002Fsource-command-resume-session","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain","https:\u002F\u002Fgithub.com\u002FPrekzursil","2026-11-02 14:30:57",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add Prekzursil\u002Fagent-skills-toolchain --skill source-command-resume-session",{"tool":50,"command":51},"bunx","bunx skills add Prekzursil\u002Fagent-skills-toolchain --skill source-command-resume-session",{"tool":53,"command":54},"pnpm","pnpm dlx skills add Prekzursil\u002Fagent-skills-toolchain --skill source-command-resume-session","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsource-command-resume-session\u002FSKILL.md",true,[],[59,79,110,137,151,166],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":33},"01M6DF7D7478R55P46REYH4QAC","clarify-requirements","Resolve genuine pre-execution ambiguity by scanning repo context, generating 1-6 grounded options, and asking 1-3 focused questions via AskUserQuestion. NOT for mid-task use (injection risk); NOT when the goal is already unambiguous; use to disambiguate vague prompts before any file edits.","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Fworkspace-hooks\u002Fskills\u002Fclarify-requirements\u002FSKILL.md",[],[66,67,68,69,70,71,72,73,74,75,31,76,77,78,29],"clarify requirements","clarify","requirements","risk","options","task","prompts","goal","scanning","use","repo","injection","execution",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":90,"publishedAt":33},"01M6DF79CA4BHJS66J8EZDBPWJ","openmm-md","Run FREE, open-source, Windows-native GPU molecular dynamics via the openmm-md MCP (OpenMM + CUDA on the local NVIDIA GPU). Use for protein \u002F protein-ligand MD when you want a free stack or are on Windows without a Schrodinger license. Covers the full workflow (prepare, solvate, minimize, equilibrate, production, analyze, mmgbsa) AND an honest decision guide vs Schrodinger Desmond, including how to run Desmond legitimately on Linux or a cloud GPU with a real license. This is a deliberately LESSER free alternative and does NOT replace the schrodinger MCP tools. Do NOT use it to pick a free tool when a validated FEP+, WaterMap, IFD-MD, or Prime MM-GBSA result is actually required.","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Fmcp\u002Fopenmm-md-mcp\u002Fskill\u002Fopenmm-md\u002FSKILL.md",[85],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[91,92,93,94,95,96,97,98,99,100,101,102,103,104,75,105,106,107,108,109],"openmm md","how","decision","pick","linux","analyze","tool","stack","open","NVIDIA","gpu","license","workflow","windows","free","molecular dynamics","local","do","MCP",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":122,"publishedAt":33},"01M6DF76C1MG85VEWP8VZCBNMN","visual-review","Take screenshots of web pages and UI using Playwright for visual review and iteration","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fvisual-review\u002FSKILL.md",[116,119],{"categoryNo":117,"categoryName":118,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":120,"categoryName":121,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000008","测试与质量",[123,124,125,126,127,128,129,130,131,132,92,133,134,135,136],"review","visual","visual review","pages","web","false","iteration","take","check","slides","ui","screenshot","playwright","screenshots",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":33},"01M6DF73AQVCBZKEN0YXEX9FXP","status","Diagnostic status report — shows metaswarm installation state, project setup, and potential issues","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fstatus\u002FSKILL.md",[],[139,144,145,146,147,148,149,150],"setup","report","project","installation","project setup","issues","state",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":33},"01M6DF6X6C2XB0P6GX76P7TTYV","start","Use when starting work on any task, when the user mentions metaswarm, or when the user wants to begin tracked development work","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fstart\u002FSKILL.md",[157],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},[153,159,71,160,161,162,75,163,30,164,165],"start issue","issue","ready","work on issue","user","work on","development",{"skillNo":167,"name":144,"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":171,"publishedAt":33},"01M6DF6QMJ9AJKFKHHKRT005PQ","Interactive project setup — detects your project, configures metaswarm, writes project-local files","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fsetup\u002FSKILL.md",[],[144,146,107,172,148,173],"files","interactive"]