[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASV202A1DQ84CS94MP637N":3,"skill-same:01M7ASV202A1DQ84CS94MP637N":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7ASV202A1DQ84CS94MP637N","project-status-maintenance",null,"Maintain or create PROJECT_STATUS.md files at the repository root with the canonical structure (Executive Summary, Completed Components, In Progress, Next Steps, Known Issues, Notes). Use when starting or finishing work on a project, when the user asks to update or create PROJECT_STATUS.md, when a session involves significant changes that should be reflected in the project status file, or when reviewing project state before committing.","saski\u002Farnesto","saski","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F140356?v=4","01M7ASBDSNXTRYDYB4K1PEA1RV","01M7ASBDTAKBDAAV99S1GE7HK6",6,"Unlicense","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproject-status-maintenance\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: project-status-maintenance\ndescription: Maintain or create PROJECT_STATUS.md files at the repository root with the canonical structure (Executive Summary, Completed Components, In Progress, Next Steps, Known Issues, Notes). Use when starting or finishing work on a project, when the user asks to update or create PROJECT_STATUS.md, when a session involves significant changes that should be reflected in the project status file, or when reviewing project state before committing.\n---\n\n# Project Status Maintenance\n\nEvery active project repository should maintain a `PROJECT_STATUS.md` at the root level. It is a living document tracking current state, completed work, and next steps.\n\n## When to update\n\nUpdate `PROJECT_STATUS.md` after any significant change: new features, bug fixes, tests added, dependencies changed, documentation modified, project structure changes. Do not let it drift — outdated status files are worse than no file.\n\n## Canonical template\n\nUse this structure when creating or rewriting `PROJECT_STATUS.md`:\n\n```markdown\n# [Project Name] - Project Status\n\n**Last Updated**: YYYY-MM-DD\n**Overall Status**: [Status Emoji] **[Percentage]% Complete** - [Brief Status]\n\n---\n\n## Executive Summary\n\n| Component | Status | Progress | Blocking |\n|-----------|--------|----------|----------|\n| Component 1 | ✅ Complete | 100% | - |\n| Component 2 | 🟡 In Progress | 50% | - |\n| Component 3 | ⚠️ Pending | 0% | No |\n\n**Current Readiness**: [Status] - [Brief description]\n\n---\n\n## ✅ Completed Components\n\n[List of completed work with dates and details]\n\n---\n\n## 🚧 In Progress\n\n[Current work items with progress indicators]\n\n---\n\n## 📋 Next Steps\n\n1. [First priority task]\n2. [Second priority task]\n3. [Third priority task]\n\n---\n\n## 🐛 Known Issues\n\n[Any known bugs or limitations]\n\n---\n\n## 📝 Notes\n\n[Additional context, decisions, or important information]\n```\n\n## Status indicators\n\nUse consistent indicators across the file:\n\n- **✅ Complete** — finished and tested\n- **🟡 In Progress** — actively being worked on\n- **⚠️ Pending** — planned but not started\n- **🟢 Ready** — ready for next phase\n- **🔴 Blocked** — blocked by dependencies or issues\n- **❌ Cancelled** — planned but cancelled\n\n## Update process\n\n1. Update the **Last Updated** date.\n2. Refresh the **Overall Status** percentage and brief description.\n3. Move items from **In Progress** to **Completed Components** when done.\n4. Update progress percentages for in-progress work.\n5. Revise **Next Steps** based on current priorities.\n6. Add any new issues to **Known Issues**.\n7. Document significant decisions in **Notes**.\n\n## Best practices\n\n- **Be specific**: include dates, commit hashes, or PR numbers when relevant.\n- **Be honest**: do not inflate progress percentages.\n- **Be actionable**: next steps should be clear and prioritized.\n- **Be concise**: keep it readable, not exhaustive.\n- **Be current**: update regularly, not only at milestones.\n\n## Anti-patterns\n\n- Creating the file but never updating it.\n- Using vague status descriptions.\n- Forgetting to update the **Last Updated** date.\n- Leaving stale information in the file.\n- Making the file too verbose or too sparse.\n\n## Integration with workflow\n\n- Before starting work: review `PROJECT_STATUS.md` to understand current state.\n- During work: update status as progress is made.\n- Before committing: ensure `PROJECT_STATUS.md` reflects the changes in the commit.\n","# Project Status Maintenance\n\nEvery active project repository should maintain a `PROJECT_STATUS.md` at the root level. It is a living document tracking current state, completed work, and next steps.\n\n## When to update\n\nUpdate `PROJECT_STATUS.md` after any significant change: new features, bug fixes, tests added, dependencies changed, documentation modified, project structure changes. Do not let it drift — outdated status files are worse than no file.\n\n## Canonical template\n\nUse this structure when creating or rewriting `PROJECT_STATUS.md`:\n\n```markdown\n# [Project Name] - Project Status\n\n**Last Updated**: YYYY-MM-DD\n**Overall Status**: [Status Emoji] **[Percentage]% Complete** - [Brief Status]\n\n---\n\n## Executive Summary\n\n| Component | Status | Progress | Blocking |\n|-----------|--------|----------|----------|\n| Component 1 | ✅ Complete | 100% | - |\n| Component 2 | 🟡 In Progress | 50% | - |\n| Component 3 | ⚠️ Pending | 0% | No |\n\n**Current Readiness**: [Status] - [Brief description]\n\n---\n\n## ✅ Completed Components\n\n[List of completed work with dates and details]\n\n---\n\n## 🚧 In Progress\n\n[Current work items with progress indicators]\n\n---\n\n## 📋 Next Steps\n\n1. [First priority task]\n2. [Second priority task]\n3. [Third priority task]\n\n---\n\n## 🐛 Known Issues\n\n[Any known bugs or limitations]\n\n---\n\n## 📝 Notes\n\n[Additional context, decisions, or important information]\n```\n\n## Status indicators\n\nUse consistent indicators across the file:\n\n- **✅ Complete** — finished and tested\n- **🟡 In Progress** — actively being worked on\n- **⚠️ Pending** — planned but not started\n- **🟢 Ready** — ready for next phase\n- **🔴 Blocked** — blocked by dependencies or issues\n- **❌ Cancelled** — planned but cancelled\n\n## Update process\n\n1. Update the **Last Updated** date.\n2. Refresh the **Overall Status** percentage and brief description.\n3. Move items from **In Progress** to **Completed Components** when done.\n4. Update progress percentages for in-progress work.\n5. Revise **Next Steps** based on current priorities.\n6. Add any new issues to **Known Issues**.\n7. Document significant decisions in **Notes**.\n\n## Best practices\n\n- **Be specific**: include dates, commit hashes, or PR numbers when relevant.\n- **Be honest**: do not inflate progress percentages.\n- **Be actionable**: next steps should be clear and prioritized.\n- **Be concise**: keep it readable, not exhaustive.\n- **Be current**: update regularly, not only at milestones.\n\n## Anti-patterns\n\n- Creating the file but never updating it.\n- Using vague status descriptions.\n- Forgetting to update the **Last Updated** date.\n- Leaving stale information in the file.\n- Making the file too verbose or too sparse.\n\n## Integration with workflow\n\n- Before starting work: review `PROJECT_STATUS.md` to understand current state.\n- During work: update status as progress is made.\n- Before committing: ensure `PROJECT_STATUS.md` reflects the changes in the commit.\n",{"name":5,"description":7},"main","3c24fc2c035029b08c7326774bee3fef8fb95566",".agents\u002Fskills\u002Fproject-status-maintenance",0,"https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto","https:\u002F\u002Fgithub.com\u002Fsaski","http:\u002F\u002Fsaski.com","2026-11-12 20:09:16",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add saski\u002Farnesto --skill project-status-maintenance",{"tool":37,"command":38},"bunx","bunx skills add saski\u002Farnesto --skill project-status-maintenance",{"tool":40,"command":41},"pnpm","pnpm dlx skills add saski\u002Farnesto --skill project-status-maintenance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproject-status-maintenance\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7AT7F5FSHNAMFMF01N0QA1X","visualize","Use \u002Fvisualize for creating compact charts, diagrams, or other visuals inline as part of the conversation itself. It chooses among Markdown tables, Mermaid, inline HTML, and other supported in-transcript forms. Use Canvas for durable artifacts outside the transcript that users may revisit, refine, or share.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fvisualize\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7AT79MHSAR3JDDMP7DGERM9","update-cursor-settings","Modify Cursor\u002FVSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fupdate-cursor-settings\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7AT73WF3Y22E0FKYAMCCJES","update-cli-config","View and modify Cursor CLI configuration settings in ~\u002F.cursor\u002Fcli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fupdate-cli-config\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7AT6F3FBP85AJJ5BJNR8B5W","statusline","Configure a custom status line in the CLI. Use when the user mentions status line, statusline, statusLine, CLI status bar, prompt footer customization, or wants to add session context above the prompt.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fstatusline\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7AT6D24QFS5XRAFN8S5XJ7W","split-to-prs","Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fsplit-to-prs\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7AT69FYFN84XZKW452JV5DF","shell","Runs the rest of a \u002Fshell request as a literal shell command. Use only when the user explicitly invokes \u002Fshell and wants the following text executed directly in the terminal.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fshell\u002FSKILL.md",[],[]]