[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71DCEXJ82VQB14545FJ4DA7":3,"skill-same:01M71DCEXJ82VQB14545FJ4DA7":68},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":14,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M71DCEXJ82VQB14545FJ4DA7","grok-project-scope",null,"Use for grok-project-scope — defining, enforcing and maintaining clear documented scopes for every project inside the GrokProjects workspace. Requires the grok-projects-workspace skill. Activate when user mentions project scope, grok-project-scope, define scope for project, scope management or project boundaries.","DCx7C5\u002Fai-marketplace","DCx7C5","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42419559?v=4","01M71C01G2AZV3NTNGWAWSHJPP","DC","01M71C01GQW6G50S2BYMS7PP3E",0,"MIT","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fgrok-project-scope\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"project","grok project scope","grok","scope","user","activate","when","management","define scope","use","define","scope management","Workspace Skill","clear","workspace","for","projects","2026-11-10 10:12:30",false,"---\nname: grok-project-scope\ndescription: Use for grok-project-scope — defining, enforcing and maintaining clear documented scopes for every project inside the GrokProjects workspace. Requires the grok-projects-workspace skill. Activate when user mentions project scope, grok-project-scope, define scope for project, scope management or project boundaries.\n---\n\n# Grok Project Scope Skill\n\n## Purpose\nThis skill guarantees that every project maintained inside `\u002Fhome\u002Fworkdir\u002FGrokProjects` has a **rigorously defined, version-controlled, and strictly adhered-to scope**. It works hand-in-hand with the grok-projects-workspace skill to provide per-project governance: clear objectives, explicit in\u002Fout-of-scope boundaries, success metrics, and change-control processes. This prevents feature creep, ensures alignment with DystopianOS principles, and keeps the single source of truth repository accurate and auditable.\n\n## Instructions\n\n**Core Workflow – Execute these steps in order every time this skill is active:**\n\n**Visual cue — scope document (its explicit intention):**  \nThis `assets\u002Fscope-icon.png` reference exists for one precise reason: to embed a visual reminder that tells the user (and every future agent) to **click the folder icon in the Grok chat UI**. Doing so instantly opens the file tree directly to the synchronized workspace at `\u002Fhome\u002Fworkdir\u002FGrokProjects` and highlights the active project's `SCOPE.md`.  \n\n![Scope Document — click to open project scope](assets\u002Fscope-icon.png)\n\n1. **Prerequisite Workspace Sync** (always run grok-projects-workspace first):\n   ```bash\n   # Ensure the shared workspace is fully synchronized before scoping any project\n   mkdir -p \u002Fhome\u002Fworkdir\u002FGrokProjects\n   if [ ! -d \"\u002Fhome\u002Fworkdir\u002FGrokProjects\u002F.git\" ]; then\n     if ! git clone https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fgrok-projects-workspace.git \u002Fhome\u002Fworkdir\u002FGrokProjects 2>\u002Fdev\u002Fnull; then\n       echo \"⚠️ Remote unavailable. Creating local workspace...\"\n       cd \u002Fhome\u002Fworkdir\u002FGrokProjects\n       git init\n       mkdir -p pipelines templates repos docs\n       echo '# Grok Projects Workspace (Local Fallback)' > README.md\n       git add .\n       git commit -m \"chore: initial local workspace setup\"\n     fi\n   else\n     cd \u002Fhome\u002Fworkdir\u002FGrokProjects && git pull --rebase\n   fi\n   cd \u002Fhome\u002Fworkdir\u002FGrokProjects\n   mkdir -p repos\n   ```\n\n2. **Explicit File Path & Project Validation** (run immediately after workspace sync):\n   ```bash\n   WORKSPACE=\"\u002Fhome\u002Fworkdir\u002FGrokProjects\"\n   if [ ! -d \"$WORKSPACE\" ]; then\n     echo \"❌ Workspace directory missing: $WORKSPACE\"\n     exit 1\n   fi\n   cd \"$WORKSPACE\" || { echo \"❌ Cannot enter workspace\"; exit 1; }\n   RESOLVED_PATH=\"$(realpath \"$WORKSPACE\")\"\n   if [ \"$RESOLVED_PATH\" != \"\u002Fhome\u002Fworkdir\u002FGrokProjects\" ]; then\n     echo \"❌ CRITICAL PATH VALIDATION FAILED\"\n     exit 1\n   fi\n   echo \"✅ Workspace validation passed: $(pwd)\"\n   mkdir -p repos pipelines templates docs\n   ```\n\n3. **Identify or Initialize Project Scope**:\n   - Ask the user for the project name if not obvious from context or conversation history.\n   - Sanitize name (lowercase, hyphens only, no spaces).\n   - Create project directory if missing: `mkdir -p \"repos\u002F$PROJECT_NAME\"`\n   - Ensure `SCOPE.md` exists in the project root. If not, generate the standard template below.\n\n   **Standard SCOPE.md Template** (write this if missing or incomplete using heredoc):\n   ```bash\n   cat > \"repos\u002F$PROJECT_NAME\u002FSCOPE.md\" \u003C\u003C 'EOF'\n   # Project Scope: [PROJECT_NAME]\n\n   ## Objective\n   [One-sentence mission statement — what this project achieves]\n\n   ## In Scope\n   - Primary deliverable 1\n   - Primary deliverable 2\n   - Supporting features \u002F integrations\n   - Documentation and tests\n\n   ## Out of Scope\n   - Explicitly excluded items (e.g. unrelated features, future phases)\n   - Nice-to-haves deferred to later projects\n\n   ## Success Criteria\n   - Measurable goal 1 (e.g. \"All pipelines pass with >95% coverage\")\n   - Measurable goal 2 (e.g. \"Deployed and validated in staging\")\n\n   ## Key Constraints & Assumptions\n   - Tech stack: Python 3.12+, specific libraries...\n   - Dependencies on other GrokProjects components\n   - Timeline \u002F milestones\n   - Resource limits\n\n   ## Change Control Process\n   All scope changes require:\n   1. Update this SCOPE.md document\n   2. Commit using conventional message: \"docs(scope): describe the boundary change\"\n   3. Immediate push to remote repository\n   4. Re-confirmation with user before proceeding with new work\n\n   ## Concurrent Work Policy (Mandatory)\n   Multiple agents in different chats **must** use `git worktree`.\n   - All agent work happens in isolated worktrees under `.worktrees\u002F\u003Cchat-id>\u002F`\n   - Never work directly in the main project root when other agents are active\n   - Create worktree with:\n     ```bash\n     git worktree add -b \"agent\u002Fchat-$$\" \".worktrees\u002Fchat-$$\"\n     cd \".worktrees\u002Fchat-$$\"\n     ```\n   - Clean up when done: `git worktree remove \".worktrees\u002Fchat-$$\"`\n\n   *Last updated: $(date +%Y-%m-%d) by Grok Project Scope Skill — Worktree policy enforced*\n   EOF\n   echo \"✅ SCOPE.md template created\u002Fupdated for $PROJECT_NAME\"\n   ```\n\n4. **Instruct the user** to click the folder icon (see image above) to open the file tree, navigate to `repos\u002F[project-name]\u002FSCOPE.md`, and review\u002Fconfirm the current scope before any implementation work begins.\n\n5. **Communicate the Scope Governance Rules** clearly:\n   - This `SCOPE.md` is the **binding contract** for all work on this project.\n   - Every task, script, commit, or change **must** be directly traceable to an item listed under \"In Scope\".\n   - Scope creep is explicitly forbidden — any proposed addition, no matter how small, must first result in an updated SCOPE.md, user confirmation, commit, and push.\n   - The GrokProjects repository is the single source of truth; scope definitions must never live in chat history, external notes, or uncommitted files.\n\n6. **Enforce Clean Scope Workflow**:\n   - At the beginning of every session involving this project: display the full SCOPE.md and obtain explicit user confirmation that the current task aligns with it.\n   - Before making any change that could expand deliverables or boundaries: update SCOPE.md first.\n   - Always run `git status && git diff` before committing scope-related edits.\n   - Use conventional commit prefixes: `docs(scope):`, `feat(scope):`, or `fix(scope):`.\n   - After every meaningful scope edit: commit immediately and push without delay.\n\n7. **Directory & Project Management**:\n   - All individual projects live exclusively under `repos\u002F`\n   - Enforce consistent internal structure for every project (including mandatory worktrees):\n\n     ```\n     repos\u002F\u003Cproject-name>\u002F\n     ├── .git\u002F                     # Main bare\u002Fmain worktree (protected)\n     ├── SCOPE.md                  # Required — the binding contract\n     ├── README.md                 # High-level overview (links to SCOPE.md)\n     ├── .worktrees\u002F               # ← MANDATORY: all concurrent agent chats live here\n     │   ├── agent-chat-abc123\u002F    # One isolated worktree per active chat\u002Fagent\n     │   │   ├── src\u002F ...\n     │   │   └── ...\n     │   └── agent-chat-def456\u002F\n     ├── docs\u002F\n     ├── src\u002F (or pipelines\u002F)\n     ├── tests\u002F\n     └── assets\u002F\n     ```\n\n   **Mandatory Git Worktree Policy (enforced by default)**\n\n   Multiple agents running in **different chats** on the **same project** **must** use `git worktree`. This is now the default and only supported way to work concurrently.\n\n   **Why worktrees?**\n   - Prevents merge conflicts between parallel agent sessions\n   - Each chat gets a completely isolated working directory + branch\n   - Main worktree stays clean and is only used for final integration \u002F PRs\n   - Full history and remote tracking are shared safely\n\n   **How to create a worktree for your current chat (run from project root):**\n\n   ```bash\n   CHAT_ID=\"chat-$(date +%s)-$$\"          # unique per chat (or use Grok chat session ID)\n   git worktree add -b \"agent\u002F${CHAT_ID}\" \".worktrees\u002F${CHAT_ID}\"\n   cd \".worktrees\u002F${CHAT_ID}\"\n   # All your work, commits, and pushes happen inside this worktree\n   ```\n\n   **Worktree Rules (strictly enforced):**\n   - Never edit files directly in the main `repos\u002F\u003Cproject-name>\u002F` if other agents are active.\n   - Always create a dedicated worktree under `.worktrees\u002F` for every new chat.\n   - When the chat\u002Fsession ends: `git worktree remove \".worktrees\u002F${CHAT_ID}\"`\n   - The main branch (`main`\u002F`master`) lives only in the primary worktree.\n   - All worktrees are automatically tracked by git and visible via `git worktree list`.\n\n   - Shared cross-project resources stay in top-level `pipelines\u002F`, `templates\u002F`, and `docs\u002F`.\n\n8. **Handle Unnamed, Ambiguous, or Legacy Projects**:\n   - If a directory exists in `repos\u002F` without a clear name or SCOPE.md: immediately ask the user for a proper kebab-case project name, rename the folder, create the SCOPE.md template, commit the reorganization, and push.\n   - If work appears to be drifting outside the defined scope: pause, flag the discrepancy, propose the required SCOPE.md update, and do not proceed until the scope document is updated and committed.\n\n9. **Migrate Legacy Scope Documents** (Robust Migration):\n   ```bash\n   # Check for legacy scope files outside the proper workspace structure\n   LEGACY_PATHS=(\"\u002Fhome\u002Fworkdir\u002F*-project\u002FSCOPE.md\" \"\u002Fhome\u002Fworkdir\u002Fscope-*.md\" \"\u002Fhome\u002Fworkdir\u002F.grok\u002Flegacy-scopes\u002F*\")\n   for legacy in \"${LEGACY_PATHS[@]}\"; do\n     if ls $legacy 1>\u002Fdev\u002Fnull 2>&1; then\n       echo \"🔄 Migrating legacy scope document(s) into GrokProjects...\"\n       # Create target project dir, move file, clean up, git add\u002Fcommit\u002Fpush\n       # (implementation details follow the same safe pattern as workspace migration)\n       git add -A\n       git commit -m \"chore(scope): migrate legacy scope document into workspace\"\n       git push\n       echo \"✅ Legacy scope successfully migrated, committed, and pushed.\"\n     fi\n   done\n   ```\n\n**Activation Triggers:**\n- \"project scope\"\n- \"grok-project-scope\"\n- \"define project scope\"\n- \"scope this project\"\n- \"update the scope\"\n- \"what is in scope\"\n- \"scope management\"\n- \"set project boundaries\"\n\nThis skill ensures **precise, auditable, and creep-resistant** project execution across all Grok and DystopianOS initiatives while maintaining perfect synchronization with the central repository.","# Grok Project Scope Skill\n\n## Purpose\nThis skill guarantees that every project maintained inside `\u002Fhome\u002Fworkdir\u002FGrokProjects` has a **rigorously defined, version-controlled, and strictly adhered-to scope**. It works hand-in-hand with the grok-projects-workspace skill to provide per-project governance: clear objectives, explicit in\u002Fout-of-scope boundaries, success metrics, and change-control processes. This prevents feature creep, ensures alignment with DystopianOS principles, and keeps the single source of truth repository accurate and auditable.\n\n## Instructions\n\n**Core Workflow – Execute these steps in order every time this skill is active:**\n\n**Visual cue — scope document (its explicit intention):**  \nThis `assets\u002Fscope-icon.png` reference exists for one precise reason: to embed a visual reminder that tells the user (and every future agent) to **click the folder icon in the Grok chat UI**. Doing so instantly opens the file tree directly to the synchronized workspace at `\u002Fhome\u002Fworkdir\u002FGrokProjects` and highlights the active project's `SCOPE.md`.  \n\n![Scope Document — click to open project scope](assets\u002Fscope-icon.png)\n\n1. **Prerequisite Workspace Sync** (always run grok-projects-workspace first):\n   ```bash\n   # Ensure the shared workspace is fully synchronized before scoping any project\n   mkdir -p \u002Fhome\u002Fworkdir\u002FGrokProjects\n   if [ ! -d \"\u002Fhome\u002Fworkdir\u002FGrokProjects\u002F.git\" ]; then\n     if ! git clone https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fgrok-projects-workspace.git \u002Fhome\u002Fworkdir\u002FGrokProjects 2>\u002Fdev\u002Fnull; then\n       echo \"⚠️ Remote unavailable. Creating local workspace...\"\n       cd \u002Fhome\u002Fworkdir\u002FGrokProjects\n       git init\n       mkdir -p pipelines templates repos docs\n       echo '# Grok Projects Workspace (Local Fallback)' > README.md\n       git add .\n       git commit -m \"chore: initial local workspace setup\"\n     fi\n   else\n     cd \u002Fhome\u002Fworkdir\u002FGrokProjects && git pull --rebase\n   fi\n   cd \u002Fhome\u002Fworkdir\u002FGrokProjects\n   mkdir -p repos\n   ```\n\n2. **Explicit File Path & Project Validation** (run immediately after workspace sync):\n   ```bash\n   WORKSPACE=\"\u002Fhome\u002Fworkdir\u002FGrokProjects\"\n   if [ ! -d \"$WORKSPACE\" ]; then\n     echo \"❌ Workspace directory missing: $WORKSPACE\"\n     exit 1\n   fi\n   cd \"$WORKSPACE\" || { echo \"❌ Cannot enter workspace\"; exit 1; }\n   RESOLVED_PATH=\"$(realpath \"$WORKSPACE\")\"\n   if [ \"$RESOLVED_PATH\" != \"\u002Fhome\u002Fworkdir\u002FGrokProjects\" ]; then\n     echo \"❌ CRITICAL PATH VALIDATION FAILED\"\n     exit 1\n   fi\n   echo \"✅ Workspace validation passed: $(pwd)\"\n   mkdir -p repos pipelines templates docs\n   ```\n\n3. **Identify or Initialize Project Scope**:\n   - Ask the user for the project name if not obvious from context or conversation history.\n   - Sanitize name (lowercase, hyphens only, no spaces).\n   - Create project directory if missing: `mkdir -p \"repos\u002F$PROJECT_NAME\"`\n   - Ensure `SCOPE.md` exists in the project root. If not, generate the standard template below.\n\n   **Standard SCOPE.md Template** (write this if missing or incomplete using heredoc):\n   ```bash\n   cat > \"repos\u002F$PROJECT_NAME\u002FSCOPE.md\" \u003C\u003C 'EOF'\n   # Project Scope: [PROJECT_NAME]\n\n   ## Objective\n   [One-sentence mission statement — what this project achieves]\n\n   ## In Scope\n   - Primary deliverable 1\n   - Primary deliverable 2\n   - Supporting features \u002F integrations\n   - Documentation and tests\n\n   ## Out of Scope\n   - Explicitly excluded items (e.g. unrelated features, future phases)\n   - Nice-to-haves deferred to later projects\n\n   ## Success Criteria\n   - Measurable goal 1 (e.g. \"All pipelines pass with >95% coverage\")\n   - Measurable goal 2 (e.g. \"Deployed and validated in staging\")\n\n   ## Key Constraints & Assumptions\n   - Tech stack: Python 3.12+, specific libraries...\n   - Dependencies on other GrokProjects components\n   - Timeline \u002F milestones\n   - Resource limits\n\n   ## Change Control Process\n   All scope changes require:\n   1. Update this SCOPE.md document\n   2. Commit using conventional message: \"docs(scope): describe the boundary change\"\n   3. Immediate push to remote repository\n   4. Re-confirmation with user before proceeding with new work\n\n   ## Concurrent Work Policy (Mandatory)\n   Multiple agents in different chats **must** use `git worktree`.\n   - All agent work happens in isolated worktrees under `.worktrees\u002F\u003Cchat-id>\u002F`\n   - Never work directly in the main project root when other agents are active\n   - Create worktree with:\n     ```bash\n     git worktree add -b \"agent\u002Fchat-$$\" \".worktrees\u002Fchat-$$\"\n     cd \".worktrees\u002Fchat-$$\"\n     ```\n   - Clean up when done: `git worktree remove \".worktrees\u002Fchat-$$\"`\n\n   *Last updated: $(date +%Y-%m-%d) by Grok Project Scope Skill — Worktree policy enforced*\n   EOF\n   echo \"✅ SCOPE.md template created\u002Fupdated for $PROJECT_NAME\"\n   ```\n\n4. **Instruct the user** to click the folder icon (see image above) to open the file tree, navigate to `repos\u002F[project-name]\u002FSCOPE.md`, and review\u002Fconfirm the current scope before any implementation work begins.\n\n5. **Communicate the Scope Governance Rules** clearly:\n   - This `SCOPE.md` is the **binding contract** for all work on this project.\n   - Every task, script, commit, or change **must** be directly traceable to an item listed under \"In Scope\".\n   - Scope creep is explicitly forbidden — any proposed addition, no matter how small, must first result in an updated SCOPE.md, user confirmation, commit, and push.\n   - The GrokProjects repository is the single source of truth; scope definitions must never live in chat history, external notes, or uncommitted files.\n\n6. **Enforce Clean Scope Workflow**:\n   - At the beginning of every session involving this project: display the full SCOPE.md and obtain explicit user confirmation that the current task aligns with it.\n   - Before making any change that could expand deliverables or boundaries: update SCOPE.md first.\n   - Always run `git status && git diff` before committing scope-related edits.\n   - Use conventional commit prefixes: `docs(scope):`, `feat(scope):`, or `fix(scope):`.\n   - After every meaningful scope edit: commit immediately and push without delay.\n\n7. **Directory & Project Management**:\n   - All individual projects live exclusively under `repos\u002F`\n   - Enforce consistent internal structure for every project (including mandatory worktrees):\n\n     ```\n     repos\u002F\u003Cproject-name>\u002F\n     ├── .git\u002F                     # Main bare\u002Fmain worktree (protected)\n     ├── SCOPE.md                  # Required — the binding contract\n     ├── README.md                 # High-level overview (links to SCOPE.md)\n     ├── .worktrees\u002F               # ← MANDATORY: all concurrent agent chats live here\n     │   ├── agent-chat-abc123\u002F    # One isolated worktree per active chat\u002Fagent\n     │   │   ├── src\u002F ...\n     │   │   └── ...\n     │   └── agent-chat-def456\u002F\n     ├── docs\u002F\n     ├── src\u002F (or pipelines\u002F)\n     ├── tests\u002F\n     └── assets\u002F\n     ```\n\n   **Mandatory Git Worktree Policy (enforced by default)**\n\n   Multiple agents running in **different chats** on the **same project** **must** use `git worktree`. This is now the default and only supported way to work concurrently.\n\n   **Why worktrees?**\n   - Prevents merge conflicts between parallel agent sessions\n   - Each chat gets a completely isolated working directory + branch\n   - Main worktree stays clean and is only used for final integration \u002F PRs\n   - Full history and remote tracking are shared safely\n\n   **How to create a worktree for your current chat (run from project root):**\n\n   ```bash\n   CHAT_ID=\"chat-$(date +%s)-$$\"          # unique per chat (or use Grok chat session ID)\n   git worktree add -b \"agent\u002F${CHAT_ID}\" \".worktrees\u002F${CHAT_ID}\"\n   cd \".worktrees\u002F${CHAT_ID}\"\n   # All your work, commits, and pushes happen inside this worktree\n   ```\n\n   **Worktree Rules (strictly enforced):**\n   - Never edit files directly in the main `repos\u002F\u003Cproject-name>\u002F` if other agents are active.\n   - Always create a dedicated worktree under `.worktrees\u002F` for every new chat.\n   - When the chat\u002Fsession ends: `git worktree remove \".worktrees\u002F${CHAT_ID}\"`\n   - The main branch (`main`\u002F`master`) lives only in the primary worktree.\n   - All worktrees are automatically tracked by git and visible via `git worktree list`.\n\n   - Shared cross-project resources stay in top-level `pipelines\u002F`, `templates\u002F`, and `docs\u002F`.\n\n8. **Handle Unnamed, Ambiguous, or Legacy Projects**:\n   - If a directory exists in `repos\u002F` without a clear name or SCOPE.md: immediately ask the user for a proper kebab-case project name, rename the folder, create the SCOPE.md template, commit the reorganization, and push.\n   - If work appears to be drifting outside the defined scope: pause, flag the discrepancy, propose the required SCOPE.md update, and do not proceed until the scope document is updated and committed.\n\n9. **Migrate Legacy Scope Documents** (Robust Migration):\n   ```bash\n   # Check for legacy scope files outside the proper workspace structure\n   LEGACY_PATHS=(\"\u002Fhome\u002Fworkdir\u002F*-project\u002FSCOPE.md\" \"\u002Fhome\u002Fworkdir\u002Fscope-*.md\" \"\u002Fhome\u002Fworkdir\u002F.grok\u002Flegacy-scopes\u002F*\")\n   for legacy in \"${LEGACY_PATHS[@]}\"; do\n     if ls $legacy 1>\u002Fdev\u002Fnull 2>&1; then\n       echo \"🔄 Migrating legacy scope document(s) into GrokProjects...\"\n       # Create target project dir, move file, clean up, git add\u002Fcommit\u002Fpush\n       # (implementation details follow the same safe pattern as workspace migration)\n       git add -A\n       git commit -m \"chore(scope): migrate legacy scope document into workspace\"\n       git push\n       echo \"✅ Legacy scope successfully migrated, committed, and pushed.\"\n     fi\n   done\n   ```\n\n**Activation Triggers:**\n- \"project scope\"\n- \"grok-project-scope\"\n- \"define project scope\"\n- \"scope this project\"\n- \"update the scope\"\n- \"what is in scope\"\n- \"scope management\"\n- \"set project boundaries\"\n\nThis skill ensures **precise, auditable, and creep-resistant** project execution across all Grok and DystopianOS initiatives while maintaining perfect synchronization with the central repository.",{"name":5,"description":7},"main","a91f1293287ffa9f4f1b8f486cd6e835a1568c84","skills\u002Fgrok-project-scope","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace","https:\u002F\u002Fgithub.com\u002FDCx7C5","#Python","2026-09-01 11:21:00",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add DCx7C5\u002Fai-marketplace --skill grok-project-scope",{"tool":54,"command":55},"bunx","bunx skills add DCx7C5\u002Fai-marketplace --skill grok-project-scope",{"tool":57,"command":58},"pnpm","pnpm dlx skills add DCx7C5\u002Fai-marketplace --skill grok-project-scope","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fgrok-project-scope\u002FSKILL.md",true,[62],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"index.json","REFERENCE","参考文档",658,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fgrok-project-scope\u002Findex.json",[69,95,118,140,162,178],{"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":36},"01M71HAPZ01KQ30RKTB0FFSQ05","services-wmi-persistence-detect","Detect WMI event subscription persistence by enumerating ActiveScriptEventConsumer, CommandLineEventConsumer, and permanent subscriptions in the WMI repository.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fpersistence\u002Fdetect\u002FSKILL.md",[],[76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94],"services","detect","services wmi persistence detect","wmi","persistence","de","cm","process","activescript","event","subscriptions","commandline-consumer","repository","subscription","event-subscription","t1546.003","forensics","cybersecurity","process-forensics",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":36},"01M71HAK6JTTTS229T17WJMMCG","services-wmi-exec-exploit","Perform lateral movement across Windows networks using WMI-based remote execution techniques including Impacket wmiexec.py, CrackMapExec, and native WMI commands for stealthy post-exploitation during red team engagements.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fexec\u002Fexploit\u002FSKILL.md",[],[102,76,103,79,104,105,106,93,107,108,109,110,111,112,81,113,114,115,116,117],"exploit","services wmi exec exploit","exec","remote","traffic","Bash","analysis","team","across","crackmapexec","native","command","lateral movement","read","lateral-movement","Impacket",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":36},"01M71HAG6MHKNQV8KDZKMT4886","registry-artifact-extract","Extract and analyze Windows Registry hives to uncover user activity, installed software, autostart entries, and evidence of system compromise.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fregistry\u002Fartifact\u002Fextract\u002FSKILL.md",[],[125,126,127,128,129,130,93,107,131,108,132,133,81,115,134,135,136,137,138,139],"artifact","registry","registry artifact extract","extract","evidence-collection","artifact-analysis","collection","analyze","uncover","software","activity","digital-forensics","windows-registry","regripper","sonnet",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":36},"01M71HACR4A8XTWTTSXK4124AA","processes-token-impersonate-detect","Detect Windows token impersonation and privilege abuse including SeImpersonatePrivilege exploitation via Potato attacks and token stealing techniques.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Ftoken\u002Fimpersonate\u002Fdetect\u002FSKILL.md",[],[77,147,148,149,150,151,152,82,153,93,94,154,155,156,157,158,159,160,161,81],"processes token impersonate detect","token","processes","attacks","windows","escalation","techniques","privilege-escalation","seimpersonate","token-impersonation","printspoofer","exploitation","potato","impersonation","via",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":36},"01M71HAABSB4Z6QFSXEG00R4RK","processes-thread-injection-detect","Detect Windows thread injection techniques including CreateRemoteThread, QueueUserAPC, NtCreateThreadEx, and thread hijacking via process memory analysis.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fthread\u002Finjection\u002Fdetect\u002FSKILL.md",[],[169,170,77,171,149,151,172,82,173,153,93,94,108,174,175,176,177,161,81,83],"thread","processes thread injection detect","injection","memory","process-injection","api","apc-injection","thread-injection","nt-api",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":36},"01M71HA7H311V5G14WMX58HQSS","processes-hollow-technique-detect","Detect process hollowing (RunPE) by identifying processes with mismatched image paths between PEB and VAD tree, or unmapped PE headers in memory.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fhollow\u002Ftechnique\u002Fdetect\u002FSKILL.md",[],[185,77,149,186,172,82,187,188,93,94,189,190,191,192,193,194,81,83,195,196],"processes hollow technique detect","tree","memory-forensics","process-hollow","peb","runpe","image","pe-header","in memory","with","mismatched","headers"]