[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KM2NP3YJ76W6C513J71CDP":3,"skill-same:01M6KM2NP3YJ76W6C513J71CDP":130},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":77,"commitSha":78,"skillDirectory":79,"forksCount":80,"repositoryHtmlUrl":81,"repositoryHomepageUrl":82,"ownerHtmlUrl":83,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":84,"install":85,"resources":97},"01M6KM2NP3YJ76W6C513J71CDP","planning-with-files",null,"Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.","cxcscmu\u002FSkillLearnBench","cxcscmu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142838272?v=4","01M6KCQDFQWPDSN0MKZY96MSQP","01M6KCQDM7G70TKJ28NTSQC0RZ",93,"MIT","https:\u002F\u002Fgithub.com\u002Fcxcscmu\u002FSkillLearnBench\u002Fblob\u002Fmain\u002Fskills\u002Fhuman_authored\u002Forganize-messy-files\u002Fplanning-with-files\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"with files","planning","with","files","planning with files","edit","websearch","scripts","progress","Echo","ready","auto","write","read","command","projects","plan","Bash","update","tasks","2026-11-10 10:12:30",false,"---\nname: planning-with-files\ndescription: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.\nallowed-tools:\n  - Read\n  - Write\n  - Edit\n  - Bash\n  - Glob\n  - Grep\n  - WebFetch\n  - WebSearch\nmetadata:\n  version: \"2.1.2\"\n  user-invocable: true\n  hooks:\n    SessionStart:\n      - hooks:\n          - type: command\n            command: \"echo '[planning-with-files] Ready. Auto-activates for complex tasks, or invoke manually with \u002Fplanning-with-files'\"\n    PreToolUse:\n      - matcher: \"Write|Edit|Bash\"\n        hooks:\n          - type: command\n            command: \"cat task_plan.md 2>\u002Fdev\u002Fnull | head -30 || true\"\n    PostToolUse:\n      - matcher: \"Write|Edit\"\n        hooks:\n          - type: command\n            command: \"echo '[planning-with-files] File updated. If this completes a phase, update task_plan.md status.'\"\n    Stop:\n      - hooks:\n          - type: command\n            command: \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fcheck-complete.sh\"\n---\n\n# Planning with Files\n\nWork like Manus: Use persistent markdown files as your \"working memory on disk.\"\n\n## Important: Where Files Go\n\nWhen using this skill:\n\n- **Templates** are stored in the skill directory at `${CLAUDE_PLUGIN_ROOT}\u002Ftemplates\u002F`\n- **Your planning files** (`task_plan.md`, `findings.md`, `progress.md`) should be created in **your project directory** — the folder where you're working\n\n| Location | What Goes There |\n|----------|-----------------|\n| Skill directory (`${CLAUDE_PLUGIN_ROOT}\u002F`) | Templates, scripts, reference docs |\n| Your project directory | `task_plan.md`, `findings.md`, `progress.md` |\n\nThis ensures your planning files live alongside your code, not buried in the skill installation folder.\n\n## Quick Start\n\nBefore ANY complex task:\n\n1. **Create `task_plan.md`** in your project — Use [templates\u002Ftask_plan.md](templates\u002Ftask_plan.md) as reference\n2. **Create `findings.md`** in your project — Use [templates\u002Ffindings.md](templates\u002Ffindings.md) as reference\n3. **Create `progress.md`** in your project — Use [templates\u002Fprogress.md](templates\u002Fprogress.md) as reference\n4. **Re-read plan before decisions** — Refreshes goals in attention window\n5. **Update after each phase** — Mark complete, log errors\n\n> **Note:** All three planning files should be created in your current working directory (your project root), not in the skill's installation folder.\n\n## The Core Pattern\n\n```\nContext Window = RAM (volatile, limited)\nFilesystem = Disk (persistent, unlimited)\n\n→ Anything important gets written to disk.\n```\n\n## File Purposes\n\n| File | Purpose | When to Update |\n|------|---------|----------------|\n| `task_plan.md` | Phases, progress, decisions | After each phase |\n| `findings.md` | Research, discoveries | After ANY discovery |\n| `progress.md` | Session log, test results | Throughout session |\n\n## Critical Rules\n\n### 1. Create Plan First\nNever start a complex task without `task_plan.md`. Non-negotiable.\n\n### 2. The 2-Action Rule\n> \"After every 2 view\u002Fbrowser\u002Fsearch operations, IMMEDIATELY save key findings to text files.\"\n\nThis prevents visual\u002Fmultimodal information from being lost.\n\n### 3. Read Before Decide\nBefore major decisions, read the plan file. This keeps goals in your attention window.\n\n### 4. Update After Act\nAfter completing any phase:\n- Mark phase status: `in_progress` → `complete`\n- Log any errors encountered\n- Note files created\u002Fmodified\n\n### 5. Log ALL Errors\nEvery error goes in the plan file. This builds knowledge and prevents repetition.\n\n```markdown\n## Errors Encountered\n| Error | Attempt | Resolution |\n|-------|---------|------------|\n| FileNotFoundError | 1 | Created default config |\n| API timeout | 2 | Added retry logic |\n```\n\n### 6. Never Repeat Failures\n```\nif action_failed:\n    next_action != same_action\n```\nTrack what you tried. Mutate the approach.\n\n## The 3-Strike Error Protocol\n\n```\nATTEMPT 1: Diagnose & Fix\n  → Read error carefully\n  → Identify root cause\n  → Apply targeted fix\n\nATTEMPT 2: Alternative Approach\n  → Same error? Try different method\n  → Different tool? Different library?\n  → NEVER repeat exact same failing action\n\nATTEMPT 3: Broader Rethink\n  → Question assumptions\n  → Search for solutions\n  → Consider updating the plan\n\nAFTER 3 FAILURES: Escalate to User\n  → Explain what you tried\n  → Share the specific error\n  → Ask for guidance\n```\n\n## Read vs Write Decision Matrix\n\n| Situation | Action | Reason |\n|-----------|--------|--------|\n| Just wrote a file | DON'T read | Content still in context |\n| Viewed image\u002FPDF | Write findings NOW | Multimodal → text before lost |\n| Browser returned data | Write to file | Screenshots don't persist |\n| Starting new phase | Read plan\u002Ffindings | Re-orient if context stale |\n| Error occurred | Read relevant file | Need current state to fix |\n| Resuming after gap | Read all planning files | Recover state |\n\n## The 5-Question Reboot Test\n\nIf you can answer these, your context management is solid:\n\n| Question | Answer Source |\n|----------|---------------|\n| Where am I? | Current phase in task_plan.md |\n| Where am I going? | Remaining phases |\n| What's the goal? | Goal statement in plan |\n| What have I learned? | findings.md |\n| What have I done? | progress.md |\n\n## When to Use This Pattern\n\n**Use for:**\n- Multi-step tasks (3+ steps)\n- Research tasks\n- Building\u002Fcreating projects\n- Tasks spanning many tool calls\n- Anything requiring organization\n\n**Skip for:**\n- Simple questions\n- Single-file edits\n- Quick lookups\n\n## Templates\n\nCopy these templates to start:\n\n- [templates\u002Ftask_plan.md](templates\u002Ftask_plan.md) — Phase tracking\n- [templates\u002Ffindings.md](templates\u002Ffindings.md) — Research storage\n- [templates\u002Fprogress.md](templates\u002Fprogress.md) — Session logging\n\n## Scripts\n\nHelper scripts for automation:\n\n- `scripts\u002Finit-session.sh` — Initialize all planning files\n- `scripts\u002Fcheck-complete.sh` — Verify all phases complete\n\n## Advanced Topics\n\n- **Manus Principles:** See [reference.md](reference.md)\n- **Real Examples:** See [examples.md](examples.md)\n\n## Anti-Patterns\n\n| Don't | Do Instead |\n|-------|------------|\n| Use TodoWrite for persistence | Create task_plan.md file |\n| State goals once and forget | Re-read plan before decisions |\n| Hide errors and retry silently | Log errors to plan file |\n| Stuff everything in context | Store large content in files |\n| Start executing immediately | Create plan file FIRST |\n| Repeat failed actions | Track attempts, mutate approach |\n| Create files in skill directory | Create files in your project |\n","# Planning with Files\n\nWork like Manus: Use persistent markdown files as your \"working memory on disk.\"\n\n## Important: Where Files Go\n\nWhen using this skill:\n\n- **Templates** are stored in the skill directory at `${CLAUDE_PLUGIN_ROOT}\u002Ftemplates\u002F`\n- **Your planning files** (`task_plan.md`, `findings.md`, `progress.md`) should be created in **your project directory** — the folder where you're working\n\n| Location | What Goes There |\n|----------|-----------------|\n| Skill directory (`${CLAUDE_PLUGIN_ROOT}\u002F`) | Templates, scripts, reference docs |\n| Your project directory | `task_plan.md`, `findings.md`, `progress.md` |\n\nThis ensures your planning files live alongside your code, not buried in the skill installation folder.\n\n## Quick Start\n\nBefore ANY complex task:\n\n1. **Create `task_plan.md`** in your project — Use [templates\u002Ftask_plan.md](templates\u002Ftask_plan.md) as reference\n2. **Create `findings.md`** in your project — Use [templates\u002Ffindings.md](templates\u002Ffindings.md) as reference\n3. **Create `progress.md`** in your project — Use [templates\u002Fprogress.md](templates\u002Fprogress.md) as reference\n4. **Re-read plan before decisions** — Refreshes goals in attention window\n5. **Update after each phase** — Mark complete, log errors\n\n> **Note:** All three planning files should be created in your current working directory (your project root), not in the skill's installation folder.\n\n## The Core Pattern\n\n```\nContext Window = RAM (volatile, limited)\nFilesystem = Disk (persistent, unlimited)\n\n→ Anything important gets written to disk.\n```\n\n## File Purposes\n\n| File | Purpose | When to Update |\n|------|---------|----------------|\n| `task_plan.md` | Phases, progress, decisions | After each phase |\n| `findings.md` | Research, discoveries | After ANY discovery |\n| `progress.md` | Session log, test results | Throughout session |\n\n## Critical Rules\n\n### 1. Create Plan First\nNever start a complex task without `task_plan.md`. Non-negotiable.\n\n### 2. The 2-Action Rule\n> \"After every 2 view\u002Fbrowser\u002Fsearch operations, IMMEDIATELY save key findings to text files.\"\n\nThis prevents visual\u002Fmultimodal information from being lost.\n\n### 3. Read Before Decide\nBefore major decisions, read the plan file. This keeps goals in your attention window.\n\n### 4. Update After Act\nAfter completing any phase:\n- Mark phase status: `in_progress` → `complete`\n- Log any errors encountered\n- Note files created\u002Fmodified\n\n### 5. Log ALL Errors\nEvery error goes in the plan file. This builds knowledge and prevents repetition.\n\n```markdown\n## Errors Encountered\n| Error | Attempt | Resolution |\n|-------|---------|------------|\n| FileNotFoundError | 1 | Created default config |\n| API timeout | 2 | Added retry logic |\n```\n\n### 6. Never Repeat Failures\n```\nif action_failed:\n    next_action != same_action\n```\nTrack what you tried. Mutate the approach.\n\n## The 3-Strike Error Protocol\n\n```\nATTEMPT 1: Diagnose & Fix\n  → Read error carefully\n  → Identify root cause\n  → Apply targeted fix\n\nATTEMPT 2: Alternative Approach\n  → Same error? Try different method\n  → Different tool? Different library?\n  → NEVER repeat exact same failing action\n\nATTEMPT 3: Broader Rethink\n  → Question assumptions\n  → Search for solutions\n  → Consider updating the plan\n\nAFTER 3 FAILURES: Escalate to User\n  → Explain what you tried\n  → Share the specific error\n  → Ask for guidance\n```\n\n## Read vs Write Decision Matrix\n\n| Situation | Action | Reason |\n|-----------|--------|--------|\n| Just wrote a file | DON'T read | Content still in context |\n| Viewed image\u002FPDF | Write findings NOW | Multimodal → text before lost |\n| Browser returned data | Write to file | Screenshots don't persist |\n| Starting new phase | Read plan\u002Ffindings | Re-orient if context stale |\n| Error occurred | Read relevant file | Need current state to fix |\n| Resuming after gap | Read all planning files | Recover state |\n\n## The 5-Question Reboot Test\n\nIf you can answer these, your context management is solid:\n\n| Question | Answer Source |\n|----------|---------------|\n| Where am I? | Current phase in task_plan.md |\n| Where am I going? | Remaining phases |\n| What's the goal? | Goal statement in plan |\n| What have I learned? | findings.md |\n| What have I done? | progress.md |\n\n## When to Use This Pattern\n\n**Use for:**\n- Multi-step tasks (3+ steps)\n- Research tasks\n- Building\u002Fcreating projects\n- Tasks spanning many tool calls\n- Anything requiring organization\n\n**Skip for:**\n- Simple questions\n- Single-file edits\n- Quick lookups\n\n## Templates\n\nCopy these templates to start:\n\n- [templates\u002Ftask_plan.md](templates\u002Ftask_plan.md) — Phase tracking\n- [templates\u002Ffindings.md](templates\u002Ffindings.md) — Research storage\n- [templates\u002Fprogress.md](templates\u002Fprogress.md) — Session logging\n\n## Scripts\n\nHelper scripts for automation:\n\n- `scripts\u002Finit-session.sh` — Initialize all planning files\n- `scripts\u002Fcheck-complete.sh` — Verify all phases complete\n\n## Advanced Topics\n\n- **Manus Principles:** See [reference.md](reference.md)\n- **Real Examples:** See [examples.md](examples.md)\n\n## Anti-Patterns\n\n| Don't | Do Instead |\n|-------|------------|\n| Use TodoWrite for persistence | Create task_plan.md file |\n| State goals once and forget | Re-read plan before decisions |\n| Hide errors and retry silently | Log errors to plan file |\n| Stuff everything in context | Store large content in files |\n| Start executing immediately | Create plan file FIRST |\n| Repeat failed actions | Track attempts, mutate approach |\n| Create files in skill directory | Create files in your project |\n",{"name":5,"metadata":43,"description":7,"allowed-tools":69},{"hooks":44,"version":67,"user-invocable":68},{"Stop":45,"PreToolUse":50,"PostToolUse":56,"SessionStart":62},[46],{"hooks":47},[48],{"type":32,"command":49},"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fcheck-complete.sh",[51],{"hooks":52,"matcher":55},[53],{"type":32,"command":54},"cat task_plan.md 2>\u002Fdev\u002Fnull | head -30 || true","Write|Edit|Bash",[57],{"hooks":58,"matcher":61},[59],{"type":32,"command":60},"echo '[planning-with-files] File updated. If this completes a phase, update task_plan.md status.'","Write|Edit",[63],{"hooks":64},[65],{"type":32,"command":66},"echo '[planning-with-files] Ready. Auto-activates for complex tasks, or invoke manually with \u002Fplanning-with-files'","2.1.2",true,[70,71,72,35,73,74,75,76],"Read","Write","Edit","Glob","Grep","WebFetch","WebSearch","main","726e1f79b96b0cb3d729d0e55a1c847e0b5353ae","skills\u002Fhuman_authored\u002Forganize-messy-files\u002Fplanning-with-files",7,"https:\u002F\u002Fgithub.com\u002Fcxcscmu\u002FSkillLearnBench","https:\u002F\u002Fcxcscmu.github.io\u002FSkillLearnBench","https:\u002F\u002Fgithub.com\u002Fcxcscmu","2026-10-02 22:55:36",{"source":8,"skillName":5,"commands":86,"prompt":96,"zipAvailable":68},[87,90,93],{"tool":88,"command":89},"npx","npx skills add cxcscmu\u002FSkillLearnBench --skill planning-with-files",{"tool":91,"command":92},"bunx","bunx skills add cxcscmu\u002FSkillLearnBench --skill planning-with-files",{"tool":94,"command":95},"pnpm","pnpm dlx skills add cxcscmu\u002FSkillLearnBench --skill planning-with-files","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcxcscmu\u002FSkillLearnBench\u002Fblob\u002Fmain\u002Fskills\u002Fhuman_authored\u002Forganize-messy-files\u002Fplanning-with-files\u002FSKILL.md",[98,104,108,114,118,122,126],{"path":99,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":103},"examples.md","REFERENCE","参考文档",4426,"https:\u002F\u002Fgithub.com\u002Fcxcscmu\u002FSkillLearnBench\u002Fblob\u002Fmain\u002Fskills\u002Fhuman_authored\u002Forganize-messy-files\u002Fplanning-with-files\u002Fexamples.md",{"path":105,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":106,"sourceHtmlUrl":107},"reference.md",8066,"https:\u002F\u002Fgithub.com\u002Fcxcscmu\u002FSkillLearnBench\u002Fblob\u002Fmain\u002Fskills\u002Fhuman_authored\u002Forganize-messy-files\u002Fplanning-with-files\u002Freference.md",{"path":109,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":112,"sourceHtmlUrl":113},"scripts\u002Fcheck-complete.sh","SCRIPT","脚本",1160,"https:\u002F\u002Fgithub.com\u002Fcxcscmu\u002FSkillLearnBench\u002Fblob\u002Fmain\u002Fskills\u002Fhuman_authored\u002Forganize-messy-files\u002Fplanning-with-files\u002Fscripts\u002Fcheck-complete.sh",{"path":115,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":116,"sourceHtmlUrl":117},"scripts\u002Finit-session.sh",2254,"https:\u002F\u002Fgithub.com\u002Fcxcscmu\u002FSkillLearnBench\u002Fblob\u002Fmain\u002Fskills\u002Fhuman_authored\u002Forganize-messy-files\u002Fplanning-with-files\u002Fscripts\u002Finit-session.sh",{"path":119,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":120,"sourceHtmlUrl":121},"templates\u002Ffindings.md",3553,"https:\u002F\u002Fgithub.com\u002Fcxcscmu\u002FSkillLearnBench\u002Fblob\u002Fmain\u002Fskills\u002Fhuman_authored\u002Forganize-messy-files\u002Fplanning-with-files\u002Ftemplates\u002Ffindings.md",{"path":123,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":124,"sourceHtmlUrl":125},"templates\u002Fprogress.md",3987,"https:\u002F\u002Fgithub.com\u002Fcxcscmu\u002FSkillLearnBench\u002Fblob\u002Fmain\u002Fskills\u002Fhuman_authored\u002Forganize-messy-files\u002Fplanning-with-files\u002Ftemplates\u002Fprogress.md",{"path":127,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":128,"sourceHtmlUrl":129},"templates\u002Ftask_plan.md",4598,"https:\u002F\u002Fgithub.com\u002Fcxcscmu\u002FSkillLearnBench\u002Fblob\u002Fmain\u002Fskills\u002Fhuman_authored\u002Forganize-messy-files\u002Fplanning-with-files\u002Ftemplates\u002Ftask_plan.md",[131,149,172,190,209,221],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":142,"publishedAt":38},"01M6KM5KH175P5ABP5JMX2SBDQ","object_counter","Count occurrences of an object in the image using computer vision algorithm.","https:\u002F\u002Fgithub.com\u002Fcxcscmu\u002FSkillLearnBench\u002Fblob\u002Fmain\u002Fskills\u002Fhuman_authored\u002Fvideo-object-counting\u002Fobject_counter\u002FSKILL.md",[137],{"categoryNo":138,"categoryName":139,"taxonomyType":140,"taxonomyTypeDesc":141},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[143,144,145,146,147,148],"object counter","object","vision","computer","Computer Vision","image",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":158,"publishedAt":38},"01M6KM51TMVXG79MMPCS6Y8G86","travel-planning-workflow","Invoke this skill when performing travel planning. It defines a structured workflow for generating itineraries. Following this workflow is essential to ensure the final plan satisfies user requirements.","https:\u002F\u002Fgithub.com\u002Fcxcscmu\u002FSkillLearnBench\u002Fblob\u002Fmain\u002Fskills\u002Fhuman_authored\u002Ftravel-planning\u002Ftravel-planning-workflow\u002FSKILL.md",[155],{"categoryNo":156,"categoryName":157,"taxonomyType":140,"taxonomyTypeDesc":141},"01JBSEEDCAT000000000000023","Skill与智能体开发",[159,19,160,161,162,163,164,165,34,166,167,168,169,170,171],"workflow","planning workflow","travel","travel planning","travel planning workflow","structured","performing","for","user","it","requirements","essential","itineraries",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":178,"publishedAt":38},"01M6KM4DY820XHS9YTSK5QP5HD","bundled-dataset-search-tool","invoke this skill when you need to perform database search for travel planning. This skill provides some useful pre-packaged tools to look up accommodations, attractions, cities, driving distance, flights, and restaurants from the bundled dataset.","https:\u002F\u002Fgithub.com\u002Fcxcscmu\u002FSkillLearnBench\u002Fblob\u002Fmain\u002Fskills\u002Fhuman_authored\u002Ftravel-planning\u002Fbundled-dataset-search-tool\u002FSKILL.md",[],[179,180,181,182,183,184,185,161,186,187,162,188,166,189,19],"search","tool","dataset","bundled dataset search tool","restaurants","Tools","up","look","flights","you","database",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":196,"publishedAt":38},"01M6KM465BB9PQ0B548HQSVAWZ","glm-output","Output-processing guidance for GLM tasks. Especially useful after glm-basics and glm-calibration when you need verifier-matching metrics from output.nc and a final \u002Froot\u002Fmetrics.json.","https:\u002F\u002Fgithub.com\u002Fcxcscmu\u002FSkillLearnBench\u002Fblob\u002Fmain\u002Fskills\u002Fhuman_authored\u002Ftemperature-simulation\u002Fglm-output\u002FSKILL.md",[],[197,198,199,166,37,200,201,202,203,204,205,206,188,207,208],"glm output","output","glm","metrics","json","basics","guidance","matching","verifier","processing","root","calibration",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":216,"publishedAt":38},"01M6KM40KY3QWDW5W97S39R2BC","glm-calibration","Calibration guidance for GLM tasks. Often most effective after glm-basics has clarified the setup; glm-output is the companion skill for exact final metric computation.","https:\u002F\u002Fgithub.com\u002Fcxcscmu\u002FSkillLearnBench\u002Fblob\u002Fmain\u002Fskills\u002Fhuman_authored\u002Ftemperature-simulation\u002Fglm-calibration\u002FSKILL.md",[215],{"categoryNo":156,"categoryName":157,"taxonomyType":140,"taxonomyTypeDesc":141},[217,208,199,198,203,202,37,218,219,166,220],"glm calibration","setup","companion","metric",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":227,"publishedAt":38},"01M6KM3VHHVSGMGHJQB3PPT6YG","glm-basics","A good starting point for GLM calibration tasks. Use to inspect glm3.nml, confirm how GLM runs, and identify the relevant files before moving on to calibration and output evaluation.","https:\u002F\u002Fgithub.com\u002Fcxcscmu\u002FSkillLearnBench\u002Fblob\u002Fmain\u002Fskills\u002Fhuman_authored\u002Ftemperature-simulation\u002Fglm-basics\u002FSKILL.md",[],[228,199,202,229,217,208,166,198,230,21,231,232,233,234,37],"glm basics","inspect","relevant","good","use","how","Evaluation"]