[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77P971W6WC9GA5D0QTRBFAH":3,"skill-same:01M77P971W6WC9GA5D0QTRBFAH":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M77P971W6WC9GA5D0QTRBFAH","northdata",null,"Use NorthData (German commercial-register + financials API) to look up companies, owners, representatives, financials, publications, and person records. Triggers on queries about NorthData itself, looking up a specific German company (GmbH, UG, KG, HRB\u002FHRA register entries), finding owners \u002F Geschäftsführer \u002F Gesellschafter, reading a company's revenue \u002F earnings \u002F balance sheet, searching by NACE segment or legal form or geography, checking NorthData credit usage, or power-searching for acquisition \u002F lead candidates. Activates for terms like \"northdata\", \"north data\", \"Handelsregister\", \"HRB\", \"HRA\", \"Gesellschafter\", \"Geschäftsführer\", \"GmbH Finanzen\", \"Firma recherchieren\", \"NACE-Suche\", \"Power Search\", \"company profile\". Provides best-practice guidance for both the `northdata` CLI (Claude Code \u002F terminal) and the NorthData MCP server (Claude Desktop \u002F any MCP client) — whichever is available in the current environment.","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fn\u002Fnorthdata\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: northdata\ndescription: Use NorthData (German commercial-register + financials API) to look up companies, owners, representatives, financials, publications, and person records. Triggers on queries about NorthData itself, looking up a specific German company (GmbH, UG, KG, HRB\u002FHRA register entries), finding owners \u002F Geschäftsführer \u002F Gesellschafter, reading a company's revenue \u002F earnings \u002F balance sheet, searching by NACE segment or legal form or geography, checking NorthData credit usage, or power-searching for acquisition \u002F lead candidates. Activates for terms like \"northdata\", \"north data\", \"Handelsregister\", \"HRB\", \"HRA\", \"Gesellschafter\", \"Geschäftsführer\", \"GmbH Finanzen\", \"Firma recherchieren\", \"NACE-Suche\", \"Power Search\", \"company profile\". Provides best-practice guidance for both the `northdata` CLI (Claude Code \u002F terminal) and the NorthData MCP server (Claude Desktop \u002F any MCP client) — whichever is available in the current environment.\n---\n\n# NorthData Companion Skill\n\nThis skill is the best-practice guide for working with the NorthData API through either:\n\n1. **`northdata` CLI** — a command-line tool, typically used in Claude Code or a terminal.\n2. **NorthData MCP server** — a set of tools exposed over the Model Context Protocol, typically used in Claude Desktop \u002F Cursor \u002F other MCP clients.\n\nBoth surfaces are built on the same `NorthDataClient` and share the same credit-guard discipline. Pick whichever is available in the current environment — this skill covers both.\n\n## Detect what's available\n\nBefore deciding, check what's reachable:\n\n| Check | Available? |\n|---|---|\n| MCP tools named `suggest`, `company`, `person`, … | Use MCP. |\n| `northdata` on `$PATH` (try `which northdata` or `northdata --version`) | Use CLI. |\n| Neither | Ask the user to install — point at `northdata-cli` (pipx) and\u002For the MCP server config. |\n\nIf both are available: **prefer MCP** when running inside an MCP-aware client (clearer tool telemetry, structured errors). **Prefer CLI** in Claude Code or any shell-driven context.\n\n## The one rule you must internalize\n\n**NorthData charges per returned company, not per HTTP call.** A single `search --limit 100` costs up to 100 credits in one go. Every billed call goes through the two-tier credit guard:\n\n| Tier | Default | How to relax |\n|---|---|---|\n| Approval threshold — `limit > 25` needs `--approve-high-cost` (CLI) or `approve_high_cost=true` (MCP) | `25` | `NORTHDATA_APPROVAL_THRESHOLD` env |\n| Absolute maximum — hard cap, flag-immune | `100` | `NORTHDATA_ABSOLUTE_MAX` env — set by a human, never by an agent |\n\nNever suggest raising either without a clear reason from the user.\n\n## Default workflow (use this order)\n\n1. **Start free.** `suggest`, `reference_*`, `billing` — zero credits. Use them to find the right company \u002F confirm register IDs \u002F check remaining quota before committing.\n2. **Dry-run anything billed.** Both surfaces accept `--dry-run` (CLI) or `dry_run=true` (MCP). Use it first when parameters are uncertain — it builds the URL without calling the API.\n3. **One `company` call is usually enough.** It returns owners, representatives, financials, sheets, events, contact extras. Don't also call `publications` or `person` unless you specifically need shareholder lists or a person's birth date.\n4. **Log watch.** After billed calls, `credits` (CLI) \u002F `local_credit_log` (MCP) shows what this session spent. `billing` shows what NorthData counts remotely.\n\n## Tool reference\n\n### Free tools\n\n| Purpose | CLI | MCP |\n|---|---|---|\n| Autocomplete a name | `northdata suggest \"Example GmbH\"` | `suggest` |\n| Current period usage | `northdata billing` | `billing` |\n| API reference (standards, countries, …) | `northdata reference overview` | `reference_overview` |\n| Segment codes for a standard | `northdata reference segments --standard NACE2025` | `reference_segment_codes` |\n| Local (session) credit log | `northdata credits` | `local_credit_log` |\n\n### Billed tools\n\n| Purpose | CLI | MCP | Cost |\n|---|---|---|---|\n| Full company profile | `northdata company --name \"X\" --city \"Y\"` or `--register \"HRB 1\u002FMünchen\"` | `company` | **1** |\n| Person lookup (birth date, roles) | `northdata person Max Mustermann --city München` | `person` | **1** |\n| Publications (e.g. Gesellschafterliste) | `northdata publications --name \"X\" --source Hrb` | `publications` | **1** |\n| Power search (filtered) | `northdata search --segment-codes 62 --legal-forms GmbH --limit 5` | `search` | **up to `limit`** |\n\nAll billed tools accept `--dry-run` \u002F `dry_run=true`.\n\n## Common workflows\n\n### \"Find Company X and tell me about it\"\n\n1. `suggest \"Company X\"` (free) — pick the right one if multiple.\n2. `company --register \"\u003Cregister from suggest>\"` **or** `--name \"\u003Cexact name>\" --city \"\u003Ccity>\"` (1 credit).\n3. Done. Owners, representatives, financials, sheets, events all come back in one payload.\n\n### \"Who owns \u002F runs Company X?\"\n\n`company` returns `owners` (Gesellschafter) and `representatives` (Geschäftsführer) in the same response. Don't chain multiple calls — one `company` call is enough.\n\nFor the **birth date** of a named person (e.g. succession planning), follow up with `person --first-name … --last-name … --city …` (1 credit).\n\n### \"Find me companies matching these criteria\"\n\nUse `search` (power search). Always:\n\n- Set `segment_codes` (NACE) and `legal_forms` — an unfiltered search is expensive and rarely useful.\n- Keep `limit` low (default `5`). Only raise with explicit user approval.\n- Use `--dry-run` first to sanity-check parameters.\n- For geo-filters combine `address` + `max_distance_km`.\n- Indicators: `revenue_min\u002Fmax`, `earnings_min\u002Fmax` narrow down the result set before spending credits.\n\nExample (CLI):\n```bash\nnorthdata search \\\n  --segment-codes \"62|63\" \\\n  --legal-forms \"GmbH|UG\" \\\n  --address \"Munich\" --max-distance-km 150 \\\n  --revenue-min 5000000 --revenue-max 50000000 \\\n  --limit 5 --dry-run\n```\n\nVerify the URL, then re-run without `--dry-run`.\n\nPaginate via the `pos` token in the previous response's `nextPos`.\n\n### \"Check if a register ID is valid before I spend a credit\"\n\n`suggest` returns the canonical `register.uniqueKey` and `register.id`. That's free. Then pass `--register` to `company` exactly as shown.\n\n### \"How many credits am I using?\"\n\n- Remote total (period): `billing`\n- This session only (local log): `credits` \u002F `local_credit_log`\n\n## Common pitfalls\n\n### `HTTP 404 \"not found\"` on `company --register`\n\nThe register string must match NorthData's format. If `\"HRB 296816\u002FMünchen\"` returns 404, try:\n\n1. `suggest` first — copy the exact `register.id` (e.g. `\"HRB 296816\"`) and `register.uniqueKey` from the response.\n2. Fall back to `--name + --city` — more forgiving than register matching.\n\n### Only `numberOfRequests` seems to count unique calls\n\nNorthData's `billing` endpoint returns **unique** requests per period. Repeated identical calls (same company, same day) don't increment the counter. The local credit log counts every attempted call regardless.\n\n### `search` with no segment filter\n\nNever run `search` with empty `segment_codes` and `legal_forms`. The credit guard allows it, but the cost\u002Fsignal ratio is terrible. Always scope.\n\n### Umlauts in register strings\n\nURL-encoding is automatic in both surfaces. You can pass `\"München\"` directly — no manual percent-encoding needed.\n\n### `--approve-high-cost` \u002F `approve_high_cost=true`\n\nOnly set when the user has explicitly agreed to spend more. Never set preemptively \"to make it work\".\n\n## Environment knobs\n\n| Var | Purpose |\n|---|---|\n| `NORTHDATA_API_KEY` | API key (required) |\n| `NORTHDATA_APPROVAL_THRESHOLD` | Raises the soft threshold (default 25) |\n| `NORTHDATA_ABSOLUTE_MAX` | Raises the hard ceiling (default 100) |\n| `NORTHDATA_CREDIT_LOG` | Overrides local log location |\n\n## When the user is stuck\n\n| Symptom | Likely cause | Fix |\n|---|---|---|\n| `No API key found` | `NORTHDATA_API_KEY` not set | Export it, or (CLI) pass `--api-key` |\n| `credit-guard: limit=X exceeds APPROVAL_THRESHOLD` | High `--limit` without opt-in | Lower limit or add `--approve-high-cost` |\n| `credit-guard: limit=X exceeds ABSOLUTE_MAX` | Above hard cap | Split into paginated calls via `pos`, or raise env var |\n| `api error: HTTP 429` | Rate-limited | Wait, retry later. Client already retries once. |\n| `api error: HTTP 404` on `company` | Bad register ID or unknown name | Use `suggest` first to get canonical identifiers |\n| Tools not visible in Claude Desktop | MCP server not registered or Claude not fully restarted | Check `~\u002FLibrary\u002FApplication Support\u002FClaude\u002Fclaude_desktop_config.json`; fully quit with ⌘Q |\n\n## Resources\n\n- NorthData API docs: \u003Chttps:\u002F\u002Fgithub.com\u002Fnorthdata\u002Fapi>\n- CLI package: `northdata-cli\u002F` (this repo)\n- MCP server: `northdata-mcp\u002F` (this repo)\n","# NorthData Companion Skill\n\nThis skill is the best-practice guide for working with the NorthData API through either:\n\n1. **`northdata` CLI** — a command-line tool, typically used in Claude Code or a terminal.\n2. **NorthData MCP server** — a set of tools exposed over the Model Context Protocol, typically used in Claude Desktop \u002F Cursor \u002F other MCP clients.\n\nBoth surfaces are built on the same `NorthDataClient` and share the same credit-guard discipline. Pick whichever is available in the current environment — this skill covers both.\n\n## Detect what's available\n\nBefore deciding, check what's reachable:\n\n| Check | Available? |\n|---|---|\n| MCP tools named `suggest`, `company`, `person`, … | Use MCP. |\n| `northdata` on `$PATH` (try `which northdata` or `northdata --version`) | Use CLI. |\n| Neither | Ask the user to install — point at `northdata-cli` (pipx) and\u002For the MCP server config. |\n\nIf both are available: **prefer MCP** when running inside an MCP-aware client (clearer tool telemetry, structured errors). **Prefer CLI** in Claude Code or any shell-driven context.\n\n## The one rule you must internalize\n\n**NorthData charges per returned company, not per HTTP call.** A single `search --limit 100` costs up to 100 credits in one go. Every billed call goes through the two-tier credit guard:\n\n| Tier | Default | How to relax |\n|---|---|---|\n| Approval threshold — `limit > 25` needs `--approve-high-cost` (CLI) or `approve_high_cost=true` (MCP) | `25` | `NORTHDATA_APPROVAL_THRESHOLD` env |\n| Absolute maximum — hard cap, flag-immune | `100` | `NORTHDATA_ABSOLUTE_MAX` env — set by a human, never by an agent |\n\nNever suggest raising either without a clear reason from the user.\n\n## Default workflow (use this order)\n\n1. **Start free.** `suggest`, `reference_*`, `billing` — zero credits. Use them to find the right company \u002F confirm register IDs \u002F check remaining quota before committing.\n2. **Dry-run anything billed.** Both surfaces accept `--dry-run` (CLI) or `dry_run=true` (MCP). Use it first when parameters are uncertain — it builds the URL without calling the API.\n3. **One `company` call is usually enough.** It returns owners, representatives, financials, sheets, events, contact extras. Don't also call `publications` or `person` unless you specifically need shareholder lists or a person's birth date.\n4. **Log watch.** After billed calls, `credits` (CLI) \u002F `local_credit_log` (MCP) shows what this session spent. `billing` shows what NorthData counts remotely.\n\n## Tool reference\n\n### Free tools\n\n| Purpose | CLI | MCP |\n|---|---|---|\n| Autocomplete a name | `northdata suggest \"Example GmbH\"` | `suggest` |\n| Current period usage | `northdata billing` | `billing` |\n| API reference (standards, countries, …) | `northdata reference overview` | `reference_overview` |\n| Segment codes for a standard | `northdata reference segments --standard NACE2025` | `reference_segment_codes` |\n| Local (session) credit log | `northdata credits` | `local_credit_log` |\n\n### Billed tools\n\n| Purpose | CLI | MCP | Cost |\n|---|---|---|---|\n| Full company profile | `northdata company --name \"X\" --city \"Y\"` or `--register \"HRB 1\u002FMünchen\"` | `company` | **1** |\n| Person lookup (birth date, roles) | `northdata person Max Mustermann --city München` | `person` | **1** |\n| Publications (e.g. Gesellschafterliste) | `northdata publications --name \"X\" --source Hrb` | `publications` | **1** |\n| Power search (filtered) | `northdata search --segment-codes 62 --legal-forms GmbH --limit 5` | `search` | **up to `limit`** |\n\nAll billed tools accept `--dry-run` \u002F `dry_run=true`.\n\n## Common workflows\n\n### \"Find Company X and tell me about it\"\n\n1. `suggest \"Company X\"` (free) — pick the right one if multiple.\n2. `company --register \"\u003Cregister from suggest>\"` **or** `--name \"\u003Cexact name>\" --city \"\u003Ccity>\"` (1 credit).\n3. Done. Owners, representatives, financials, sheets, events all come back in one payload.\n\n### \"Who owns \u002F runs Company X?\"\n\n`company` returns `owners` (Gesellschafter) and `representatives` (Geschäftsführer) in the same response. Don't chain multiple calls — one `company` call is enough.\n\nFor the **birth date** of a named person (e.g. succession planning), follow up with `person --first-name … --last-name … --city …` (1 credit).\n\n### \"Find me companies matching these criteria\"\n\nUse `search` (power search). Always:\n\n- Set `segment_codes` (NACE) and `legal_forms` — an unfiltered search is expensive and rarely useful.\n- Keep `limit` low (default `5`). Only raise with explicit user approval.\n- Use `--dry-run` first to sanity-check parameters.\n- For geo-filters combine `address` + `max_distance_km`.\n- Indicators: `revenue_min\u002Fmax`, `earnings_min\u002Fmax` narrow down the result set before spending credits.\n\nExample (CLI):\n```bash\nnorthdata search \\\n  --segment-codes \"62|63\" \\\n  --legal-forms \"GmbH|UG\" \\\n  --address \"Munich\" --max-distance-km 150 \\\n  --revenue-min 5000000 --revenue-max 50000000 \\\n  --limit 5 --dry-run\n```\n\nVerify the URL, then re-run without `--dry-run`.\n\nPaginate via the `pos` token in the previous response's `nextPos`.\n\n### \"Check if a register ID is valid before I spend a credit\"\n\n`suggest` returns the canonical `register.uniqueKey` and `register.id`. That's free. Then pass `--register` to `company` exactly as shown.\n\n### \"How many credits am I using?\"\n\n- Remote total (period): `billing`\n- This session only (local log): `credits` \u002F `local_credit_log`\n\n## Common pitfalls\n\n### `HTTP 404 \"not found\"` on `company --register`\n\nThe register string must match NorthData's format. If `\"HRB 296816\u002FMünchen\"` returns 404, try:\n\n1. `suggest` first — copy the exact `register.id` (e.g. `\"HRB 296816\"`) and `register.uniqueKey` from the response.\n2. Fall back to `--name + --city` — more forgiving than register matching.\n\n### Only `numberOfRequests` seems to count unique calls\n\nNorthData's `billing` endpoint returns **unique** requests per period. Repeated identical calls (same company, same day) don't increment the counter. The local credit log counts every attempted call regardless.\n\n### `search` with no segment filter\n\nNever run `search` with empty `segment_codes` and `legal_forms`. The credit guard allows it, but the cost\u002Fsignal ratio is terrible. Always scope.\n\n### Umlauts in register strings\n\nURL-encoding is automatic in both surfaces. You can pass `\"München\"` directly — no manual percent-encoding needed.\n\n### `--approve-high-cost` \u002F `approve_high_cost=true`\n\nOnly set when the user has explicitly agreed to spend more. Never set preemptively \"to make it work\".\n\n## Environment knobs\n\n| Var | Purpose |\n|---|---|\n| `NORTHDATA_API_KEY` | API key (required) |\n| `NORTHDATA_APPROVAL_THRESHOLD` | Raises the soft threshold (default 25) |\n| `NORTHDATA_ABSOLUTE_MAX` | Raises the hard ceiling (default 100) |\n| `NORTHDATA_CREDIT_LOG` | Overrides local log location |\n\n## When the user is stuck\n\n| Symptom | Likely cause | Fix |\n|---|---|---|\n| `No API key found` | `NORTHDATA_API_KEY` not set | Export it, or (CLI) pass `--api-key` |\n| `credit-guard: limit=X exceeds APPROVAL_THRESHOLD` | High `--limit` without opt-in | Lower limit or add `--approve-high-cost` |\n| `credit-guard: limit=X exceeds ABSOLUTE_MAX` | Above hard cap | Split into paginated calls via `pos`, or raise env var |\n| `api error: HTTP 429` | Rate-limited | Wait, retry later. Client already retries once. |\n| `api error: HTTP 404` on `company` | Bad register ID or unknown name | Use `suggest` first to get canonical identifiers |\n| Tools not visible in Claude Desktop | MCP server not registered or Claude not fully restarted | Check `~\u002FLibrary\u002FApplication Support\u002FClaude\u002Fclaude_desktop_config.json`; fully quit with ⌘Q |\n\n## Resources\n\n- NorthData API docs: \u003Chttps:\u002F\u002Fgithub.com\u002Fnorthdata\u002Fapi>\n- CLI package: `northdata-cli\u002F` (this repo)\n- MCP server: `northdata-mcp\u002F` (this repo)\n",{"name":5,"description":7},"master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fn\u002Fnorthdata",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill northdata",{"tool":39,"command":40},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill northdata",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill northdata","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fn\u002Fnorthdata\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]