[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75W2FJXVS80NTAQGETPB53R":3,"skill-same:01M75W2FJXVS80NTAQGETPB53R":48},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M75W2FJXVS80NTAQGETPB53R","gitnexus-guide",null,"Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: \"What GitNexus tools are available?\", \"How do I use GitNexus?\"","PyModel\u002Fpythinker-code","PyModel","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F316629828?v=4","01M75W0KV82C1WDD31FBA5P1G6","pymodel","01M75W0KVYQADNDDQG70WHT35B",29,"MIT","https:\u002F\u002Fgithub.com\u002FPyModel\u002Fpythinker-code\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgitnexus\u002Fgitnexus-guide\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: gitnexus-guide\ndescription: \"Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: \\\"What GitNexus tools are available?\\\", \\\"How do I use GitNexus?\\\"\"\n---\n\n# GitNexus Guide\n\nQuick reference for all GitNexus MCP tools, resources, and the knowledge graph schema.\n\n## Always Start Here\n\nFor any task involving code understanding, debugging, impact analysis, or refactoring:\n\n1. **Read `gitnexus:\u002F\u002Frepo\u002F{name}\u002Fcontext`** — codebase overview + check index freshness\n2. **Match your task to a skill below** and **read that skill file**\n3. **Follow the skill's workflow and checklist**\n\n> If step 1 warns the index is stale, run `node .gitnexus\u002Frun.cjs analyze` in the terminal first.\n\n## Skills\n\n| Task                                         | Skill to read       |\n| -------------------------------------------- | ------------------- |\n| Understand architecture \u002F \"How does X work?\" | `gitnexus-exploring`         |\n| Blast radius \u002F \"What breaks if I change X?\"  | `gitnexus-impact-analysis`   |\n| Trace bugs \u002F \"Why is X failing?\"             | `gitnexus-debugging`         |\n| Rename \u002F extract \u002F split \u002F refactor          | `gitnexus-refactoring`       |\n| Tools, resources, schema reference           | `gitnexus-guide` (this file) |\n| Index, status, clean, wiki CLI commands      | `gitnexus-cli`               |\n\n## Tools Reference\n\n| Tool             | What it gives you                                                        |\n| ---------------- | ------------------------------------------------------------------------ |\n| `query`          | Process-grouped code intelligence — execution flows related to a concept |\n| `context`        | 360-degree symbol view — categorized refs, processes it participates in  |\n| `impact`         | Symbol blast radius — what breaks at depth 1\u002F2\u002F3 with confidence         |\n| `trace`          | Shortest path between two symbols — \"how does A reach B?\" in one call     |\n| `detect_changes` | Git-diff impact — what do your current changes affect                    |\n| `rename`         | Multi-file coordinated rename with confidence-tagged edits               |\n| `cypher`         | Raw graph queries (read `gitnexus:\u002F\u002Frepo\u002F{name}\u002Fschema` first)           |\n| `explain`        | Persisted taint findings — source→sink data flows (needs `analyze --pdg`) |\n| `pdg_query`      | Control\u002Fdata dependence — what gates X (CDG) \u002F where Y flows (REACHING_DEF); needs `analyze --pdg` |\n| `check`          | Check graph invariants such as circular imports                          |\n| `route_map`      | API route map — which components\u002Fhooks fetch which endpoints, and the handler files that serve them |\n| `shape_check`    | Response-shape drift — keys each route returns vs keys its consumers access (flags MISMATCH) |\n| `api_impact`     | Pre-change report for an API route — consumers, middleware, shape mismatches, risk level |\n| `tool_map`       | MCP\u002FRPC tool definitions and the files that handle them                  |\n| `group_list`     | List configured multi-repo groups, or one group's config                 |\n| `group_sync`     | Rebuild a group's Contract Registry (cross-repo HTTP contract links); run after `group.yaml` changes or member re-index |\n| `list_repos`     | Discover indexed repos (paginated — `limit`\u002F`offset`)                    |\n\n### Paginating `list_repos`\n\n`list_repos` is paginated so a large registry is not truncated by MCP\u002FLLM token limits. It takes optional `limit` (default **50**, max **200**) and `offset`, and returns:\n\n```jsonc\n{\n  \"repositories\": [\n    { \"name\": \"...\", \"path\": \"...\", \"indexedAt\": \"...\", \"lastCommit\": \"...\", \"stats\": { } }\n  ],\n  \"pagination\": {\n    \"total\": 437,\n    \"limit\": 50,\n    \"offset\": 0,\n    \"returned\": 50,\n    \"hasMore\": true,\n    \"nextOffset\": 50\n  }\n}\n```\n\nTo enumerate **every** repository, keep calling with `offset` set to `pagination.nextOffset` until `hasMore` is `false`:\n\n```text\nlist_repos {}               → repos 1–50,    nextOffset 50,  hasMore true\nlist_repos { offset: 50 }   → repos 51–100,  nextOffset 100, hasMore true\n…\nlist_repos { offset: 400 }  → repos 401–437,                 hasMore false   (done)\n```\n\nNotes: `offset` ≥ `total` returns an empty page (with `total` still reported). Out-of-range or malformed `limit`\u002F`offset` (non-integer, `limit` outside `[1, 200]`, `offset \u003C 0`) are rejected with a clear error — `limit` above the max is rejected, not silently capped. The order is deterministic (lower-cased name, then path), so paging never skips or duplicates an entry while the registry is unchanged.\n\n### Taint findings (`explain`)\n\n`explain` returns taint findings recorded by `gitnexus analyze --pdg` — intra-procedural `TAINTED` edges plus cross-function `TAINT_PATH` hops where the interprocedural taint phase found a function-level source→sink chain. Each finding includes a sink category (command-injection, code-injection, path-traversal, sql-injection, xss), source\u002Fsink lines, and the ordered hop path with the variable carried on each hop.\n\n- `explain {}` — enumerate all findings for the repo (bounded by `limit`, deterministic order)\n- `explain { target: \"src\u002Fvuln.ts\" }` — findings in a file (suffix path match accepted)\n- `explain { target: \"runUserCommand\" }` — findings in a function (resolved like `context`; ambiguous names return ranked candidates)\n\nA repo indexed without `--pdg` returns a clear \"no taint layer\" note. Caveats: closure\u002Fcallback, property\u002Ffield, and implicit flows are not modeled, and interprocedural findings are function-level `TAINT_PATH` hops rather than statement-level path proof, so the absence of a finding is **not** proof of safety. `SANITIZES` (sanitizer-kill) edges are queryable via `cypher`.\n\n### Control & data dependence (`pdg_query`)\n\n`pdg_query` reads the control\u002Fdata-dependence layers `gitnexus analyze --pdg` records (CDG + REACHING_DEF, basic-block granular) — the control\u002Fdata analog of `explain`. It is **always anchored** (a `target` file path or symbol, resolved like `context`) and has two modes:\n\n- `pdg_query { mode: \"controls\", target: \"...\" }` — CDG: \"under what condition does X run?\". Each edge is a controlling predicate block → dependent block with the branch sense (`'T'`\u002F`'F'`) in `reason`; an edge into an early `return`\u002F`throw` is flagged `guard: true` (guard-clause discovery — the sense depends on the predicate, so don't filter guards by a fixed label).\n- `pdg_query { mode: \"flows\", target: \"...\", variable?: \"...\" }` — REACHING_DEF def→use edges within the function; pass `variable` to trace one binding.\n\nA repo indexed without `--pdg` returns a \"no PDG layer\" note (or \"status unknown\" when the layer can't be confirmed). Intra-procedural only — cross-function flow is taint's domain (`explain`). The raw CDG\u002FREACHING_DEF edges are also queryable via `cypher`. See the `gitnexus-pdg-query` skill for the full query surface.\n\n### Shortest path between two symbols (`trace`)\n\n`trace` answers \"how does A reach B?\" in one call — the shortest directed path over `CALLS` (plus `HAS_METHOD`, so a class-rooted trace descends into its methods) instead of chaining 3–8 `context`\u002F`impact` hops by hand.\n\n- `trace { from: \"validateUser\", to: \"executeQuery\" }` — shortest path between two symbols.\n- Disambiguate common names with `from_uid`\u002F`to_uid` (zero-ambiguity) or `from_file`\u002F`to_file`; an ambiguous name returns ranked candidates.\n- `maxDepth` (default 10, max 30) bounds the search; `includeTests` (default false) lets the traversal pass through test-file symbols.\n\nReturns ordered `hops` (each `{ name, filePath, startLine }`) and an aligned `edges[]` of `{ relType, confidence }`, so call hops and containment (`HAS_METHOD`) hops stay distinguishable. When no path exists it reports the **furthest** reachable node (where the chain breaks) and sets `truncated: true` if a traversal cap was hit first. Every result carries a `status`: `ok` \u002F `no_path` \u002F `ambiguous` \u002F `not_found` \u002F `error`.\n\nCross-repo (experimental): pass `repo: \"@groupName\"` to trace across a group's member repos — the path may cross **one** `ContractLink` boundary (reported as a `CONTRACT_LINK` hop with the bridged contract in `crossings[]`). Omit `to` entirely to follow `from`'s outgoing HTTP call to whatever provider endpoint it lands on. Groups are configured via `group_list` \u002F `group_sync`.\n\n## Resources Reference\n\nLightweight reads (~100-500 tokens) for navigation:\n\n| Resource                                       | Content                                   |\n| ---------------------------------------------- | ----------------------------------------- |\n| `gitnexus:\u002F\u002Frepo\u002F{name}\u002Fcontext`               | Stats, staleness check                    |\n| `gitnexus:\u002F\u002Frepo\u002F{name}\u002Fclusters`              | All functional areas with cohesion scores |\n| `gitnexus:\u002F\u002Frepo\u002F{name}\u002Fcluster\u002F{clusterName}` | Area members                              |\n| `gitnexus:\u002F\u002Frepo\u002F{name}\u002Fprocesses`             | All execution flows                       |\n| `gitnexus:\u002F\u002Frepo\u002F{name}\u002Fprocess\u002F{processName}` | Step-by-step trace                        |\n| `gitnexus:\u002F\u002Frepo\u002F{name}\u002Fschema`                | Graph schema for Cypher                   |\n\n## Graph Schema\n\n**Nodes:** File, Folder, Function, Class, Interface, Method, CodeElement, Community, Process, Route, Tool, plus language-specific types (Struct, Enum, Trait, Impl, Namespace, Module, …) and BasicBlock (`--pdg` indexes only). The full node list lives in `gitnexus:\u002F\u002Frepo\u002F{name}\u002Fschema`.\n**Edges (via CodeRelation.type):** CALLS, IMPORTS, EXTENDS, IMPLEMENTS, DEFINES, CONTAINS, MEMBER_OF, HAS_METHOD, HAS_PROPERTY, ACCESSES, METHOD_OVERRIDES, METHOD_IMPLEMENTS, STEP_IN_PROCESS, HANDLES_ROUTE, FETCHES, HANDLES_TOOL, ENTRY_POINT_OF, WRAPS, QUERIES, INJECTS, plus `--pdg`-only types (CFG, REACHING_DEF, TAINTED, SANITIZES, TAINT_PATH, CDG — zero rows on a default index).\n\nRead `gitnexus:\u002F\u002Frepo\u002F{name}\u002Fschema` before writing Cypher — it is the authoritative schema for the indexed repo.\n\n```cypher\nMATCH (caller)-[:CodeRelation {type: 'CALLS'}]->(f:Function {name: \"myFunc\"})\nRETURN caller.name, caller.filePath\n```\n","# GitNexus Guide\n\nQuick reference for all GitNexus MCP tools, resources, and the knowledge graph schema.\n\n## Always Start Here\n\nFor any task involving code understanding, debugging, impact analysis, or refactoring:\n\n1. **Read `gitnexus:\u002F\u002Frepo\u002F{name}\u002Fcontext`** — codebase overview + check index freshness\n2. **Match your task to a skill below** and **read that skill file**\n3. **Follow the skill's workflow and checklist**\n\n> If step 1 warns the index is stale, run `node .gitnexus\u002Frun.cjs analyze` in the terminal first.\n\n## Skills\n\n| Task                                         | Skill to read       |\n| -------------------------------------------- | ------------------- |\n| Understand architecture \u002F \"How does X work?\" | `gitnexus-exploring`         |\n| Blast radius \u002F \"What breaks if I change X?\"  | `gitnexus-impact-analysis`   |\n| Trace bugs \u002F \"Why is X failing?\"             | `gitnexus-debugging`         |\n| Rename \u002F extract \u002F split \u002F refactor          | `gitnexus-refactoring`       |\n| Tools, resources, schema reference           | `gitnexus-guide` (this file) |\n| Index, status, clean, wiki CLI commands      | `gitnexus-cli`               |\n\n## Tools Reference\n\n| Tool             | What it gives you                                                        |\n| ---------------- | ------------------------------------------------------------------------ |\n| `query`          | Process-grouped code intelligence — execution flows related to a concept |\n| `context`        | 360-degree symbol view — categorized refs, processes it participates in  |\n| `impact`         | Symbol blast radius — what breaks at depth 1\u002F2\u002F3 with confidence         |\n| `trace`          | Shortest path between two symbols — \"how does A reach B?\" in one call     |\n| `detect_changes` | Git-diff impact — what do your current changes affect                    |\n| `rename`         | Multi-file coordinated rename with confidence-tagged edits               |\n| `cypher`         | Raw graph queries (read `gitnexus:\u002F\u002Frepo\u002F{name}\u002Fschema` first)           |\n| `explain`        | Persisted taint findings — source→sink data flows (needs `analyze --pdg`) |\n| `pdg_query`      | Control\u002Fdata dependence — what gates X (CDG) \u002F where Y flows (REACHING_DEF); needs `analyze --pdg` |\n| `check`          | Check graph invariants such as circular imports                          |\n| `route_map`      | API route map — which components\u002Fhooks fetch which endpoints, and the handler files that serve them |\n| `shape_check`    | Response-shape drift — keys each route returns vs keys its consumers access (flags MISMATCH) |\n| `api_impact`     | Pre-change report for an API route — consumers, middleware, shape mismatches, risk level |\n| `tool_map`       | MCP\u002FRPC tool definitions and the files that handle them                  |\n| `group_list`     | List configured multi-repo groups, or one group's config                 |\n| `group_sync`     | Rebuild a group's Contract Registry (cross-repo HTTP contract links); run after `group.yaml` changes or member re-index |\n| `list_repos`     | Discover indexed repos (paginated — `limit`\u002F`offset`)                    |\n\n### Paginating `list_repos`\n\n`list_repos` is paginated so a large registry is not truncated by MCP\u002FLLM token limits. It takes optional `limit` (default **50**, max **200**) and `offset`, and returns:\n\n```jsonc\n{\n  \"repositories\": [\n    { \"name\": \"...\", \"path\": \"...\", \"indexedAt\": \"...\", \"lastCommit\": \"...\", \"stats\": { } }\n  ],\n  \"pagination\": {\n    \"total\": 437,\n    \"limit\": 50,\n    \"offset\": 0,\n    \"returned\": 50,\n    \"hasMore\": true,\n    \"nextOffset\": 50\n  }\n}\n```\n\nTo enumerate **every** repository, keep calling with `offset` set to `pagination.nextOffset` until `hasMore` is `false`:\n\n```text\nlist_repos {}               → repos 1–50,    nextOffset 50,  hasMore true\nlist_repos { offset: 50 }   → repos 51–100,  nextOffset 100, hasMore true\n…\nlist_repos { offset: 400 }  → repos 401–437,                 hasMore false   (done)\n```\n\nNotes: `offset` ≥ `total` returns an empty page (with `total` still reported). Out-of-range or malformed `limit`\u002F`offset` (non-integer, `limit` outside `[1, 200]`, `offset \u003C 0`) are rejected with a clear error — `limit` above the max is rejected, not silently capped. The order is deterministic (lower-cased name, then path), so paging never skips or duplicates an entry while the registry is unchanged.\n\n### Taint findings (`explain`)\n\n`explain` returns taint findings recorded by `gitnexus analyze --pdg` — intra-procedural `TAINTED` edges plus cross-function `TAINT_PATH` hops where the interprocedural taint phase found a function-level source→sink chain. Each finding includes a sink category (command-injection, code-injection, path-traversal, sql-injection, xss), source\u002Fsink lines, and the ordered hop path with the variable carried on each hop.\n\n- `explain {}` — enumerate all findings for the repo (bounded by `limit`, deterministic order)\n- `explain { target: \"src\u002Fvuln.ts\" }` — findings in a file (suffix path match accepted)\n- `explain { target: \"runUserCommand\" }` — findings in a function (resolved like `context`; ambiguous names return ranked candidates)\n\nA repo indexed without `--pdg` returns a clear \"no taint layer\" note. Caveats: closure\u002Fcallback, property\u002Ffield, and implicit flows are not modeled, and interprocedural findings are function-level `TAINT_PATH` hops rather than statement-level path proof, so the absence of a finding is **not** proof of safety. `SANITIZES` (sanitizer-kill) edges are queryable via `cypher`.\n\n### Control & data dependence (`pdg_query`)\n\n`pdg_query` reads the control\u002Fdata-dependence layers `gitnexus analyze --pdg` records (CDG + REACHING_DEF, basic-block granular) — the control\u002Fdata analog of `explain`. It is **always anchored** (a `target` file path or symbol, resolved like `context`) and has two modes:\n\n- `pdg_query { mode: \"controls\", target: \"...\" }` — CDG: \"under what condition does X run?\". Each edge is a controlling predicate block → dependent block with the branch sense (`'T'`\u002F`'F'`) in `reason`; an edge into an early `return`\u002F`throw` is flagged `guard: true` (guard-clause discovery — the sense depends on the predicate, so don't filter guards by a fixed label).\n- `pdg_query { mode: \"flows\", target: \"...\", variable?: \"...\" }` — REACHING_DEF def→use edges within the function; pass `variable` to trace one binding.\n\nA repo indexed without `--pdg` returns a \"no PDG layer\" note (or \"status unknown\" when the layer can't be confirmed). Intra-procedural only — cross-function flow is taint's domain (`explain`). The raw CDG\u002FREACHING_DEF edges are also queryable via `cypher`. See the `gitnexus-pdg-query` skill for the full query surface.\n\n### Shortest path between two symbols (`trace`)\n\n`trace` answers \"how does A reach B?\" in one call — the shortest directed path over `CALLS` (plus `HAS_METHOD`, so a class-rooted trace descends into its methods) instead of chaining 3–8 `context`\u002F`impact` hops by hand.\n\n- `trace { from: \"validateUser\", to: \"executeQuery\" }` — shortest path between two symbols.\n- Disambiguate common names with `from_uid`\u002F`to_uid` (zero-ambiguity) or `from_file`\u002F`to_file`; an ambiguous name returns ranked candidates.\n- `maxDepth` (default 10, max 30) bounds the search; `includeTests` (default false) lets the traversal pass through test-file symbols.\n\nReturns ordered `hops` (each `{ name, filePath, startLine }`) and an aligned `edges[]` of `{ relType, confidence }`, so call hops and containment (`HAS_METHOD`) hops stay distinguishable. When no path exists it reports the **furthest** reachable node (where the chain breaks) and sets `truncated: true` if a traversal cap was hit first. Every result carries a `status`: `ok` \u002F `no_path` \u002F `ambiguous` \u002F `not_found` \u002F `error`.\n\nCross-repo (experimental): pass `repo: \"@groupName\"` to trace across a group's member repos — the path may cross **one** `ContractLink` boundary (reported as a `CONTRACT_LINK` hop with the bridged contract in `crossings[]`). Omit `to` entirely to follow `from`'s outgoing HTTP call to whatever provider endpoint it lands on. Groups are configured via `group_list` \u002F `group_sync`.\n\n## Resources Reference\n\nLightweight reads (~100-500 tokens) for navigation:\n\n| Resource                                       | Content                                   |\n| ---------------------------------------------- | ----------------------------------------- |\n| `gitnexus:\u002F\u002Frepo\u002F{name}\u002Fcontext`               | Stats, staleness check                    |\n| `gitnexus:\u002F\u002Frepo\u002F{name}\u002Fclusters`              | All functional areas with cohesion scores |\n| `gitnexus:\u002F\u002Frepo\u002F{name}\u002Fcluster\u002F{clusterName}` | Area members                              |\n| `gitnexus:\u002F\u002Frepo\u002F{name}\u002Fprocesses`             | All execution flows                       |\n| `gitnexus:\u002F\u002Frepo\u002F{name}\u002Fprocess\u002F{processName}` | Step-by-step trace                        |\n| `gitnexus:\u002F\u002Frepo\u002F{name}\u002Fschema`                | Graph schema for Cypher                   |\n\n## Graph Schema\n\n**Nodes:** File, Folder, Function, Class, Interface, Method, CodeElement, Community, Process, Route, Tool, plus language-specific types (Struct, Enum, Trait, Impl, Namespace, Module, …) and BasicBlock (`--pdg` indexes only). The full node list lives in `gitnexus:\u002F\u002Frepo\u002F{name}\u002Fschema`.\n**Edges (via CodeRelation.type):** CALLS, IMPORTS, EXTENDS, IMPLEMENTS, DEFINES, CONTAINS, MEMBER_OF, HAS_METHOD, HAS_PROPERTY, ACCESSES, METHOD_OVERRIDES, METHOD_IMPLEMENTS, STEP_IN_PROCESS, HANDLES_ROUTE, FETCHES, HANDLES_TOOL, ENTRY_POINT_OF, WRAPS, QUERIES, INJECTS, plus `--pdg`-only types (CFG, REACHING_DEF, TAINTED, SANITIZES, TAINT_PATH, CDG — zero rows on a default index).\n\nRead `gitnexus:\u002F\u002Frepo\u002F{name}\u002Fschema` before writing Cypher — it is the authoritative schema for the indexed repo.\n\n```cypher\nMATCH (caller)-[:CodeRelation {type: 'CALLS'}]->(f:Function {name: \"myFunc\"})\nRETURN caller.name, caller.filePath\n```\n",{"name":5,"description":7},"main","21e9d44fdaaca8c4f9214e5cc65f6a470cde9150",".agents\u002Fskills\u002Fgitnexus\u002Fgitnexus-guide",9,"https:\u002F\u002Fgithub.com\u002FPyModel\u002Fpythinker-code","https:\u002F\u002Fpythinker.com","https:\u002F\u002Fgithub.com\u002FPyModel","https:\u002F\u002Fpymodel.com","AI, LLM, and machine learning solutions. Think first, then code.","2026-11-14 19:27:49",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add PyModel\u002Fpythinker-code --skill gitnexus-guide",{"tool":40,"command":41},"bunx","bunx skills add PyModel\u002Fpythinker-code --skill gitnexus-guide",{"tool":43,"command":44},"pnpm","pnpm dlx skills add PyModel\u002Fpythinker-code --skill gitnexus-guide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPyModel\u002Fpythinker-code\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgitnexus\u002Fgitnexus-guide\u002FSKILL.md",true,[],[49,56,63,69,76,83],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M75W4KT7SF7713RMC0AW447N","pythinker-webbridge","Pythinker Browser Extension lets AI control the user's real browser — navigate, click, type, read, screenshot, and interact with any website using the user's actual login sessions. Use this skill whenever the user wants to interact with websites, automate browser tasks, scrape web content, or perform any action requiring a real browser. Also use when the user mentions \"browser\", \"webpage\", \"open URL\", \"screenshot\", or asks to read\u002Finteract with any website. Use even for simple-sounding browser requests — the daemon handles all complexity.","https:\u002F\u002Fgithub.com\u002FPyModel\u002Fpythinker-code\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fpythinker-webbridge\u002Fskills\u002Fpythinker-webbridge\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M75W4JD3116MVVZM0DPRFNG2","golden-skill","Golden fixture skill","https:\u002F\u002Fgithub.com\u002FPyModel\u002Fpythinker-code\u002Fblob\u002Fmain\u002Fpackages\u002Fmigration-legacy\u002Ftest\u002Ffixtures\u002Fgolden\u002F.pythinker\u002Fskills\u002Fgolden-skill\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M75W4D9XE0YP7GYTY7X9Y020","tools","https:\u002F\u002Fgithub.com\u002FPyModel\u002Fpythinker-code\u002Fblob\u002Fmain\u002Fpackages\u002Fagent-core-v2\u002Fsrc\u002Ffeatures\u002Fskill\u002Ftools\u002Fskill.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M75W44KYZ87VVKCFBR1MPX40","review","Analyze the available skill set and recommend candidate groups that could be consolidated into sub-skill bundles. Read-only — proposes a plan, does not move files.","https:\u002F\u002Fgithub.com\u002FPyModel\u002Fpythinker-code\u002Fblob\u002Fmain\u002Fpackages\u002Fagent-core-v2\u002Fsrc\u002Ffeatures\u002Fskill\u002Fcatalog\u002Fbuiltin\u002Fsub-skill\u002Freview\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M75W3V96RQ8N2E1DJB9A20PR","consolidate","Apply an approved sub-skill grouping by moving user-specified skills into a parent bundle, with timestamped backups of every modified directory.","https:\u002F\u002Fgithub.com\u002FPyModel\u002Fpythinker-code\u002Fblob\u002Fmain\u002Fpackages\u002Fagent-core-v2\u002Fsrc\u002Ffeatures\u002Fskill\u002Fcatalog\u002Fbuiltin\u002Fsub-skill\u002Fconsolidate\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M75W3S1NEJ5N05CDYS292QQG","sub-skill","Discover and reorganize the skill inventory into hierarchical sub-skill bundles. Use when the user asks to review, group, or consolidate skills into a parent bundle.","https:\u002F\u002Fgithub.com\u002FPyModel\u002Fpythinker-code\u002Fblob\u002Fmain\u002Fpackages\u002Fagent-core-v2\u002Fsrc\u002Ffeatures\u002Fskill\u002Fcatalog\u002Fbuiltin\u002Fsub-skill\u002FSKILL.md",[],[]]