{"id":"d25364b9-a73a-486f-8368-5e0e346b70f5","entityType":"agent","slug":"clawhub-athola-nm-sanctum-file-analysis","name":"file-analysis","canonicalUrl":"https://www.xpersona.co/agent/clawhub-athola-nm-sanctum-file-analysis","canonicalPath":"/agent/clawhub-athola-nm-sanctum-file-analysis","generatedAt":"2026-10-10T13:33:25.584Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-10T10:09:13.488Z","emptyReason":null},"description":"Maps file structure and module organization of a codebase. Use before architecture reviews, refactoring planning, or migration scope estimation Skill: file-analysis Owner: athola Summary: Maps file structure and module organization of a codebase. Use before architecture reviews, refactoring planning, or migration scope estimation Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:20:20.967Z | user Release v1.9.19 v1.9.17 | 2026-07-30T05:40:25.226Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:57:19.321Z | user Release v1.9.16 v1.9.14 | 2026-06-30T","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.5K downloads reported by the source. Last updated 10/10/2026.","installCommand":"clawhub skill install s17emme0e2m3cpf7k2jvp3a84984b8z9:nm-sanctum-file-analysis","sourceUrl":"https://clawhub.ai/athola/nm-sanctum-file-analysis","homepage":"https://clawhub.ai/athola/skills/nm-sanctum-file-analysis","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/athola/nm-sanctum-file-analysis","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/athola/skills/nm-sanctum-file-analysis","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":64,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Maps file structure and module organization of a codebase. Use before architecture reviews, refactoring planning, or migration scope estimation Skill: file-anal"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-10T10:09:13.488Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T10:09:13.488Z","emptyReason":null},"stars":null,"forks":null,"downloads":1505,"packageName":null,"latestVersion":"1.9.19","tractionLabel":"1.5K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T10:09:13.488Z","emptyReason":null},"lastUpdatedAt":"2026-10-10T10:09:13.488Z","lastCrawledAt":"2026-10-10T10:09:13.488Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-11T10:09:13.488Z","lastVerifiedAt":null,"highlights":[{"version":"1.9.19","createdAt":"2026-08-26T13:20:20.967Z","changelog":"Release v1.9.19","fileCount":3,"zipByteSize":2858},{"version":"1.9.17","createdAt":"2026-07-30T05:40:25.226Z","changelog":"Release v1.9.17","fileCount":3,"zipByteSize":2892},{"version":"1.9.16","createdAt":"2026-07-14T19:57:19.321Z","changelog":"Release v1.9.16","fileCount":3,"zipByteSize":2942},{"version":"1.9.14","createdAt":"2026-06-30T18:05:12.938Z","changelog":"Release v1.9.14","fileCount":3,"zipByteSize":2944},{"version":"1.9.13","createdAt":"2026-06-27T16:23:06.634Z","changelog":"Release v1.9.13","fileCount":3,"zipByteSize":2861},{"version":"1.9.12","createdAt":"2026-06-19T03:18:29.955Z","changelog":"Release v1.9.12","fileCount":3,"zipByteSize":2964},{"version":"1.0.3","createdAt":"2026-06-18T15:20:16.632Z","changelog":"Release v1.9.12","fileCount":3,"zipByteSize":2908},{"version":"1.0.2","createdAt":"2026-05-09T02:19:50.365Z","changelog":"Release v1.9.5","fileCount":3,"zipByteSize":2976}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17emme0e2m3cpf7k2jvp3a84984b8z9:nm-sanctum-file-analysis","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-file-analysis/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-file-analysis/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-file-analysis/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-file-analysis/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-file-analysis/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-file-analysis/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T13:33:25.583Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-file-analysis/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-file-analysis/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-file-analysis/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-file-analysis/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-10T10:09:13.488Z","emptyReason":null},"readme":"Skill: file-analysis\n\nOwner: athola\n\nSummary: Maps file structure and module organization of a codebase. Use before architecture reviews, refactoring planning, or migration scope estimation\n\nTags: latest:1.9.19\n\nVersion history:\n\nv1.9.19 | 2026-08-26T13:20:20.967Z | user\n\nRelease v1.9.19\n\nv1.9.17 | 2026-07-30T05:40:25.226Z | user\n\nRelease v1.9.17\n\nv1.9.16 | 2026-07-14T19:57:19.321Z | user\n\nRelease v1.9.16\n\nv1.9.14 | 2026-06-30T18:05:12.938Z | user\n\nRelease v1.9.14\n\nv1.9.13 | 2026-06-27T16:23:06.634Z | user\n\nRelease v1.9.13\n\nv1.9.12 | 2026-06-19T03:18:29.955Z | user\n\nRelease v1.9.12\n\nv1.0.3 | 2026-06-18T15:20:16.632Z | user\n\nRelease v1.9.12\n\nv1.0.2 | 2026-05-09T02:19:50.365Z | user\n\nRelease v1.9.5\n\nv1.0.1 | 2026-05-06T14:21:13.419Z | user\n\nRelease v1.9.4\n\nv1.0.0 | 2026-04-15T19:01:42.904Z | auto\n\n- Initial release of the file-analysis skill.\n- Provides step-by-step workflow for mapping codebase structure and organization.\n- Includes triggers for structure, files, analysis, and exploration.\n- Details required steps and checks for identifying root, mapping structure, detecting patterns, and noting hotspots.\n- Outlines troubleshooting guidance for common issues.\n\nArchive index:\n\nArchive v1.9.19: 3 files, 2858 bytes\n\nFiles: skill-card.md (1921b), SKILL.md (3147b), _meta.json (144b)\n\nFile v1.9.19:SKILL.md\n\n---\nname: file-analysis\ndescription: |\n  Maps file structure and module organization of a codebase. Use before architecture reviews, refactoring planning, or migration scope estimation\nversion: 1.9.8\ntriggers:\n  - files\n  - structure\n  - analysis\n  - codebase\n  - exploration\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# File Analysis\n\n## When To Use\n- Before architecture reviews to understand module boundaries and file organization.\n- When exploring unfamiliar codebases to map structure before making changes.\n- As input to scope estimation for refactoring or migration work.\n\n## When NOT To Use\n\n- General code exploration - use the Explore agent\n- Searching for specific patterns - use Grep directly\n\n## Required TodoWrite Items\n1. `file-analysis:root-identified`\n2. `file-analysis:structure-mapped`\n3. `file-analysis:patterns-detected`\n4. `file-analysis:hotspots-noted`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Identify Root (`file-analysis:root-identified`)\n- Confirm the analysis root directory with `pwd`.\n- Note any monorepo boundaries, workspace roots, or subproject paths.\n- Capture the project type (language, framework) from manifest files (`package.json`, `Cargo.toml`, `pyproject.toml`, etc.).\n\n## Step 2: Map Structure (`file-analysis:structure-mapped`)\n- Run `tree -L 2 -d` or `find . -type d -maxdepth 2` to capture the top-level directory layout.\n- Identify standard directories: `src/`, `lib/`, `tests/`, `docs/`, `scripts/`, `configs/`.\n- Note any non-standard organization patterns that may affect downstream analysis.\n\n## Step 3: Detect Patterns (`file-analysis:patterns-detected`)\n- Use `find . -name \"*.ext\" -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" | wc -l` to count files by extension.\n- Identify dominant languages and their file distributions.\n- Note configuration files, generated files, and vendored dependencies.\n- Run `wc -l $(find . -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" -name \"*.py\" -o -name \"*.rs\" | head -20)` to sample file sizes.\n\n## Step 4: Note Hotspots (`file-analysis:hotspots-noted`)\n- Identify large files (potential \"god objects\"): `find . -type f -exec wc -l {} + | sort -rn | head -10`.\n- Flag deeply nested directories that may indicate complexity.\n- Note files with unusual naming conventions or placement.\n\n## Exit Criteria\n- `TodoWrite` items are completed with concrete observations.\n- Downstream workflows (architecture review, refactoring) have structural context.\n- File counts, directory layout, and hotspots are documented for reference.\n\nFile v1.9.19:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-file-analysis\",\n  \"version\": \"1.9.19\",\n  \"publishedAt\": 1787750420967\n}\n\nFile v1.9.19:skill-card.md\n\n## Description:\n\nMaps file structure and module organization of a codebase for architecture reviews, refactoring planning, or migration scope estimation.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[athola](https://clawhub.ai/user/athola)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and engineers use this skill to map repository layout, identify module boundaries, and collect structural observations before architecture review, refactoring, or migration planning.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad trigger words may cause the skill to run during general codebase conversations and enumerate structure in sensitive repositories.\n\nMitigation: Confirm the intended analysis root and scope before relying on or sharing structural file enumeration.\n\nRisk: Repository layout and file names may reveal sensitive project details in generated analysis notes.\n\nMitigation: Review the generated observations before sharing them outside the intended audience.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-sanctum-file-analysis)\n- [OpenClaw homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, guidance]\n\n**Output Format:** [Markdown with shell command snippets and structured observations]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Includes directory layout, file counts, module organization, and hotspot observations when available.]\n\n## Skill Version(s):\n\n1.9.19 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.9.17: 3 files, 2892 bytes\n\nFiles: skill-card.md (2081b), SKILL.md (3147b), _meta.json (144b)\n\nFile v1.9.17:SKILL.md\n\n---\nname: file-analysis\ndescription: |\n  Maps file structure and module organization of a codebase. Use before architecture reviews, refactoring planning, or migration scope estimation\nversion: 1.9.8\ntriggers:\n  - files\n  - structure\n  - analysis\n  - codebase\n  - exploration\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# File Analysis\n\n## When To Use\n- Before architecture reviews to understand module boundaries and file organization.\n- When exploring unfamiliar codebases to map structure before making changes.\n- As input to scope estimation for refactoring or migration work.\n\n## When NOT To Use\n\n- General code exploration - use the Explore agent\n- Searching for specific patterns - use Grep directly\n\n## Required TodoWrite Items\n1. `file-analysis:root-identified`\n2. `file-analysis:structure-mapped`\n3. `file-analysis:patterns-detected`\n4. `file-analysis:hotspots-noted`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Identify Root (`file-analysis:root-identified`)\n- Confirm the analysis root directory with `pwd`.\n- Note any monorepo boundaries, workspace roots, or subproject paths.\n- Capture the project type (language, framework) from manifest files (`package.json`, `Cargo.toml`, `pyproject.toml`, etc.).\n\n## Step 2: Map Structure (`file-analysis:structure-mapped`)\n- Run `tree -L 2 -d` or `find . -type d -maxdepth 2` to capture the top-level directory layout.\n- Identify standard directories: `src/`, `lib/`, `tests/`, `docs/`, `scripts/`, `configs/`.\n- Note any non-standard organization patterns that may affect downstream analysis.\n\n## Step 3: Detect Patterns (`file-analysis:patterns-detected`)\n- Use `find . -name \"*.ext\" -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" | wc -l` to count files by extension.\n- Identify dominant languages and their file distributions.\n- Note configuration files, generated files, and vendored dependencies.\n- Run `wc -l $(find . -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" -name \"*.py\" -o -name \"*.rs\" | head -20)` to sample file sizes.\n\n## Step 4: Note Hotspots (`file-analysis:hotspots-noted`)\n- Identify large files (potential \"god objects\"): `find . -type f -exec wc -l {} + | sort -rn | head -10`.\n- Flag deeply nested directories that may indicate complexity.\n- Note files with unusual naming conventions or placement.\n\n## Exit Criteria\n- `TodoWrite` items are completed with concrete observations.\n- Downstream workflows (architecture review, refactoring) have structural context.\n- File counts, directory layout, and hotspots are documented for reference.\n\nFile v1.9.17:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-file-analysis\",\n  \"version\": \"1.9.17\",\n  \"publishedAt\": 1785390025226\n}\n\nFile v1.9.17:skill-card.md\n\n## Description: <br>\nMaps file structure and module organization of a codebase before architecture reviews, refactoring planning, or migration scope estimation. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and engineers use this skill to map repository layout, module organization, file distributions, and likely complexity hotspots before architecture review, refactoring, or migration planning. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may enumerate file and directory names in the active workspace. <br>\nMitigation: Use it only in workspaces where repository structure can be shared with the active agent and review outputs before redistribution. <br>\nRisk: Broad activation triggers could make the skill run for some general file-related requests. <br>\nMitigation: Confirm the task is repository structure analysis before using the skill's workflow. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-sanctum-file-analysis) <br>\n- [Publisher profile](https://clawhub.ai/user/athola) <br>\n- [ClawHub metadata homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, shell commands, guidance] <br>\n**Output Format:** [Markdown with repository observations and inline shell commands] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Includes file counts, directory layout notes, and hotspot observations when applied to a workspace.] <br>\n\n## Skill Version(s): <br>\n1.9.17 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.9.16: 3 files, 2942 bytes\n\nFiles: skill-card.md (2078b), SKILL.md (3147b), _meta.json (144b)\n\nFile v1.9.16:SKILL.md\n\n---\nname: file-analysis\ndescription: |\n  Maps file structure and module organization of a codebase. Use before architecture reviews, refactoring planning, or migration scope estimation\nversion: 1.9.8\ntriggers:\n  - files\n  - structure\n  - analysis\n  - codebase\n  - exploration\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# File Analysis\n\n## When To Use\n- Before architecture reviews to understand module boundaries and file organization.\n- When exploring unfamiliar codebases to map structure before making changes.\n- As input to scope estimation for refactoring or migration work.\n\n## When NOT To Use\n\n- General code exploration - use the Explore agent\n- Searching for specific patterns - use Grep directly\n\n## Required TodoWrite Items\n1. `file-analysis:root-identified`\n2. `file-analysis:structure-mapped`\n3. `file-analysis:patterns-detected`\n4. `file-analysis:hotspots-noted`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Identify Root (`file-analysis:root-identified`)\n- Confirm the analysis root directory with `pwd`.\n- Note any monorepo boundaries, workspace roots, or subproject paths.\n- Capture the project type (language, framework) from manifest files (`package.json`, `Cargo.toml`, `pyproject.toml`, etc.).\n\n## Step 2: Map Structure (`file-analysis:structure-mapped`)\n- Run `tree -L 2 -d` or `find . -type d -maxdepth 2` to capture the top-level directory layout.\n- Identify standard directories: `src/`, `lib/`, `tests/`, `docs/`, `scripts/`, `configs/`.\n- Note any non-standard organization patterns that may affect downstream analysis.\n\n## Step 3: Detect Patterns (`file-analysis:patterns-detected`)\n- Use `find . -name \"*.ext\" -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" | wc -l` to count files by extension.\n- Identify dominant languages and their file distributions.\n- Note configuration files, generated files, and vendored dependencies.\n- Run `wc -l $(find . -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" -name \"*.py\" -o -name \"*.rs\" | head -20)` to sample file sizes.\n\n## Step 4: Note Hotspots (`file-analysis:hotspots-noted`)\n- Identify large files (potential \"god objects\"): `find . -type f -exec wc -l {} + | sort -rn | head -10`.\n- Flag deeply nested directories that may indicate complexity.\n- Note files with unusual naming conventions or placement.\n\n## Exit Criteria\n- `TodoWrite` items are completed with concrete observations.\n- Downstream workflows (architecture review, refactoring) have structural context.\n- File counts, directory layout, and hotspots are documented for reference.\n\nFile v1.9.16:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-file-analysis\",\n  \"version\": \"1.9.16\",\n  \"publishedAt\": 1784059039321\n}\n\nFile v1.9.16:skill-card.md\n\n## Description: <br>\nMaps file structure and module organization of a codebase for architecture reviews, refactoring planning, or migration scope estimation. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and engineers use this skill to map repository structure, module boundaries, file distributions, and hotspots before architecture reviews, refactoring plans, or migration scoping. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Repository mapping can expose directory names, filenames, and line-count details from the working tree. <br>\nMitigation: Run the skill only from the intended project directory and review or redact findings before sharing them. <br>\nRisk: Broad file-structure scans can produce noisy or expensive results in large repositories. <br>\nMitigation: Scope the analysis root and exclude generated, dependency, virtual environment, and VCS directories where practical. <br>\n\n\n## Reference(s): <br>\n- [Nm Sanctum File Analysis on ClawHub](https://clawhub.ai/athola/skills/nm-sanctum-file-analysis) <br>\n- [Sanctum homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Text, Markdown, Shell commands, Guidance] <br>\n**Output Format:** [Markdown narrative with shell command examples and checklist status updates] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Run from the intended project directory; no persistent output file is specified.] <br>\n\n## Skill Version(s): <br>\n1.9.16 (source: server release evidence; artifact frontmatter lists 1.9.8) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.9.14: 3 files, 2944 bytes\n\nFiles: skill-card.md (2102b), SKILL.md (3147b), _meta.json (144b)\n\nFile v1.9.14:SKILL.md\n\n---\nname: file-analysis\ndescription: |\n  Maps file structure and module organization of a codebase. Use before architecture reviews, refactoring planning, or migration scope estimation\nversion: 1.9.8\ntriggers:\n  - files\n  - structure\n  - analysis\n  - codebase\n  - exploration\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# File Analysis\n\n## When To Use\n- Before architecture reviews to understand module boundaries and file organization.\n- When exploring unfamiliar codebases to map structure before making changes.\n- As input to scope estimation for refactoring or migration work.\n\n## When NOT To Use\n\n- General code exploration - use the Explore agent\n- Searching for specific patterns - use Grep directly\n\n## Required TodoWrite Items\n1. `file-analysis:root-identified`\n2. `file-analysis:structure-mapped`\n3. `file-analysis:patterns-detected`\n4. `file-analysis:hotspots-noted`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Identify Root (`file-analysis:root-identified`)\n- Confirm the analysis root directory with `pwd`.\n- Note any monorepo boundaries, workspace roots, or subproject paths.\n- Capture the project type (language, framework) from manifest files (`package.json`, `Cargo.toml`, `pyproject.toml`, etc.).\n\n## Step 2: Map Structure (`file-analysis:structure-mapped`)\n- Run `tree -L 2 -d` or `find . -type d -maxdepth 2` to capture the top-level directory layout.\n- Identify standard directories: `src/`, `lib/`, `tests/`, `docs/`, `scripts/`, `configs/`.\n- Note any non-standard organization patterns that may affect downstream analysis.\n\n## Step 3: Detect Patterns (`file-analysis:patterns-detected`)\n- Use `find . -name \"*.ext\" -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" | wc -l` to count files by extension.\n- Identify dominant languages and their file distributions.\n- Note configuration files, generated files, and vendored dependencies.\n- Run `wc -l $(find . -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" -name \"*.py\" -o -name \"*.rs\" | head -20)` to sample file sizes.\n\n## Step 4: Note Hotspots (`file-analysis:hotspots-noted`)\n- Identify large files (potential \"god objects\"): `find . -type f -exec wc -l {} + | sort -rn | head -10`.\n- Flag deeply nested directories that may indicate complexity.\n- Note files with unusual naming conventions or placement.\n\n## Exit Criteria\n- `TodoWrite` items are completed with concrete observations.\n- Downstream workflows (architecture review, refactoring) have structural context.\n- File counts, directory layout, and hotspots are documented for reference.\n\nFile v1.9.14:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-file-analysis\",\n  \"version\": \"1.9.14\",\n  \"publishedAt\": 1782842712938\n}\n\nFile v1.9.14:skill-card.md\n\n## Description: <br>\nMaps file structure and module organization of a codebase before architecture reviews, refactoring planning, or migration scope estimation. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and engineers use this skill to survey a repository's layout, dominant file types, module boundaries, and structural hotspots before planning architecture reviews, refactors, or migrations. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Repository mapping can place local file names, directory layout, and approximate file sizes or line counts into the active agent context. <br>\nMitigation: Run it only on repositories where that structural metadata is acceptable to disclose to the active agent session. <br>\nRisk: The reviewed artifact is only the standalone skill text, while the referenced Night Market plugin may include additional behavior. <br>\nMitigation: Review and scan the separate Night Market plugin before installing the full plugin experience. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-sanctum-file-analysis) <br>\n- [Metadata homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, shell commands, guidance] <br>\n**Output Format:** [Markdown with checklist items and inline shell commands] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Produces repository structure observations, file counts, and hotspot notes for downstream planning.] <br>\n\n## Skill Version(s): <br>\n1.9.14 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.9.13: 3 files, 2861 bytes\n\nFiles: skill-card.md (1873b), SKILL.md (3147b), _meta.json (144b)\n\nFile v1.9.13:SKILL.md\n\n---\nname: file-analysis\ndescription: |\n  Maps file structure and module organization of a codebase. Use before architecture reviews, refactoring planning, or migration scope estimation\nversion: 1.9.8\ntriggers:\n  - files\n  - structure\n  - analysis\n  - codebase\n  - exploration\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# File Analysis\n\n## When To Use\n- Before architecture reviews to understand module boundaries and file organization.\n- When exploring unfamiliar codebases to map structure before making changes.\n- As input to scope estimation for refactoring or migration work.\n\n## When NOT To Use\n\n- General code exploration - use the Explore agent\n- Searching for specific patterns - use Grep directly\n\n## Required TodoWrite Items\n1. `file-analysis:root-identified`\n2. `file-analysis:structure-mapped`\n3. `file-analysis:patterns-detected`\n4. `file-analysis:hotspots-noted`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Identify Root (`file-analysis:root-identified`)\n- Confirm the analysis root directory with `pwd`.\n- Note any monorepo boundaries, workspace roots, or subproject paths.\n- Capture the project type (language, framework) from manifest files (`package.json`, `Cargo.toml`, `pyproject.toml`, etc.).\n\n## Step 2: Map Structure (`file-analysis:structure-mapped`)\n- Run `tree -L 2 -d` or `find . -type d -maxdepth 2` to capture the top-level directory layout.\n- Identify standard directories: `src/`, `lib/`, `tests/`, `docs/`, `scripts/`, `configs/`.\n- Note any non-standard organization patterns that may affect downstream analysis.\n\n## Step 3: Detect Patterns (`file-analysis:patterns-detected`)\n- Use `find . -name \"*.ext\" -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" | wc -l` to count files by extension.\n- Identify dominant languages and their file distributions.\n- Note configuration files, generated files, and vendored dependencies.\n- Run `wc -l $(find . -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" -name \"*.py\" -o -name \"*.rs\" | head -20)` to sample file sizes.\n\n## Step 4: Note Hotspots (`file-analysis:hotspots-noted`)\n- Identify large files (potential \"god objects\"): `find . -type f -exec wc -l {} + | sort -rn | head -10`.\n- Flag deeply nested directories that may indicate complexity.\n- Note files with unusual naming conventions or placement.\n\n## Exit Criteria\n- `TodoWrite` items are completed with concrete observations.\n- Downstream workflows (architecture review, refactoring) have structural context.\n- File counts, directory layout, and hotspots are documented for reference.\n\nFile v1.9.13:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-file-analysis\",\n  \"version\": \"1.9.13\",\n  \"publishedAt\": 1782577386634\n}\n\nFile v1.9.13:skill-card.md\n\n## Description: <br>\nMaps file structure and module organization of a codebase for architecture reviews, refactoring planning, and migration scope estimation. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and engineers use this skill to quickly map repository structure, identify project organization patterns, and capture file-level hotspots before review or refactoring work. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill can activate on broad analysis or exploration requests and summarize local file structure in sensitive repositories. <br>\nMitigation: Invoke it explicitly or narrow activation triggers when working in sensitive repositories, and review generated structural summaries before sharing them. <br>\n\n\n## Reference(s): <br>\n- [ClawHub Skill Page](https://clawhub.ai/athola/skills/nm-sanctum-file-analysis) <br>\n- [Configured Homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, shell commands, guidance] <br>\n**Output Format:** [Markdown notes with command examples and structured observations] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Summarizes directory layout, file distributions, configuration signals, and likely complexity hotspots.] <br>\n\n## Skill Version(s): <br>\n1.9.13 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.9.12: 3 files, 2964 bytes\n\nFiles: skill-card.md (2180b), SKILL.md (3147b), _meta.json (144b)\n\nFile v1.9.12:SKILL.md\n\n---\nname: file-analysis\ndescription: |\n  Maps file structure and module organization of a codebase. Use before architecture reviews, refactoring planning, or migration scope estimation\nversion: 1.9.8\ntriggers:\n  - files\n  - structure\n  - analysis\n  - codebase\n  - exploration\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# File Analysis\n\n## When To Use\n- Before architecture reviews to understand module boundaries and file organization.\n- When exploring unfamiliar codebases to map structure before making changes.\n- As input to scope estimation for refactoring or migration work.\n\n## When NOT To Use\n\n- General code exploration - use the Explore agent\n- Searching for specific patterns - use Grep directly\n\n## Required TodoWrite Items\n1. `file-analysis:root-identified`\n2. `file-analysis:structure-mapped`\n3. `file-analysis:patterns-detected`\n4. `file-analysis:hotspots-noted`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Identify Root (`file-analysis:root-identified`)\n- Confirm the analysis root directory with `pwd`.\n- Note any monorepo boundaries, workspace roots, or subproject paths.\n- Capture the project type (language, framework) from manifest files (`package.json`, `Cargo.toml`, `pyproject.toml`, etc.).\n\n## Step 2: Map Structure (`file-analysis:structure-mapped`)\n- Run `tree -L 2 -d` or `find . -type d -maxdepth 2` to capture the top-level directory layout.\n- Identify standard directories: `src/`, `lib/`, `tests/`, `docs/`, `scripts/`, `configs/`.\n- Note any non-standard organization patterns that may affect downstream analysis.\n\n## Step 3: Detect Patterns (`file-analysis:patterns-detected`)\n- Use `find . -name \"*.ext\" -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" | wc -l` to count files by extension.\n- Identify dominant languages and their file distributions.\n- Note configuration files, generated files, and vendored dependencies.\n- Run `wc -l $(find . -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" -name \"*.py\" -o -name \"*.rs\" | head -20)` to sample file sizes.\n\n## Step 4: Note Hotspots (`file-analysis:hotspots-noted`)\n- Identify large files (potential \"god objects\"): `find . -type f -exec wc -l {} + | sort -rn | head -10`.\n- Flag deeply nested directories that may indicate complexity.\n- Note files with unusual naming conventions or placement.\n\n## Exit Criteria\n- `TodoWrite` items are completed with concrete observations.\n- Downstream workflows (architecture review, refactoring) have structural context.\n- File counts, directory layout, and hotspots are documented for reference.\n\nFile v1.9.12:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-file-analysis\",\n  \"version\": \"1.9.12\",\n  \"publishedAt\": 1781839109955\n}\n\nFile v1.9.12:skill-card.md\n\n## Description: <br>\nMaps file structure and module organization of a codebase before architecture reviews, refactoring planning, or migration scope estimation. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and engineers use this skill to map an unfamiliar repository's layout, dominant file patterns, and likely complexity hotspots before planning reviews, refactors, or migrations. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Broad trigger words such as files, structure, analysis, codebase, or exploration may activate the skill during general repository discussions. <br>\nMitigation: Use it in workspaces where local file inspection is acceptable, and review the generated observations before relying on them. <br>\nRisk: File listings, counts, and hotspot summaries can reveal project structure or sensitive filenames. <br>\nMitigation: Avoid applying the skill to repositories whose structural metadata should not be shared in the active agent session. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/athola/nm-sanctum-file-analysis) <br>\n- [Sanctum homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum) <br>\n- [Publisher profile](https://clawhub.ai/user/athola) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, shell commands, guidance] <br>\n**Output Format:** [Markdown guidance with shell command examples and checklist items.] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Produces structural observations, file counts, directory layout notes, and hotspot summaries; no credentials are required.] <br>\n\n## Skill Version(s): <br>\n1.9.12 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.3: 3 files, 2908 bytes\n\nFiles: skill-card.md (2080b), SKILL.md (3147b), _meta.json (143b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: file-analysis\ndescription: |\n  Maps file structure and module organization of a codebase. Use before architecture reviews, refactoring planning, or migration scope estimation\nversion: 1.9.8\ntriggers:\n  - files\n  - structure\n  - analysis\n  - codebase\n  - exploration\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# File Analysis\n\n## When To Use\n- Before architecture reviews to understand module boundaries and file organization.\n- When exploring unfamiliar codebases to map structure before making changes.\n- As input to scope estimation for refactoring or migration work.\n\n## When NOT To Use\n\n- General code exploration - use the Explore agent\n- Searching for specific patterns - use Grep directly\n\n## Required TodoWrite Items\n1. `file-analysis:root-identified`\n2. `file-analysis:structure-mapped`\n3. `file-analysis:patterns-detected`\n4. `file-analysis:hotspots-noted`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Identify Root (`file-analysis:root-identified`)\n- Confirm the analysis root directory with `pwd`.\n- Note any monorepo boundaries, workspace roots, or subproject paths.\n- Capture the project type (language, framework) from manifest files (`package.json`, `Cargo.toml`, `pyproject.toml`, etc.).\n\n## Step 2: Map Structure (`file-analysis:structure-mapped`)\n- Run `tree -L 2 -d` or `find . -type d -maxdepth 2` to capture the top-level directory layout.\n- Identify standard directories: `src/`, `lib/`, `tests/`, `docs/`, `scripts/`, `configs/`.\n- Note any non-standard organization patterns that may affect downstream analysis.\n\n## Step 3: Detect Patterns (`file-analysis:patterns-detected`)\n- Use `find . -name \"*.ext\" -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" | wc -l` to count files by extension.\n- Identify dominant languages and their file distributions.\n- Note configuration files, generated files, and vendored dependencies.\n- Run `wc -l $(find . -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" -name \"*.py\" -o -name \"*.rs\" | head -20)` to sample file sizes.\n\n## Step 4: Note Hotspots (`file-analysis:hotspots-noted`)\n- Identify large files (potential \"god objects\"): `find . -type f -exec wc -l {} + | sort -rn | head -10`.\n- Flag deeply nested directories that may indicate complexity.\n- Note files with unusual naming conventions or placement.\n\n## Exit Criteria\n- `TodoWrite` items are completed with concrete observations.\n- Downstream workflows (architecture review, refactoring) have structural context.\n- File counts, directory layout, and hotspots are documented for reference.\n\nFile v1.0.3:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-file-analysis\",\n  \"version\": \"1.0.3\",\n  \"publishedAt\": 1781796016632\n}\n\nFile v1.0.3:skill-card.md\n\n## Description: <br>\nMaps file structure and module organization of a codebase before architecture reviews, refactoring planning, or migration scope estimation. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and engineers use this skill to map project layout, dominant file patterns, and complexity hotspots before architecture reviews, refactoring planning, or migration scoping. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may enumerate file paths, directory structure, and line counts from the selected project tree. <br>\nMitigation: Run it from the intended project root and review generated observations before sharing them outside the environment. <br>\nRisk: Broad activation terms may cause unwanted structural analysis in routine codebase discussions. <br>\nMitigation: Invoke the skill explicitly for architecture, refactoring, or migration scoping work, and tighten triggers if activations become noisy. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/athola/nm-sanctum-file-analysis) <br>\n- [Metadata homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Text, Markdown, Shell commands, Guidance] <br>\n**Output Format:** [Markdown with shell-command examples and checklist-style observations] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Read-only structural analysis that may include file paths, directory layouts, file counts, and hotspot summaries.] <br>\n\n## Skill Version(s): <br>\n1.0.3 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.2: 3 files, 2976 bytes\n\nFiles: skill-card.md (1856b), SKILL.md (3350b), _meta.json (143b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: file-analysis\ndescription: |\n  Map file structure and organization for downstream review and refactoring workflows\nversion: 1.9.5\ntriggers:\n  - files\n  - structure\n  - analysis\n  - codebase\n  - exploration\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# File Analysis\n\n## When To Use\n- Before architecture reviews to understand module boundaries and file organization.\n- When exploring unfamiliar codebases to map structure before making changes.\n- As input to scope estimation for refactoring or migration work.\n\n## When NOT To Use\n\n- General code exploration - use the Explore agent\n- Searching for specific patterns - use Grep directly\n\n## Required TodoWrite Items\n1. `file-analysis:root-identified`\n2. `file-analysis:structure-mapped`\n3. `file-analysis:patterns-detected`\n4. `file-analysis:hotspots-noted`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Identify Root (`file-analysis:root-identified`)\n- Confirm the analysis root directory with `pwd`.\n- Note any monorepo boundaries, workspace roots, or subproject paths.\n- Capture the project type (language, framework) from manifest files (`package.json`, `Cargo.toml`, `pyproject.toml`, etc.).\n\n## Step 2: Map Structure (`file-analysis:structure-mapped`)\n- Run `tree -L 2 -d` or `find . -type d -maxdepth 2` to capture the top-level directory layout.\n- Identify standard directories: `src/`, `lib/`, `tests/`, `docs/`, `scripts/`, `configs/`.\n- Note any non-standard organization patterns that may affect downstream analysis.\n\n## Step 3: Detect Patterns (`file-analysis:patterns-detected`)\n- Use `find . -name \"*.ext\" -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" | wc -l` to count files by extension.\n- Identify dominant languages and their file distributions.\n- Note configuration files, generated files, and vendored dependencies.\n- Run `wc -l $(find . -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" -name \"*.py\" -o -name \"*.rs\" | head -20)` to sample file sizes.\n\n## Step 4: Note Hotspots (`file-analysis:hotspots-noted`)\n- Identify large files (potential \"god objects\"): `find . -type f -exec wc -l {} + | sort -rn | head -10`.\n- Flag deeply nested directories that may indicate complexity.\n- Note files with unusual naming conventions or placement.\n\n## Exit Criteria\n- `TodoWrite` items are completed with concrete observations.\n- Downstream workflows (architecture review, refactoring) have structural context.\n- File counts, directory layout, and hotspots are documented for reference.\n## Troubleshooting\n\n### Common Issues\n\n**Command not found**\nEnsure all dependencies are installed and in PATH\n\n**Permission errors**\nCheck file permissions and run with appropriate privileges\n\n**Unexpected behavior**\nEnable verbose logging with `--verbose` flag\n\nFile v1.0.2:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-file-analysis\",\n  \"version\": \"1.0.2\",\n  \"publishedAt\": 1778293190365\n}\n\nFile v1.0.2:skill-card.md\n\n## Description: <br>\nMap file structure and organization for downstream review and refactoring workflows. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and engineers use this skill to map a repository's directory layout, dominant file types, and structural hotspots before architecture review, refactoring, or migration work. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Running the skill from an overly broad directory can expose local path names and file-size or line-count metadata beyond the intended project. <br>\nMitigation: Start the skill from the specific repository or subdirectory that should be analyzed. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/athola/nm-sanctum-file-analysis) <br>\n- [Publisher profile](https://clawhub.ai/user/athola) <br>\n- [Clawdis homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, shell commands, guidance] <br>\n**Output Format:** [Markdown notes with shell command snippets and structured observations] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May include directory summaries, file counts, language distribution notes, and hotspot observations.] <br>\n\n## Skill Version(s): <br>\n1.0.2 (source: server release metadata; artifact frontmatter reports 1.9.5) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.1: 2 files, 1928 bytes\n\nFiles: SKILL.md (3350b), _meta.json (143b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: file-analysis\ndescription: |\n  Map file structure and organization for downstream review and refactoring workflows\nversion: 1.9.4\ntriggers:\n  - files\n  - structure\n  - analysis\n  - codebase\n  - exploration\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# File Analysis\n\n## When To Use\n- Before architecture reviews to understand module boundaries and file organization.\n- When exploring unfamiliar codebases to map structure before making changes.\n- As input to scope estimation for refactoring or migration work.\n\n## When NOT To Use\n\n- General code exploration - use the Explore agent\n- Searching for specific patterns - use Grep directly\n\n## Required TodoWrite Items\n1. `file-analysis:root-identified`\n2. `file-analysis:structure-mapped`\n3. `file-analysis:patterns-detected`\n4. `file-analysis:hotspots-noted`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Identify Root (`file-analysis:root-identified`)\n- Confirm the analysis root directory with `pwd`.\n- Note any monorepo boundaries, workspace roots, or subproject paths.\n- Capture the project type (language, framework) from manifest files (`package.json`, `Cargo.toml`, `pyproject.toml`, etc.).\n\n## Step 2: Map Structure (`file-analysis:structure-mapped`)\n- Run `tree -L 2 -d` or `find . -type d -maxdepth 2` to capture the top-level directory layout.\n- Identify standard directories: `src/`, `lib/`, `tests/`, `docs/`, `scripts/`, `configs/`.\n- Note any non-standard organization patterns that may affect downstream analysis.\n\n## Step 3: Detect Patterns (`file-analysis:patterns-detected`)\n- Use `find . -name \"*.ext\" -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" | wc -l` to count files by extension.\n- Identify dominant languages and their file distributions.\n- Note configuration files, generated files, and vendored dependencies.\n- Run `wc -l $(find . -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" -name \"*.py\" -o -name \"*.rs\" | head -20)` to sample file sizes.\n\n## Step 4: Note Hotspots (`file-analysis:hotspots-noted`)\n- Identify large files (potential \"god objects\"): `find . -type f -exec wc -l {} + | sort -rn | head -10`.\n- Flag deeply nested directories that may indicate complexity.\n- Note files with unusual naming conventions or placement.\n\n## Exit Criteria\n- `TodoWrite` items are completed with concrete observations.\n- Downstream workflows (architecture review, refactoring) have structural context.\n- File counts, directory layout, and hotspots are documented for reference.\n## Troubleshooting\n\n### Common Issues\n\n**Command not found**\nEnsure all dependencies are installed and in PATH\n\n**Permission errors**\nCheck file permissions and run with appropriate privileges\n\n**Unexpected behavior**\nEnable verbose logging with `--verbose` flag\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-file-analysis\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1778077273419\n}\n\nArchive v1.0.0: 2 files, 1928 bytes\n\nFiles: SKILL.md (3350b), _meta.json (143b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: file-analysis\ndescription: |\n  Map file structure and organization for downstream review and refactoring workflows\nversion: 1.8.2\ntriggers:\n  - files\n  - structure\n  - analysis\n  - codebase\n  - exploration\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# File Analysis\n\n## When To Use\n- Before architecture reviews to understand module boundaries and file organization.\n- When exploring unfamiliar codebases to map structure before making changes.\n- As input to scope estimation for refactoring or migration work.\n\n## When NOT To Use\n\n- General code exploration - use the Explore agent\n- Searching for specific patterns - use Grep directly\n\n## Required TodoWrite Items\n1. `file-analysis:root-identified`\n2. `file-analysis:structure-mapped`\n3. `file-analysis:patterns-detected`\n4. `file-analysis:hotspots-noted`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Identify Root (`file-analysis:root-identified`)\n- Confirm the analysis root directory with `pwd`.\n- Note any monorepo boundaries, workspace roots, or subproject paths.\n- Capture the project type (language, framework) from manifest files (`package.json`, `Cargo.toml`, `pyproject.toml`, etc.).\n\n## Step 2: Map Structure (`file-analysis:structure-mapped`)\n- Run `tree -L 2 -d` or `find . -type d -maxdepth 2` to capture the top-level directory layout.\n- Identify standard directories: `src/`, `lib/`, `tests/`, `docs/`, `scripts/`, `configs/`.\n- Note any non-standard organization patterns that may affect downstream analysis.\n\n## Step 3: Detect Patterns (`file-analysis:patterns-detected`)\n- Use `find . -name \"*.ext\" -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" | wc -l` to count files by extension.\n- Identify dominant languages and their file distributions.\n- Note configuration files, generated files, and vendored dependencies.\n- Run `wc -l $(find . -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" -name \"*.py\" -o -name \"*.rs\" | head -20)` to sample file sizes.\n\n## Step 4: Note Hotspots (`file-analysis:hotspots-noted`)\n- Identify large files (potential \"god objects\"): `find . -type f -exec wc -l {} + | sort -rn | head -10`.\n- Flag deeply nested directories that may indicate complexity.\n- Note files with unusual naming conventions or placement.\n\n## Exit Criteria\n- `TodoWrite` items are completed with concrete observations.\n- Downstream workflows (architecture review, refactoring) have structural context.\n- File counts, directory layout, and hotspots are documented for reference.\n## Troubleshooting\n\n### Common Issues\n\n**Command not found**\nEnsure all dependencies are installed and in PATH\n\n**Permission errors**\nCheck file permissions and run with appropriate privileges\n\n**Unexpected behavior**\nEnable verbose logging with `--verbose` flag\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-file-analysis\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1776279702904\n}","readmeExcerpt":"Skill: file-analysis Owner: athola Summary: Maps file structure and module organization of a codebase. Use before architecture reviews, refactoring planning, or migration scope estimation Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:20:20.967Z | user Release v1.9.19 v1.9.17 | 2026-07-30T05:40:25.226Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:57:19.321Z | user Release v1.9.16 v1.9.14 | 2026-06-30T","codeSnippets":[],"executableExamples":[],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: file-analysis\ndescription: |\n  Maps file structure and module organization of a codebase. Use before architecture reviews, refactoring planning, or migration scope estimation\nversion: 1.9.8\ntriggers:\n  - files\n  - structure\n  - analysis\n  - codebase\n  - exploration\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.imbue:proof-of-work\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# File Analysis\n\n## When To Use\n- Before architecture reviews to understand module boundaries and file organization.\n- When exploring unfamiliar codebases to map structure before making changes.\n- As input to scope estimation for refactoring or migration work.\n\n## When NOT To Use\n\n- General code exploration - use the Explore agent\n- Searching for specific patterns - use Grep directly\n\n## Required TodoWrite Items\n1. `file-analysis:root-identified`\n2. `file-analysis:structure-mapped`\n3. `file-analysis:patterns-detected`\n4. `file-analysis:hotspots-noted`\n\nMark each item as complete as you finish the corresponding step.\n\n## Step 1: Identify Root (`file-analysis:root-identified`)\n- Confirm the analysis root directory with `pwd`.\n- Note any monorepo boundaries, workspace roots, or subproject paths.\n- Capture the project type (language, framework) from manifest files (`package.json`, `Cargo.toml`, `pyproject.toml`, etc.).\n\n## Step 2: Map Structure (`file-analysis:structure-mapped`)\n- Run `tree -L 2 -d` or `find . -type d -maxdepth 2` to capture the top-level directory layout.\n- Identify standard directories: `src/`, `lib/`, `tests/`, `docs/`, `scripts/`, `configs/`.\n- Note any non-standard organization patterns that may affect downstream analysis.\n\n## Step 3: Detect Patterns (`file-analysis:patterns-detected`)\n- Use `find . -name \"*.ext\" -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" | wc -l` to count files by extension.\n- Identify dominant languages and their file distributions.\n- Note configuration files, generated files, and vendored dependencies.\n- Run `wc -l $(find . -not -path \"*/.venv/*\" -not -path \"*/__pycache__/*\" -not -path \"*/node_modules/*\" -not -path \"*/.git/*\" -name \"*.py\" -o -name \"*.rs\" | head -20)` to sample file sizes.\n\n## Step 4: Note Hotspots (`file-analysis:hotspots-noted`)\n- Identify large files (potential \"god objects\"): `find . -type f -exec wc -l {} + | sort -rn | head -10`.\n- Flag deeply nested directories that may indicate complexity.\n- Note files with unusual naming conventions or placement.\n\n## Exit Criteria\n- `TodoWrite` items are completed with concrete observations.\n- Downstream w"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-file-analysis\",\n  \"version\": \"1.9.19\",\n  \"publishedAt\": 1787750420967\n}"},{"path":"skill-card.md","content":"## Description:\n\nMaps file structure and module organization of a codebase for architecture reviews, refactoring planning, or migration scope estimation.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[athola](https://clawhub.ai/user/athola)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and engineers use this skill to map repository layout, identify module boundaries, and collect structural observations before architecture review, refactoring, or migration planning.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad trigger words may cause the skill to run during general codebase conversations and enumerate structure in sensitive repositories.\n\nMitigation: Confirm the intended analysis root and scope before relying on or sharing structural file enumeration.\n\nRisk: Repository layout and file names may reveal sensitive project details in generated analysis notes.\n\nMitigation: Review the generated observations before sharing them outside the intended audience.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-sanctum-file-analysis)\n- [OpenClaw homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, guidance]\n\n**Output Format:** [Markdown with shell command snippets and structured observations]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Includes directory layout, file counts, module organization, and hotspot observations when available.]\n\n## Skill Version(s):\n\n1.9.19 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Maps file structure and module organization of a codebase. Use before architecture reviews, refactoring planning, or migration scope estimation Skill: file-analysis Owner: athola Summary: Maps file structure and module organization of a codebase. Use before architecture reviews, refactoring planning, or migration scope estimation Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:20:20.967Z | user Release v1.9.19 v1.9.17 | 2026-07-30T05:40:25.226Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:57:19.321Z | user Release v1.9.16 v1.9.14 | 2026-06-30T","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1026,"uniquenessScore":53,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-10T10:09:13.488Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-10T10:09:13.488Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-10T13:33:25.584Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}