[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M748PC36B7YXEXAGASYNB9EN":3,"skill-same:01M748PC36B7YXEXAGASYNB9EN":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M748PC36B7YXEXAGASYNB9EN","skimmable",null,"Enforce code readability and state minimisation before opening or updating a pull request. Use when code is functionally complete and needs a final simplification pass focused on skimmability: reducing arguments, removing optionality and overrides, collapsing unnecessary abstractions, preferring discriminated unions, adding assertions at boundaries, handling variants exhaustively, deleting incidental changes, and making the diff shorter, clearer, and easier to review.","surfingalien\u002FFinSurfing","surfingalien","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F138259559?v=4","01M71XACCFHNXK70BHYFHFT657","01M71XACDJSV4YA5NZ191F1C8C",1,"MIT","https:\u002F\u002Fgithub.com\u002Fsurfingalien\u002FFinSurfing\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fskimmable\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: skimmable\ndescription: \"Enforce code readability and state minimisation before opening or updating a pull request. Use when code is functionally complete and needs a final simplification pass focused on skimmability: reducing arguments, removing optionality and overrides, collapsing unnecessary abstractions, preferring discriminated unions, adding assertions at boundaries, handling variants exhaustively, deleting incidental changes, and making the diff shorter, clearer, and easier to review.\"\n---\n\n# Skimmable\n\nReview the change as if a tired reviewer must understand it in one fast pass.\n\nPrefer deleting code to explaining code.\n\nKeep the pass narrow: improve readability, state modelling, and diff clarity without changing product behaviour unless the current behaviour is obviously dead, redundant, or inconsistent with types.\n\n## Checklist\n\nApply these rules aggressively:\n\n1. Make the code obvious on first read.\n2. Reduce the number of states the code can represent.\n3. Reduce parameter count.\n4. Remove optional parameters unless they are truly required by callers.\n5. Replace boolean flags and loose option bags with discriminated unions when behaviour differs by mode.\n6. Handle every known variant exhaustively.\n7. Fail on unknown variants immediately.\n8. Trust static types inside the typed core; do not add defensive branches for impossible states.\n9. Assert at boundaries when loading data, parsing input, or reading external systems.\n10. Prefer early returns over nested conditionals.\n11. Keep functions cohesive; do not split logic into many tiny wrappers.\n12. Avoid clever helpers, indirection, and generic abstractions.\n13. Remove overrides, escape hatches, and customisation points unless there is a proven need.\n14. Remove dead paths, temporary compatibility layers, and unrelated edits.\n15. Bias toward fewer lines and fewer moving parts.\n\n## Working method\n\nFollow this order:\n\n### 1. Trim the diff\n\nRemove changes that do not help the main goal of the PR.\n\nDelete:\n- incidental renames\n- opportunistic refactors\n- styling churn with no behavioural value\n- compatibility code for callers that no longer exist\n- unused helpers, types, branches, and comments\n\nIf a simplification requires a separate behavioural decision, stop and call it out instead of smuggling it into the readability pass.\n\n### 2. Simplify data shape first\n\nReduce complexity in types before touching control flow.\n\nPrefer:\n- required fields over optional fields\n- one obvious input shape over many flexible ones\n- discriminated unions over booleans or loosely related fields\n- named domain types over generic maps and stringly typed objects\n\nAsk of every argument:\n- Is it required?\n- Can it be derived?\n- Can two arguments become one domain object?\n- Is it just an override for an API that is too flexible?\n\n### 3. Simplify control flow\n\nMake happy paths short and visible.\n\nPrefer:\n- early returns\n- straight-line code\n- one level of indentation where possible\n- local branching near use\n\nAvoid:\n- nested `if` pyramids\n- defensive `else` branches for impossible states\n- `try\u002Fcatch` for expected values\n- hidden branching spread across helper functions\n\n### 4. Make invalid states loud\n\nAssert at boundaries.\n\nUse assertions when:\n- decoding external data\n- reading files, env vars, or request payloads\n- converting untyped data into typed domain values\n- checking invariants that must hold\n\nAfter the boundary, write simple code that trusts the asserted shape.\n\n### 5. Exhaust variants\n\nWhen code depends on a variant, make the variant explicit and handle all cases.\n\nPrefer a `switch` on a discriminant.\n\nEnd with an exhaustive check or assertion if the language allows it.\n\nDo not silently ignore unknown values.\n\n### 6. Collapse unnecessary abstraction\n\nInline small one-use wrappers when they hide the real logic.\n\nKeep helper functions only when they:\n- remove real duplication\n- encode a domain concept\n- make the caller meaningfully clearer\n\nDo not split a 20-line readable function into five 4-line helpers just to look tidy.\n\n## Preferred patterns\n\n### Keep arguments few and strict\n\nBad signs:\n- more than 3 parameters\n- multiple booleans\n- optional callback plus optional overrides plus optional config\n- passing values already available on an object\n\nPrefer:\n- one required object when the fields belong together\n- one discriminated union when there are modes\n- separate functions when the behaviours are actually different\n\n### Prefer discriminated unions over booleans\n\nIf a boolean changes behaviour, model the behaviour directly.\n\nUse:\n- `kind: \"draft\" | \"published\"`\n- `source: \"cache\" | \"network\"`\n- `status: \"idle\" | \"loading\" | \"success\" | \"error\"`\n\nAvoid:\n- `isDraft`\n- `useCache`\n- `isLoading` plus `error` plus `data` on the same object unless the state machine truly permits all combinations\n\n### Prefer assertions over defensive code\n\nAt boundaries, assert once. Inside, trust the assertion.\n\nAvoid repetitive checks like:\n- `if (!user) return`\n- `if (!user.id) return`\n- `if (typeof user.id !== \"string\") return`\n\nwhen types and boundary validation already guarantee the shape.\n\n### Prefer one obvious path\n\nIf there is a default behaviour, encode it directly.\n\nDo not add overrides like `sortOrder = \"desc\"`, `strategy = \"auto\"`, `separator = \",\"`, `shouldLog = false` unless callers truly need them.\n\nEvery option multiplies states.\n\n## Review prompts\n\nUse these prompts during the pass:\n\n- Can this function lose a parameter?\n- Can this object lose an optional field?\n- Can this branch become an early return?\n- Can these two booleans become one union?\n- Can this helper be inlined?\n- Can this error path become an assertion at the boundary?\n- Can this code fail loudly instead of guessing?\n- Can this diff lose files or lines?\n- If a reviewer skims this in 30 seconds, will the intent be obvious?\n\n## Examples\n\n### Reduce arguments and remove overrides\n\nBefore:\n\n```ts\nfunction createReport(\n  userId: string,\n  includeDrafts = false,\n  sortBy: \"date\" | \"name\" = \"date\",\n  sortDirection: \"asc\" | \"desc\" = \"desc\",\n  limit?: number,\n  overrides?: { timezone?: string; now?: Date }\n) {\n  const now = overrides?.now ?? new Date()\n  const timezone = overrides?.timezone ?? \"UTC\"\n\n  return buildReport({\n    userId,\n    includeDrafts,\n    sortBy,\n    sortDirection,\n    limit,\n    now,\n    timezone,\n  })\n}\n```\n\nAfter:\n\n```ts\ntype ReportScope =\n  | { kind: \"published\" }\n  | { kind: \"all\" }\n\nfunction createReport(userId: string, scope: ReportScope) {\n  return buildReport({ userId, scope, now: new Date(), timezone: \"UTC\" })\n}\n```\n\nPrefer a smaller API. Add configurability only when a real caller needs it.\n\n### Replace booleans with a discriminated union\n\nBefore:\n\n```ts\ntype SaveState = {\n  isSaving: boolean\n  error?: string\n  receipt?: string\n}\n```\n\nAfter:\n\n```ts\ntype SaveState =\n  | { kind: \"idle\" }\n  | { kind: \"saving\" }\n  | { kind: \"error\"; message: string }\n  | { kind: \"saved\"; receipt: string }\n```\n\nThe second version prevents impossible combinations.\n\n### Handle variants exhaustively\n\nBefore:\n\n```ts\nfunction badgeColor(status: Status) {\n  if (status === \"success\") return \"green\"\n  if (status === \"error\") return \"red\"\n  return \"gray\"\n}\n```\n\nAfter:\n\n```ts\nfunction badgeColor(status: Status) {\n  switch (status) {\n    case \"success\":\n      return \"green\"\n    case \"error\":\n      return \"red\"\n    case \"pending\":\n      return \"gray\"\n    default:\n      return assertNever(status)\n  }\n}\n```\n\nUnknown variants should fail loudly during development.\n\n### Assert at the boundary, trust inside\n\nBefore:\n\n```ts\nasync function loadAccount(accountId: string) {\n  const raw = await db.accounts.find(accountId)\n\n  if (!raw) {\n    throw new Error(\"Account not found\")\n  }\n\n  if (typeof raw.email !== \"string\") {\n    throw new Error(\"Invalid account email\")\n  }\n\n  return raw\n}\n\nfunction sendWelcomeEmail(account: any) {\n  if (!account) return\n  if (!account.email) return\n  mailer.send(account.email)\n}\n```\n\nAfter:\n\n```ts\nasync function loadAccount(accountId: string): Promise\u003CAccount> {\n  const raw = await db.accounts.find(accountId)\n  assert(raw, \"Account not found\")\n  assert(typeof raw.email === \"string\", \"Invalid account email\")\n  return raw as Account\n}\n\nfunction sendWelcomeEmail(account: Account) {\n  mailer.send(account.email)\n}\n```\n\nValidate once. Keep the typed core simple.\n\n### Prefer early returns over nesting\n\nBefore:\n\n```ts\nfunction visibleItems(items: Item[], user?: User) {\n  if (user) {\n    if (user.isAdmin) {\n      return items\n    } else {\n      return items.filter((item) => !item.hidden)\n    }\n  } else {\n    return []\n  }\n}\n```\n\nAfter:\n\n```ts\nfunction visibleItems(items: Item[], user?: User) {\n  if (!user) return []\n  if (user.isAdmin) return items\n  return items.filter((item) => !item.hidden)\n}\n```\n\nFlatten the shape of the code.\n\n### Do not split logic into too many tiny functions\n\nBefore:\n\n```ts\nfunction checkout(cart: Cart) {\n  validateCart(cart)\n  const subtotal = calculateSubtotal(cart)\n  const tax = calculateTax(subtotal)\n  const total = calculateTotal(subtotal, tax)\n  return finalizeCheckout(total)\n}\n\nfunction calculateTotal(subtotal: number, tax: number) {\n  return subtotal + tax\n}\n```\n\nAfter:\n\n```ts\nfunction checkout(cart: Cart) {\n  assert(cart.items.length > 0, \"Cart is empty\")\n\n  const subtotal = sum(cart.items.map((item) => item.price))\n  const tax = subtotal * TAX_RATE\n  const total = subtotal + tax\n\n  return finalizeCheckout(total)\n}\n```\n\nKeep trivial logic close to use.\n\n## PR gate\n\nBefore opening or updating the PR, verify:\n\n- The diff contains only necessary changes.\n- Public APIs are stricter or simpler, not more configurable.\n- Modes are modelled explicitly.\n- Variants are handled exhaustively.\n- Assertions exist at boundaries.\n- The core logic trusts types instead of re-checking everything.\n- Functions read top-to-bottom with minimal nesting.\n- Argument counts are low.\n- Helpers exist only when they clarify.\n- The final version is shorter, plainer, and easier to skim.\n\nIf a choice is between clever and obvious, choose obvious.\n\nIf a choice is between flexible and simple, choose simple.\n\nIf a choice is between adding code and deleting code, prefer deleting code.\n","# Skimmable\n\nReview the change as if a tired reviewer must understand it in one fast pass.\n\nPrefer deleting code to explaining code.\n\nKeep the pass narrow: improve readability, state modelling, and diff clarity without changing product behaviour unless the current behaviour is obviously dead, redundant, or inconsistent with types.\n\n## Checklist\n\nApply these rules aggressively:\n\n1. Make the code obvious on first read.\n2. Reduce the number of states the code can represent.\n3. Reduce parameter count.\n4. Remove optional parameters unless they are truly required by callers.\n5. Replace boolean flags and loose option bags with discriminated unions when behaviour differs by mode.\n6. Handle every known variant exhaustively.\n7. Fail on unknown variants immediately.\n8. Trust static types inside the typed core; do not add defensive branches for impossible states.\n9. Assert at boundaries when loading data, parsing input, or reading external systems.\n10. Prefer early returns over nested conditionals.\n11. Keep functions cohesive; do not split logic into many tiny wrappers.\n12. Avoid clever helpers, indirection, and generic abstractions.\n13. Remove overrides, escape hatches, and customisation points unless there is a proven need.\n14. Remove dead paths, temporary compatibility layers, and unrelated edits.\n15. Bias toward fewer lines and fewer moving parts.\n\n## Working method\n\nFollow this order:\n\n### 1. Trim the diff\n\nRemove changes that do not help the main goal of the PR.\n\nDelete:\n- incidental renames\n- opportunistic refactors\n- styling churn with no behavioural value\n- compatibility code for callers that no longer exist\n- unused helpers, types, branches, and comments\n\nIf a simplification requires a separate behavioural decision, stop and call it out instead of smuggling it into the readability pass.\n\n### 2. Simplify data shape first\n\nReduce complexity in types before touching control flow.\n\nPrefer:\n- required fields over optional fields\n- one obvious input shape over many flexible ones\n- discriminated unions over booleans or loosely related fields\n- named domain types over generic maps and stringly typed objects\n\nAsk of every argument:\n- Is it required?\n- Can it be derived?\n- Can two arguments become one domain object?\n- Is it just an override for an API that is too flexible?\n\n### 3. Simplify control flow\n\nMake happy paths short and visible.\n\nPrefer:\n- early returns\n- straight-line code\n- one level of indentation where possible\n- local branching near use\n\nAvoid:\n- nested `if` pyramids\n- defensive `else` branches for impossible states\n- `try\u002Fcatch` for expected values\n- hidden branching spread across helper functions\n\n### 4. Make invalid states loud\n\nAssert at boundaries.\n\nUse assertions when:\n- decoding external data\n- reading files, env vars, or request payloads\n- converting untyped data into typed domain values\n- checking invariants that must hold\n\nAfter the boundary, write simple code that trusts the asserted shape.\n\n### 5. Exhaust variants\n\nWhen code depends on a variant, make the variant explicit and handle all cases.\n\nPrefer a `switch` on a discriminant.\n\nEnd with an exhaustive check or assertion if the language allows it.\n\nDo not silently ignore unknown values.\n\n### 6. Collapse unnecessary abstraction\n\nInline small one-use wrappers when they hide the real logic.\n\nKeep helper functions only when they:\n- remove real duplication\n- encode a domain concept\n- make the caller meaningfully clearer\n\nDo not split a 20-line readable function into five 4-line helpers just to look tidy.\n\n## Preferred patterns\n\n### Keep arguments few and strict\n\nBad signs:\n- more than 3 parameters\n- multiple booleans\n- optional callback plus optional overrides plus optional config\n- passing values already available on an object\n\nPrefer:\n- one required object when the fields belong together\n- one discriminated union when there are modes\n- separate functions when the behaviours are actually different\n\n### Prefer discriminated unions over booleans\n\nIf a boolean changes behaviour, model the behaviour directly.\n\nUse:\n- `kind: \"draft\" | \"published\"`\n- `source: \"cache\" | \"network\"`\n- `status: \"idle\" | \"loading\" | \"success\" | \"error\"`\n\nAvoid:\n- `isDraft`\n- `useCache`\n- `isLoading` plus `error` plus `data` on the same object unless the state machine truly permits all combinations\n\n### Prefer assertions over defensive code\n\nAt boundaries, assert once. Inside, trust the assertion.\n\nAvoid repetitive checks like:\n- `if (!user) return`\n- `if (!user.id) return`\n- `if (typeof user.id !== \"string\") return`\n\nwhen types and boundary validation already guarantee the shape.\n\n### Prefer one obvious path\n\nIf there is a default behaviour, encode it directly.\n\nDo not add overrides like `sortOrder = \"desc\"`, `strategy = \"auto\"`, `separator = \",\"`, `shouldLog = false` unless callers truly need them.\n\nEvery option multiplies states.\n\n## Review prompts\n\nUse these prompts during the pass:\n\n- Can this function lose a parameter?\n- Can this object lose an optional field?\n- Can this branch become an early return?\n- Can these two booleans become one union?\n- Can this helper be inlined?\n- Can this error path become an assertion at the boundary?\n- Can this code fail loudly instead of guessing?\n- Can this diff lose files or lines?\n- If a reviewer skims this in 30 seconds, will the intent be obvious?\n\n## Examples\n\n### Reduce arguments and remove overrides\n\nBefore:\n\n```ts\nfunction createReport(\n  userId: string,\n  includeDrafts = false,\n  sortBy: \"date\" | \"name\" = \"date\",\n  sortDirection: \"asc\" | \"desc\" = \"desc\",\n  limit?: number,\n  overrides?: { timezone?: string; now?: Date }\n) {\n  const now = overrides?.now ?? new Date()\n  const timezone = overrides?.timezone ?? \"UTC\"\n\n  return buildReport({\n    userId,\n    includeDrafts,\n    sortBy,\n    sortDirection,\n    limit,\n    now,\n    timezone,\n  })\n}\n```\n\nAfter:\n\n```ts\ntype ReportScope =\n  | { kind: \"published\" }\n  | { kind: \"all\" }\n\nfunction createReport(userId: string, scope: ReportScope) {\n  return buildReport({ userId, scope, now: new Date(), timezone: \"UTC\" })\n}\n```\n\nPrefer a smaller API. Add configurability only when a real caller needs it.\n\n### Replace booleans with a discriminated union\n\nBefore:\n\n```ts\ntype SaveState = {\n  isSaving: boolean\n  error?: string\n  receipt?: string\n}\n```\n\nAfter:\n\n```ts\ntype SaveState =\n  | { kind: \"idle\" }\n  | { kind: \"saving\" }\n  | { kind: \"error\"; message: string }\n  | { kind: \"saved\"; receipt: string }\n```\n\nThe second version prevents impossible combinations.\n\n### Handle variants exhaustively\n\nBefore:\n\n```ts\nfunction badgeColor(status: Status) {\n  if (status === \"success\") return \"green\"\n  if (status === \"error\") return \"red\"\n  return \"gray\"\n}\n```\n\nAfter:\n\n```ts\nfunction badgeColor(status: Status) {\n  switch (status) {\n    case \"success\":\n      return \"green\"\n    case \"error\":\n      return \"red\"\n    case \"pending\":\n      return \"gray\"\n    default:\n      return assertNever(status)\n  }\n}\n```\n\nUnknown variants should fail loudly during development.\n\n### Assert at the boundary, trust inside\n\nBefore:\n\n```ts\nasync function loadAccount(accountId: string) {\n  const raw = await db.accounts.find(accountId)\n\n  if (!raw) {\n    throw new Error(\"Account not found\")\n  }\n\n  if (typeof raw.email !== \"string\") {\n    throw new Error(\"Invalid account email\")\n  }\n\n  return raw\n}\n\nfunction sendWelcomeEmail(account: any) {\n  if (!account) return\n  if (!account.email) return\n  mailer.send(account.email)\n}\n```\n\nAfter:\n\n```ts\nasync function loadAccount(accountId: string): Promise\u003CAccount> {\n  const raw = await db.accounts.find(accountId)\n  assert(raw, \"Account not found\")\n  assert(typeof raw.email === \"string\", \"Invalid account email\")\n  return raw as Account\n}\n\nfunction sendWelcomeEmail(account: Account) {\n  mailer.send(account.email)\n}\n```\n\nValidate once. Keep the typed core simple.\n\n### Prefer early returns over nesting\n\nBefore:\n\n```ts\nfunction visibleItems(items: Item[], user?: User) {\n  if (user) {\n    if (user.isAdmin) {\n      return items\n    } else {\n      return items.filter((item) => !item.hidden)\n    }\n  } else {\n    return []\n  }\n}\n```\n\nAfter:\n\n```ts\nfunction visibleItems(items: Item[], user?: User) {\n  if (!user) return []\n  if (user.isAdmin) return items\n  return items.filter((item) => !item.hidden)\n}\n```\n\nFlatten the shape of the code.\n\n### Do not split logic into too many tiny functions\n\nBefore:\n\n```ts\nfunction checkout(cart: Cart) {\n  validateCart(cart)\n  const subtotal = calculateSubtotal(cart)\n  const tax = calculateTax(subtotal)\n  const total = calculateTotal(subtotal, tax)\n  return finalizeCheckout(total)\n}\n\nfunction calculateTotal(subtotal: number, tax: number) {\n  return subtotal + tax\n}\n```\n\nAfter:\n\n```ts\nfunction checkout(cart: Cart) {\n  assert(cart.items.length > 0, \"Cart is empty\")\n\n  const subtotal = sum(cart.items.map((item) => item.price))\n  const tax = subtotal * TAX_RATE\n  const total = subtotal + tax\n\n  return finalizeCheckout(total)\n}\n```\n\nKeep trivial logic close to use.\n\n## PR gate\n\nBefore opening or updating the PR, verify:\n\n- The diff contains only necessary changes.\n- Public APIs are stricter or simpler, not more configurable.\n- Modes are modelled explicitly.\n- Variants are handled exhaustively.\n- Assertions exist at boundaries.\n- The core logic trusts types instead of re-checking everything.\n- Functions read top-to-bottom with minimal nesting.\n- Argument counts are low.\n- Helpers exist only when they clarify.\n- The final version is shorter, plainer, and easier to skim.\n\nIf a choice is between clever and obvious, choose obvious.\n\nIf a choice is between flexible and simple, choose simple.\n\nIf a choice is between adding code and deleting code, prefer deleting code.\n",{"name":5,"description":7},"main","351d6f0a5dac78be33208c688fdbb820b9053685",".claude\u002Fskills\u002Fskimmable",0,"https:\u002F\u002Fgithub.com\u002Fsurfingalien\u002FFinSurfing","https:\u002F\u002Fgithub.com\u002Fsurfingalien","2026-11-14 00:29:40",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add surfingalien\u002FFinSurfing --skill skimmable",{"tool":36,"command":37},"bunx","bunx skills add surfingalien\u002FFinSurfing --skill skimmable",{"tool":39,"command":40},"pnpm","pnpm dlx skills add surfingalien\u002FFinSurfing --skill skimmable","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsurfingalien\u002FFinSurfing\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fskimmable\u002FSKILL.md",true,[],[45,51,57,64,71,78],{"skillNo":46,"name":47,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M7490VYNX3NCT8R0PPSYHTXP","portfolio-management","https:\u002F\u002Fgithub.com\u002Fsurfingalien\u002FFinSurfing\u002Fblob\u002Fmain\u002Fskills\u002Fportfolio-management\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M7490SNSG32QP06X1P1EVK7N","financial-analysis","https:\u002F\u002Fgithub.com\u002Fsurfingalien\u002FFinSurfing\u002Fblob\u002Fmain\u002Fskills\u002Ffinancial-analysis\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M7490MKJ5QCVWWXC8HK57EVQ","tradingview-mcp","AI Trading Intelligence — live prices, 30+ technical indicators, backtesting (6 strategies), walk-forward overfitting detection, trade logs, equity curves, Reddit sentiment, news, and multi-market screener. Supports stocks, crypto, ETFs, indices, Turkish (BIST), and Egyptian (EGX) markets.","https:\u002F\u002Fgithub.com\u002Fsurfingalien\u002FFinSurfing\u002Fblob\u002Fmain\u002Fopenclaw\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M7490FHXRPVEPQMZ4KHFD161","sales-engineer","Analyzes RFP\u002FRFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win\u002Floss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.","https:\u002F\u002Fgithub.com\u002Fsurfingalien\u002FFinSurfing\u002Fblob\u002Fmain\u002Fbusiness-growth\u002Fskills\u002Fsales-engineer\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M7490C91D8F7CM7AXFZK8SQE","revenue-operations","Analyzes sales pipeline health, revenue forecasting accuracy, and go-to-market efficiency metrics for SaaS revenue optimization. Use when analyzing sales pipeline coverage, forecasting revenue, evaluating go-to-market performance, reviewing sales metrics, assessing pipeline analysis, tracking forecast accuracy with MAPE, calculating GTM efficiency, or measuring sales efficiency and unit economics for SaaS teams.","https:\u002F\u002Fgithub.com\u002Fsurfingalien\u002FFinSurfing\u002Fblob\u002Fmain\u002Fbusiness-growth\u002Fskills\u002Frevenue-operations\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M74907FEV2YRKSYPNG649HGF","customer-success-manager","Monitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success. Use when analyzing customer accounts, reviewing retention metrics, scoring at-risk customers, or when the user mentions churn, customer health scores, upsell opportunities, expansion revenue, retention analysis, or customer analytics. Runs three Python CLI tools to produce deterministic health scores, churn risk tiers, and prioritized expansion recommendations across Enterprise, Mid-Market, and SMB segments.","https:\u002F\u002Fgithub.com\u002Fsurfingalien\u002FFinSurfing\u002Fblob\u002Fmain\u002Fbusiness-growth\u002Fskills\u002Fcustomer-success-manager\u002FSKILL.md",[],[]]