[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASM3BCT81B81KVD6B3D0PC":3,"skill-same:01M7ASM3BCT81B81KVD6B3D0PC":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},"01M7ASM3BCT81B81KVD6B3D0PC","graph-colorize",null,"Color-code the Obsidian graph view by rewriting `.obsidian\u002Fgraph.json` colorGroups. Use this skill when the user says \"color my graph\", \"color code obsidian\", \"colorize the graph\", \"color the graph by tag\", \"color by category\", \"highlight visibility in graph\", \"make the graph colorful\", \"distinguish tags in graph\", or wants nodes in Obsidian's graph view tinted by tag, folder, or visibility. Generates a `colorGroups` array from the vault's actual tags\u002Fcategories and merges it into the existing graph.json without clobbering other graph settings. Always backs up first.","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\u002Fgraph-colorize\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: graph-colorize\ndescription: >\n  Color-code the Obsidian graph view by rewriting `.obsidian\u002Fgraph.json` colorGroups.\n  Use this skill when the user says \"color my graph\", \"color code obsidian\", \"colorize\n  the graph\", \"color the graph by tag\", \"color by category\", \"highlight visibility\n  in graph\", \"make the graph colorful\", \"distinguish tags in graph\", or wants nodes\n  in Obsidian's graph view tinted by tag, folder, or visibility. Generates a\n  `colorGroups` array from the vault's actual tags\u002Fcategories and merges it into the\n  existing graph.json without clobbering other graph settings. Always backs up first.\n---\n\n# Graph Colorize — Color-code the Obsidian Graph View\n\nYou are rewriting `$OBSIDIAN_VAULT_PATH\u002F.obsidian\u002Fgraph.json` so Obsidian's graph view tints nodes by tag, folder, or visibility.\n\nObsidian stores graph settings in `\u003Cvault>\u002F.obsidian\u002Fgraph.json`. The `colorGroups` array is a list of `{query, color}` pairs; the first matching query wins per node. Queries use Obsidian's search syntax: `tag:#foo`, `path:\"concepts\"`, `file:foo`, etc. Color is `{\"a\": 1, \"rgb\": \u003Cpacked-int>}` where the int is `(R \u003C\u003C 16) | (G \u003C\u003C 8) | B`.\n\n## Before You Start\n\n1. Read `~\u002F.obsidian-wiki\u002Fconfig`, or fall back to `.env` in this repo, to get `OBSIDIAN_VAULT_PATH`.\n2. Confirm `$OBSIDIAN_VAULT_PATH\u002F.obsidian\u002F` exists. If it doesn't, the vault has never been opened in Obsidian — tell the user to open the vault once in Obsidian, then re-run.\n3. **Warn the user if Obsidian is likely open**: Obsidian overwrites `graph.json` on close. Tell them to close the vault first, or be ready to reload (Cmd\u002FCtrl+R) and not touch the graph settings until they reload.\n\n## Step 1: Pick a Mode\n\nInfer the mode from the user's phrasing. If ambiguous, default to **by-tag**.\n\n| User intent | Mode |\n|---|---|\n| \"color by tag\", \"color my graph\", \"make it colorful\" (default) | `by-tag` |\n| \"color by folder\", \"color by category\", \"color by directory\" | `by-category` |\n| \"highlight visibility\", \"show internal\u002Fpii in graph\", \"visibility colors\" | `by-visibility` |\n| User provides explicit mapping (`tag:#foo = red`, or JSON blob) | `custom` |\n| \"combine tag and visibility\" \u002F \"both\" | `combined` (visibility first, then tag) |\n\n## Step 2: Build the `colorGroups` Array\n\n### Palette (10 distinct, colorblind-friendly colors)\n\nUse in order. If more groups than colors, cycle and add a lightness shift by dividing brightness ~20% via a second pass — or just cap at 10 and tell the user the remaining tags share the \"other\" color.\n\n| # | Hex | rgb (packed int) | Role |\n|---|---|---|---|\n| 0 | `#4E79A7` | `5142951` | blue |\n| 1 | `#F28E2B` | `15896107` | orange |\n| 2 | `#E15759` | `14767961` | red |\n| 3 | `#76B7B2` | `7780786` | teal |\n| 4 | `#59A14F` | `5873999` | green |\n| 5 | `#EDC948` | `15583048` | yellow |\n| 6 | `#B07AA1` | `11565217` | purple |\n| 7 | `#FF9DA7` | `16751527` | pink |\n| 8 | `#9C755F` | `10253663` | brown |\n| 9 | `#BAB0AC` | `12234924` | gray |\n\nEvery color is wrapped as `{\"a\": 1, \"rgb\": \u003Cint>}`.\n\n### Mode: `by-tag`\n\n1. Glob `$VAULT_PATH\u002F**\u002F*.md` excluding `_archives\u002F`, `_raw\u002F`, `.obsidian\u002F`, `node_modules\u002F`, `index.md`, `log.md`, `_insights.md`.\n2. Parse frontmatter `tags` from each page. Count usage per tag.\n3. **Drop `visibility\u002F*` tags** from the frequency list — they are reserved system tags, handled only in `by-visibility` or `combined` mode.\n4. Take the top 10 tags by usage. If there are fewer than 10 unique tags, use all of them.\n5. For each tag `T` at index `i`: emit `{\"query\": \"tag:#T\", \"color\": palette[i]}`.\n6. Optionally, append a final catch-all entry for untagged pages at the end: `{\"query\": \"-[\\\"tag\\\":]\", \"color\": palette[9]}` — **skip** if color slot 9 is already taken by a real tag.\n\n### Mode: `by-category`\n\nUse the seven vault top-level folders in this fixed order so colors are stable across runs:\n\n| Folder | Color index |\n|---|---|\n| `concepts` | 0 (blue) |\n| `entities` | 1 (orange) |\n| `skills` | 2 (red) |\n| `references` | 3 (teal) |\n| `synthesis` | 4 (green) |\n| `projects` | 5 (yellow) |\n| `journal` | 6 (purple) |\n\nEmit one entry per folder that exists AND contains at least one `.md` file. Each entry is:\n\n```json\n{\"query\": \"path:\\\"\u003Cfolder>\\\"\", \"color\": {\"a\": 1, \"rgb\": \u003Cint>}}\n```\n\n### Mode: `by-visibility`\n\nEmit exactly three entries, in this order (first-match wins, so most restrictive comes first):\n\n1. `visibility\u002Fpii` → `#E15759` (red, rgb 14767961)\n2. `visibility\u002Finternal` → `#F28E2B` (orange, rgb 15896107)\n3. `visibility\u002Fpublic` → `#59A14F` (green, rgb 5873999)\n\n```json\n{\"query\": \"tag:#visibility\u002Fpii\", \"color\": {\"a\": 1, \"rgb\": 14767961}}\n```\n\nPages with no `visibility\u002F` tag remain Obsidian's default color — do not add a catch-all.\n\n### Mode: `combined`\n\nEmit `by-visibility` entries first, then `by-tag` entries. Visibility wins on conflict because it appears first in the list.\n\n### Mode: `custom`\n\nIf the user gave explicit mappings, honor them literally. Convert any hex they give (e.g. `#FF00FF`) to packed int using `int(hex_without_hash, 16)`. Wrap each as `{\"a\": 1, \"rgb\": \u003Cint>}`.\n\n## Step 3: Merge into graph.json (Do Not Clobber)\n\n1. Read the existing `$VAULT_PATH\u002F.obsidian\u002Fgraph.json`. If it doesn't exist, start from this minimal default:\n\n   ```json\n   {\n     \"collapse-filter\": true,\n     \"search\": \"\",\n     \"showTags\": false,\n     \"showAttachments\": false,\n     \"hideUnresolved\": false,\n     \"showOrphans\": true,\n     \"collapse-color-groups\": false,\n     \"colorGroups\": [],\n     \"collapse-display\": true,\n     \"showArrow\": false,\n     \"textFadeMultiplier\": 0,\n     \"nodeSizeMultiplier\": 1,\n     \"lineSizeMultiplier\": 1,\n     \"collapse-forces\": true,\n     \"centerStrength\": 0.518713248970312,\n     \"repelStrength\": 10,\n     \"linkStrength\": 1,\n     \"linkDistance\": 250,\n     \"scale\": 1,\n     \"close\": true\n   }\n   ```\n\n2. **Back up first**: copy the existing file to `.obsidian\u002Fgraph.json.backup-\u003CYYYYMMDD-HHMM>` before writing. If a backup from the same minute exists, reuse it — don't pile up duplicates.\n\n3. Replace **only** the `colorGroups` field with your new array. Leave every other field untouched. This preserves the user's zoom, physics, filter, search, and display preferences.\n\n4. Write the file back with the same JSON style as the original (usually compact single-line or 2-space indent — preserve what's there).\n\n## Step 4: Report and Log\n\nPrint a summary like:\n\n```\nGraph colorized → .obsidian\u002Fgraph.json\n  Mode:    by-tag\n  Groups:  7 color assignments\n  Palette: blue, orange, red, teal, green, yellow, purple\n  Backup:  .obsidian\u002Fgraph.json.backup-20260424-1432\n\nReload Obsidian (Cmd\u002FCtrl+R) to see the new colors.\nIf Obsidian is currently open, close it first OR reload immediately — Obsidian\noverwrites graph.json on close and can erase these changes.\n```\n\nAppend to `$VAULT_PATH\u002Flog.md`:\n\n```\n- [TIMESTAMP] GRAPH_COLORIZE mode=\u003Cmode> groups=\u003CN> backup=graph.json.backup-\u003Cstamp>\n```\n\n## Edge Cases\n\n- **No tags in vault** in `by-tag` mode → fall back to `by-category` and tell the user.\n- **User wants to undo** → restore from the latest `graph.json.backup-*` and note that in `log.md`.\n- **User wants to clear all color groups** → set `colorGroups: []`, back up, log as `GRAPH_COLORIZE mode=clear`.\n- **`.obsidian\u002F` missing** → the vault hasn't been opened in Obsidian yet. Tell the user to open it once, then re-run. Don't create `.obsidian\u002F` yourself — Obsidian populates many files there on first open.\n- **Query syntax gotchas**: folder paths with spaces need quoting (`path:\"my folder\"`); tags with nested slashes work literally (`tag:#visibility\u002Finternal`); don't URL-encode.\n- **Obsidian open during edit**: surface the risk — Obsidian reads graph.json at startup and **rewrites it on close**. If the user is editing live, tell them to close Obsidian first or run the reload (Cmd\u002FCtrl+R) immediately and avoid opening graph settings before they do.\n\n## Notes\n\n- This is a pure config edit — no page content changes, no frontmatter writes.\n- Re-running is safe: each run creates a new backup, only `colorGroups` is rewritten.\n- If the user has manually curated color groups they want to keep, offer `combined` mode or ask before overwriting.\n- The palette here matches `wiki-export`'s `graph.html` community colors, so the Obsidian graph and the exported visualization look consistent.\n","# Graph Colorize — Color-code the Obsidian Graph View\n\nYou are rewriting `$OBSIDIAN_VAULT_PATH\u002F.obsidian\u002Fgraph.json` so Obsidian's graph view tints nodes by tag, folder, or visibility.\n\nObsidian stores graph settings in `\u003Cvault>\u002F.obsidian\u002Fgraph.json`. The `colorGroups` array is a list of `{query, color}` pairs; the first matching query wins per node. Queries use Obsidian's search syntax: `tag:#foo`, `path:\"concepts\"`, `file:foo`, etc. Color is `{\"a\": 1, \"rgb\": \u003Cpacked-int>}` where the int is `(R \u003C\u003C 16) | (G \u003C\u003C 8) | B`.\n\n## Before You Start\n\n1. Read `~\u002F.obsidian-wiki\u002Fconfig`, or fall back to `.env` in this repo, to get `OBSIDIAN_VAULT_PATH`.\n2. Confirm `$OBSIDIAN_VAULT_PATH\u002F.obsidian\u002F` exists. If it doesn't, the vault has never been opened in Obsidian — tell the user to open the vault once in Obsidian, then re-run.\n3. **Warn the user if Obsidian is likely open**: Obsidian overwrites `graph.json` on close. Tell them to close the vault first, or be ready to reload (Cmd\u002FCtrl+R) and not touch the graph settings until they reload.\n\n## Step 1: Pick a Mode\n\nInfer the mode from the user's phrasing. If ambiguous, default to **by-tag**.\n\n| User intent | Mode |\n|---|---|\n| \"color by tag\", \"color my graph\", \"make it colorful\" (default) | `by-tag` |\n| \"color by folder\", \"color by category\", \"color by directory\" | `by-category` |\n| \"highlight visibility\", \"show internal\u002Fpii in graph\", \"visibility colors\" | `by-visibility` |\n| User provides explicit mapping (`tag:#foo = red`, or JSON blob) | `custom` |\n| \"combine tag and visibility\" \u002F \"both\" | `combined` (visibility first, then tag) |\n\n## Step 2: Build the `colorGroups` Array\n\n### Palette (10 distinct, colorblind-friendly colors)\n\nUse in order. If more groups than colors, cycle and add a lightness shift by dividing brightness ~20% via a second pass — or just cap at 10 and tell the user the remaining tags share the \"other\" color.\n\n| # | Hex | rgb (packed int) | Role |\n|---|---|---|---|\n| 0 | `#4E79A7` | `5142951` | blue |\n| 1 | `#F28E2B` | `15896107` | orange |\n| 2 | `#E15759` | `14767961` | red |\n| 3 | `#76B7B2` | `7780786` | teal |\n| 4 | `#59A14F` | `5873999` | green |\n| 5 | `#EDC948` | `15583048` | yellow |\n| 6 | `#B07AA1` | `11565217` | purple |\n| 7 | `#FF9DA7` | `16751527` | pink |\n| 8 | `#9C755F` | `10253663` | brown |\n| 9 | `#BAB0AC` | `12234924` | gray |\n\nEvery color is wrapped as `{\"a\": 1, \"rgb\": \u003Cint>}`.\n\n### Mode: `by-tag`\n\n1. Glob `$VAULT_PATH\u002F**\u002F*.md` excluding `_archives\u002F`, `_raw\u002F`, `.obsidian\u002F`, `node_modules\u002F`, `index.md`, `log.md`, `_insights.md`.\n2. Parse frontmatter `tags` from each page. Count usage per tag.\n3. **Drop `visibility\u002F*` tags** from the frequency list — they are reserved system tags, handled only in `by-visibility` or `combined` mode.\n4. Take the top 10 tags by usage. If there are fewer than 10 unique tags, use all of them.\n5. For each tag `T` at index `i`: emit `{\"query\": \"tag:#T\", \"color\": palette[i]}`.\n6. Optionally, append a final catch-all entry for untagged pages at the end: `{\"query\": \"-[\\\"tag\\\":]\", \"color\": palette[9]}` — **skip** if color slot 9 is already taken by a real tag.\n\n### Mode: `by-category`\n\nUse the seven vault top-level folders in this fixed order so colors are stable across runs:\n\n| Folder | Color index |\n|---|---|\n| `concepts` | 0 (blue) |\n| `entities` | 1 (orange) |\n| `skills` | 2 (red) |\n| `references` | 3 (teal) |\n| `synthesis` | 4 (green) |\n| `projects` | 5 (yellow) |\n| `journal` | 6 (purple) |\n\nEmit one entry per folder that exists AND contains at least one `.md` file. Each entry is:\n\n```json\n{\"query\": \"path:\\\"\u003Cfolder>\\\"\", \"color\": {\"a\": 1, \"rgb\": \u003Cint>}}\n```\n\n### Mode: `by-visibility`\n\nEmit exactly three entries, in this order (first-match wins, so most restrictive comes first):\n\n1. `visibility\u002Fpii` → `#E15759` (red, rgb 14767961)\n2. `visibility\u002Finternal` → `#F28E2B` (orange, rgb 15896107)\n3. `visibility\u002Fpublic` → `#59A14F` (green, rgb 5873999)\n\n```json\n{\"query\": \"tag:#visibility\u002Fpii\", \"color\": {\"a\": 1, \"rgb\": 14767961}}\n```\n\nPages with no `visibility\u002F` tag remain Obsidian's default color — do not add a catch-all.\n\n### Mode: `combined`\n\nEmit `by-visibility` entries first, then `by-tag` entries. Visibility wins on conflict because it appears first in the list.\n\n### Mode: `custom`\n\nIf the user gave explicit mappings, honor them literally. Convert any hex they give (e.g. `#FF00FF`) to packed int using `int(hex_without_hash, 16)`. Wrap each as `{\"a\": 1, \"rgb\": \u003Cint>}`.\n\n## Step 3: Merge into graph.json (Do Not Clobber)\n\n1. Read the existing `$VAULT_PATH\u002F.obsidian\u002Fgraph.json`. If it doesn't exist, start from this minimal default:\n\n   ```json\n   {\n     \"collapse-filter\": true,\n     \"search\": \"\",\n     \"showTags\": false,\n     \"showAttachments\": false,\n     \"hideUnresolved\": false,\n     \"showOrphans\": true,\n     \"collapse-color-groups\": false,\n     \"colorGroups\": [],\n     \"collapse-display\": true,\n     \"showArrow\": false,\n     \"textFadeMultiplier\": 0,\n     \"nodeSizeMultiplier\": 1,\n     \"lineSizeMultiplier\": 1,\n     \"collapse-forces\": true,\n     \"centerStrength\": 0.518713248970312,\n     \"repelStrength\": 10,\n     \"linkStrength\": 1,\n     \"linkDistance\": 250,\n     \"scale\": 1,\n     \"close\": true\n   }\n   ```\n\n2. **Back up first**: copy the existing file to `.obsidian\u002Fgraph.json.backup-\u003CYYYYMMDD-HHMM>` before writing. If a backup from the same minute exists, reuse it — don't pile up duplicates.\n\n3. Replace **only** the `colorGroups` field with your new array. Leave every other field untouched. This preserves the user's zoom, physics, filter, search, and display preferences.\n\n4. Write the file back with the same JSON style as the original (usually compact single-line or 2-space indent — preserve what's there).\n\n## Step 4: Report and Log\n\nPrint a summary like:\n\n```\nGraph colorized → .obsidian\u002Fgraph.json\n  Mode:    by-tag\n  Groups:  7 color assignments\n  Palette: blue, orange, red, teal, green, yellow, purple\n  Backup:  .obsidian\u002Fgraph.json.backup-20260424-1432\n\nReload Obsidian (Cmd\u002FCtrl+R) to see the new colors.\nIf Obsidian is currently open, close it first OR reload immediately — Obsidian\noverwrites graph.json on close and can erase these changes.\n```\n\nAppend to `$VAULT_PATH\u002Flog.md`:\n\n```\n- [TIMESTAMP] GRAPH_COLORIZE mode=\u003Cmode> groups=\u003CN> backup=graph.json.backup-\u003Cstamp>\n```\n\n## Edge Cases\n\n- **No tags in vault** in `by-tag` mode → fall back to `by-category` and tell the user.\n- **User wants to undo** → restore from the latest `graph.json.backup-*` and note that in `log.md`.\n- **User wants to clear all color groups** → set `colorGroups: []`, back up, log as `GRAPH_COLORIZE mode=clear`.\n- **`.obsidian\u002F` missing** → the vault hasn't been opened in Obsidian yet. Tell the user to open it once, then re-run. Don't create `.obsidian\u002F` yourself — Obsidian populates many files there on first open.\n- **Query syntax gotchas**: folder paths with spaces need quoting (`path:\"my folder\"`); tags with nested slashes work literally (`tag:#visibility\u002Finternal`); don't URL-encode.\n- **Obsidian open during edit**: surface the risk — Obsidian reads graph.json at startup and **rewrites it on close**. If the user is editing live, tell them to close Obsidian first or run the reload (Cmd\u002FCtrl+R) immediately and avoid opening graph settings before they do.\n\n## Notes\n\n- This is a pure config edit — no page content changes, no frontmatter writes.\n- Re-running is safe: each run creates a new backup, only `colorGroups` is rewritten.\n- If the user has manually curated color groups they want to keep, offer `combined` mode or ask before overwriting.\n- The palette here matches `wiki-export`'s `graph.html` community colors, so the Obsidian graph and the exported visualization look consistent.\n",{"name":5,"description":7},"main","3c24fc2c035029b08c7326774bee3fef8fb95566",".agents\u002Fskills\u002Fgraph-colorize",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 graph-colorize",{"tool":37,"command":38},"bunx","bunx skills add saski\u002Farnesto --skill graph-colorize",{"tool":40,"command":41},"pnpm","pnpm dlx skills add saski\u002Farnesto --skill graph-colorize","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgraph-colorize\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",[],[]]