[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M748VS0XSDATSPVP8CESYZ1W":3,"skill-same:01M748VS0XSDATSPVP8CESYZ1W":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},"01M748VS0XSDATSPVP8CESYZ1W","writing-plans",null,"Write structured implementation plans from specs or requirements before touching code. Use when given a spec, requirements doc, or feature description, when user says \"plan this out\", \"write a plan for\", \"how should we implement\", or before starting any multi-step coding task.","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\u002Fwriting-plans\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: writing-plans\ndescription: Write structured implementation plans from specs or requirements before touching code. Use when given a spec, requirements doc, or feature description, when user says \"plan this out\", \"write a plan for\", \"how should we implement\", or before starting any multi-step coding task.\n---\n\n# Writing Plans\n\n## Overview\n\nWrite comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.\n\nAssume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.\n\n**Announce at start:** \"I'm using the writing-plans skill to create the implementation plan.\"\n\n**Context:** This should be run in a dedicated worktree (created by brainstorming skill).\n\n**Save plans to:** `docs\u002Fplans\u002FYYYY-MM-DD-\u003Cfeature-name>.md`\n\n## Bite-Sized Task Granularity\n\n**Each step is one action (2-5 minutes):**\n- \"Write the failing test\" - step\n- \"Run it to make sure it fails\" - step\n- \"Implement the minimal code to make the test pass\" - step\n- \"Run the tests and make sure they pass\" - step\n- \"Commit\" - step\n\n## Plan Document Header\n\n**Every plan MUST start with this header:**\n\n```markdown\n# [Feature Name] Implementation Plan\n\n> **For Claude:** REQUIRED SUB-SKILL: Use the executing-plans skill to implement this plan task-by-task.\n\n**Goal:** [One sentence describing what this builds]\n\n**Architecture:** [2-3 sentences about approach]\n\n**Tech Stack:** [Key technologies\u002Flibraries]\n\n---\n```\n\n## Task Structure\n\n````markdown\n### Task N: [Component Name]\n\n**Files:**\n- Create: `exact\u002Fpath\u002Fto\u002Ffile.py`\n- Modify: `exact\u002Fpath\u002Fto\u002Fexisting.py:123-145`\n- Test: `tests\u002Fexact\u002Fpath\u002Fto\u002Ftest.py`\n\n**Step 1: Write the failing test**\n\n```python\ndef test_specific_behavior():\n    result = function(input)\n    assert result == expected\n```\n\n**Step 2: Run test to verify it fails**\n\nRun: `pytest tests\u002Fpath\u002Ftest.py::test_name -v`\nExpected: FAIL with \"function not defined\"\n\n**Step 3: Write minimal implementation**\n\n```python\ndef function(input):\n    return expected\n```\n\n**Step 4: Run test to verify it passes**\n\nRun: `pytest tests\u002Fpath\u002Ftest.py::test_name -v`\nExpected: PASS\n\n**Step 5: Commit**\n\n```bash\ngit add tests\u002Fpath\u002Ftest.py src\u002Fpath\u002Ffile.py\ngit commit -m \"feat: add specific feature\"\n```\n````\n\n## Remember\n- Exact file paths always\n- Complete code in plan (not \"add validation\")\n- Exact commands with expected output\n- Reference relevant skills with @ syntax\n- DRY, YAGNI, TDD, frequent commits\n\n## Common Pitfalls\n\n### 1. Plans Too Abstract (No Concrete Paths or Commands)\n\n**Symptom:** Plan reads smoothly but lacks actionable details. Steps like \"Add validation\" or \"Update the API handler\" leave the engineer guessing which file, which function, or what commands to run.\n\n**Why it fails:**\n- Engineer wastes time hunting for the right file or inferring code structure\n- Different engineers interpret abstract steps differently, leading to rework\n- No way to verify the plan is complete until someone starts implementing\n\n**How to fix:**\n- Always include exact file paths: `src\u002Fhandlers\u002Fuser.ts` not `update the handler`\n- Always include exact commands: `pytest tests\u002Fhandlers\u002Ftest_user.py -v` not `run tests`\n- Always include complete code in fenced blocks, not pseudocode\n- Provide line numbers when modifying existing files: `Modify: src\u002Fhandlers\u002Fuser.ts:45-62`\n\n**Example (bad vs good):**\n```\n❌ BAD: \"Update the validation logic to handle email addresses\"\n✅ GOOD: \"Modify: src\u002Fvalidators\u002Femail.py:12-18. Replace the regex pattern with: re.compile(r'^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\\.[a-zA-Z]{2,}$')\"\n```\n\n---\n\n### 2. Task Granularity Wrong (Steps Too Large or Too Small)\n\n**Symptom:** Steps are either vague epics (\"Build the authentication system\") or so granular they create friction (\"Import the module\", \"Define the function signature\", \"Write the function body\").\n\n**Why it fails:**\n- Large steps: engineer lacks guardrails; easy to implement wrong thing\n- Small steps: excessive context switching; commits become noise; hard to trace intent\n- Either way, progress becomes hard to measure and verify\n\n**How to fix:**\n- Target 2-5 minute steps: small enough to verify and commit independently, large enough to be meaningful\n- Group related micro-steps under a single task heading, then break them into numbered steps\n- Each step should produce a git-committable change\n- Use this litmus test: \"Can I understand and verify this single commit in isolation?\"\n\n**Example (bad vs good):**\n```\n❌ BAD:\n  Step 1: Import json\n  Step 2: Define function\n  Step 3: Write body\n  Step 4: Run test\n\n✅ GOOD:\n  Step 1: Write failing test for json parsing\n  Step 2: Implement minimal function that passes test\n  Step 3: Run test and verify PASS\n  Step 4: Commit\n```\n\n---\n\n### 3. Missing Verification Steps (No Way to Confirm Task Success)\n\n**Symptom:** Plan describes what to do but never says how to verify it's done correctly. Engineer finishes a step and isn't sure if it actually worked.\n\n**Why it fails:**\n- Silent failures: code runs but produces wrong result; engineer doesn't catch it\n- Wasted debugging time: engineer has to invent their own verification method\n- Plan can't be reused reliably because success criteria are ambiguous\n\n**How to fix:**\n- Every step that changes behavior must include a verification command\n- Verification command must include expected output or success indicator\n- For tests: `Expected: PASS`. For commands: `Expected output: [actual output]`\n- Include negative cases: \"Run: `pytest tests\u002F... -v`. Expected: Should fail with 'ValidationError'\"\n\n**Example (bad vs good):**\n`````\n❌ BAD:\n  Step 3: Implement the validation function\n\n✅ GOOD:\n  Step 3: Implement the validation function\n  \n  ```python\n  def validate_email(email):\n      pattern = r'^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\\.[a-zA-Z]{2,}$'\n      return bool(re.match(pattern, email))\n  ```\n\n  Step 4: Run test to verify it passes\n  \n  Run: `pytest tests\u002Fvalidators\u002Ftest_email.py::test_valid_email -v`\n  Expected: `PASSED test_valid_email`\n`````\n\n---\n\n### 4. DRY Violations (Repeated Instructions Across Tasks)\n\n**Symptom:** Plan repeats the same instruction in multiple tasks (\"Run the full test suite\", \"Import X module\", \"Follow the naming convention\"). Same boilerplate appears in steps across different tasks.\n\n**Why it fails:**\n- Maintainability: updating the pattern requires editing multiple places\n- Cognitive load: engineer has to understand the intent is the same across tasks\n- Error-prone: same instruction might be subtly different in different places, causing confusion\n\n**How to fix:**\n- Capture repeated patterns in a \"Setup\" or \"Prerequisites\" section at the top of the plan\n- Use consistent command syntax and structure across similar steps\n- Link to shared instructions: \"As per 'Testing' section above, run: `pytest ...`\"\n- If a pattern is truly repeated, ask: can these tasks be combined or is there a shared utility that would eliminate the duplication?\n\n**Example (bad vs good):**\n```\n❌ BAD:\n  Task 1: Write test, run `pytest tests\u002Fhandlers\u002Ftest_a.py -v`, commit\n  Task 2: Write test, run `pytest tests\u002Fhandlers\u002Ftest_b.py -v`, commit\n  Task 3: Write test, run `pytest tests\u002Fhandlers\u002Ftest_c.py -v`, commit\n\n✅ GOOD:\n  # Testing Pattern\n  After each implementation, verify with: `pytest tests\u002Fhandlers\u002Ftest_\u003Cname>.py -v`\n  Expected: All tests PASS\n  \n  Task 1: [test_a implementation]\n  Task 2: [test_b implementation]\n  Task 3: [test_c implementation]\n```\n\n---\n\n### 5. Assumes Context Agent Won't Have (Framework Specifics, Conventions)\n\n**Symptom:** Plan references \"the standard pattern\", \"as we do it\", or \"use the company convention\" without explaining what that actually means. Assumes engineer knows framework shortcuts, naming conventions, or project structure.\n\n**Why it fails:**\n- Fresh engineer or external contributor has no reference for \"the pattern\"\n- Different projects have different conventions; agent may mix them up\n- Engineer spends time reverse-engineering conventions instead of following a plan\n\n**How to fix:**\n- Explicitly state conventions in a \"Context\" or \"Setup\" section at the plan start\n- Name the convention if it's framework-specific: \"Django model naming: `class MyModel(models.Model)`\"\n- Provide an example: \"All API handlers follow this pattern: [example file + code snippet]\"\n- If a pattern is specific to this codebase, explain it briefly instead of assuming knowledge\n\n**Example (bad vs good):**\n`````\n❌ BAD:\n  Step 1: Create a handler using the standard pattern\n  Step 2: Follow our naming convention for tests\n\n✅ GOOD:\n  Context: This project uses Flask. All handlers live in src\u002Fhandlers\u002F and follow the pattern:\n  ```python\n  @app.route('\u002Fendpoint', methods=['POST'])\n  def handle_endpoint():\n      # Handler logic\n      return jsonify({...})\n  ```\n  \n  Step 1: Create handler in src\u002Fhandlers\u002Fmy_handler.py following the pattern above\n  Step 2: Create test in tests\u002Fhandlers\u002Ftest_my_handler.py. Naming: test_\u003Cfunction_name>_\u003Cscenario>\n`````\n\n---\n\n## Execution Handoff\n\nAfter saving the plan, offer execution choice:\n\n**\"Plan complete and saved to `docs\u002Fplans\u002F\u003Cfilename>.md`. Two execution options:**\n\n**1. Subagent-Driven (this session)** - I dispatch fresh subagent per task, review between tasks, fast iteration\n\n**2. Parallel Session (separate)** - Open new session with executing-plans, batch execution with checkpoints\n\n**Which approach?\"**\n\n**If Subagent-Driven chosen:**\n- Spawn a subagent per task, review results between tasks, fast iteration\n- Stay in this session and orchestrate\n\n**If Parallel Session chosen:**\n- Guide them to open new session in the git worktree\n- **REQUIRED SUB-SKILL:** New session uses the executing-plans skill\n","# Writing Plans\n\n## Overview\n\nWrite comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.\n\nAssume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.\n\n**Announce at start:** \"I'm using the writing-plans skill to create the implementation plan.\"\n\n**Context:** This should be run in a dedicated worktree (created by brainstorming skill).\n\n**Save plans to:** `docs\u002Fplans\u002FYYYY-MM-DD-\u003Cfeature-name>.md`\n\n## Bite-Sized Task Granularity\n\n**Each step is one action (2-5 minutes):**\n- \"Write the failing test\" - step\n- \"Run it to make sure it fails\" - step\n- \"Implement the minimal code to make the test pass\" - step\n- \"Run the tests and make sure they pass\" - step\n- \"Commit\" - step\n\n## Plan Document Header\n\n**Every plan MUST start with this header:**\n\n```markdown\n# [Feature Name] Implementation Plan\n\n> **For Claude:** REQUIRED SUB-SKILL: Use the executing-plans skill to implement this plan task-by-task.\n\n**Goal:** [One sentence describing what this builds]\n\n**Architecture:** [2-3 sentences about approach]\n\n**Tech Stack:** [Key technologies\u002Flibraries]\n\n---\n```\n\n## Task Structure\n\n````markdown\n### Task N: [Component Name]\n\n**Files:**\n- Create: `exact\u002Fpath\u002Fto\u002Ffile.py`\n- Modify: `exact\u002Fpath\u002Fto\u002Fexisting.py:123-145`\n- Test: `tests\u002Fexact\u002Fpath\u002Fto\u002Ftest.py`\n\n**Step 1: Write the failing test**\n\n```python\ndef test_specific_behavior():\n    result = function(input)\n    assert result == expected\n```\n\n**Step 2: Run test to verify it fails**\n\nRun: `pytest tests\u002Fpath\u002Ftest.py::test_name -v`\nExpected: FAIL with \"function not defined\"\n\n**Step 3: Write minimal implementation**\n\n```python\ndef function(input):\n    return expected\n```\n\n**Step 4: Run test to verify it passes**\n\nRun: `pytest tests\u002Fpath\u002Ftest.py::test_name -v`\nExpected: PASS\n\n**Step 5: Commit**\n\n```bash\ngit add tests\u002Fpath\u002Ftest.py src\u002Fpath\u002Ffile.py\ngit commit -m \"feat: add specific feature\"\n```\n````\n\n## Remember\n- Exact file paths always\n- Complete code in plan (not \"add validation\")\n- Exact commands with expected output\n- Reference relevant skills with @ syntax\n- DRY, YAGNI, TDD, frequent commits\n\n## Common Pitfalls\n\n### 1. Plans Too Abstract (No Concrete Paths or Commands)\n\n**Symptom:** Plan reads smoothly but lacks actionable details. Steps like \"Add validation\" or \"Update the API handler\" leave the engineer guessing which file, which function, or what commands to run.\n\n**Why it fails:**\n- Engineer wastes time hunting for the right file or inferring code structure\n- Different engineers interpret abstract steps differently, leading to rework\n- No way to verify the plan is complete until someone starts implementing\n\n**How to fix:**\n- Always include exact file paths: `src\u002Fhandlers\u002Fuser.ts` not `update the handler`\n- Always include exact commands: `pytest tests\u002Fhandlers\u002Ftest_user.py -v` not `run tests`\n- Always include complete code in fenced blocks, not pseudocode\n- Provide line numbers when modifying existing files: `Modify: src\u002Fhandlers\u002Fuser.ts:45-62`\n\n**Example (bad vs good):**\n```\n❌ BAD: \"Update the validation logic to handle email addresses\"\n✅ GOOD: \"Modify: src\u002Fvalidators\u002Femail.py:12-18. Replace the regex pattern with: re.compile(r'^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\\.[a-zA-Z]{2,}$')\"\n```\n\n---\n\n### 2. Task Granularity Wrong (Steps Too Large or Too Small)\n\n**Symptom:** Steps are either vague epics (\"Build the authentication system\") or so granular they create friction (\"Import the module\", \"Define the function signature\", \"Write the function body\").\n\n**Why it fails:**\n- Large steps: engineer lacks guardrails; easy to implement wrong thing\n- Small steps: excessive context switching; commits become noise; hard to trace intent\n- Either way, progress becomes hard to measure and verify\n\n**How to fix:**\n- Target 2-5 minute steps: small enough to verify and commit independently, large enough to be meaningful\n- Group related micro-steps under a single task heading, then break them into numbered steps\n- Each step should produce a git-committable change\n- Use this litmus test: \"Can I understand and verify this single commit in isolation?\"\n\n**Example (bad vs good):**\n```\n❌ BAD:\n  Step 1: Import json\n  Step 2: Define function\n  Step 3: Write body\n  Step 4: Run test\n\n✅ GOOD:\n  Step 1: Write failing test for json parsing\n  Step 2: Implement minimal function that passes test\n  Step 3: Run test and verify PASS\n  Step 4: Commit\n```\n\n---\n\n### 3. Missing Verification Steps (No Way to Confirm Task Success)\n\n**Symptom:** Plan describes what to do but never says how to verify it's done correctly. Engineer finishes a step and isn't sure if it actually worked.\n\n**Why it fails:**\n- Silent failures: code runs but produces wrong result; engineer doesn't catch it\n- Wasted debugging time: engineer has to invent their own verification method\n- Plan can't be reused reliably because success criteria are ambiguous\n\n**How to fix:**\n- Every step that changes behavior must include a verification command\n- Verification command must include expected output or success indicator\n- For tests: `Expected: PASS`. For commands: `Expected output: [actual output]`\n- Include negative cases: \"Run: `pytest tests\u002F... -v`. Expected: Should fail with 'ValidationError'\"\n\n**Example (bad vs good):**\n`````\n❌ BAD:\n  Step 3: Implement the validation function\n\n✅ GOOD:\n  Step 3: Implement the validation function\n  \n  ```python\n  def validate_email(email):\n      pattern = r'^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\\.[a-zA-Z]{2,}$'\n      return bool(re.match(pattern, email))\n  ```\n\n  Step 4: Run test to verify it passes\n  \n  Run: `pytest tests\u002Fvalidators\u002Ftest_email.py::test_valid_email -v`\n  Expected: `PASSED test_valid_email`\n`````\n\n---\n\n### 4. DRY Violations (Repeated Instructions Across Tasks)\n\n**Symptom:** Plan repeats the same instruction in multiple tasks (\"Run the full test suite\", \"Import X module\", \"Follow the naming convention\"). Same boilerplate appears in steps across different tasks.\n\n**Why it fails:**\n- Maintainability: updating the pattern requires editing multiple places\n- Cognitive load: engineer has to understand the intent is the same across tasks\n- Error-prone: same instruction might be subtly different in different places, causing confusion\n\n**How to fix:**\n- Capture repeated patterns in a \"Setup\" or \"Prerequisites\" section at the top of the plan\n- Use consistent command syntax and structure across similar steps\n- Link to shared instructions: \"As per 'Testing' section above, run: `pytest ...`\"\n- If a pattern is truly repeated, ask: can these tasks be combined or is there a shared utility that would eliminate the duplication?\n\n**Example (bad vs good):**\n```\n❌ BAD:\n  Task 1: Write test, run `pytest tests\u002Fhandlers\u002Ftest_a.py -v`, commit\n  Task 2: Write test, run `pytest tests\u002Fhandlers\u002Ftest_b.py -v`, commit\n  Task 3: Write test, run `pytest tests\u002Fhandlers\u002Ftest_c.py -v`, commit\n\n✅ GOOD:\n  # Testing Pattern\n  After each implementation, verify with: `pytest tests\u002Fhandlers\u002Ftest_\u003Cname>.py -v`\n  Expected: All tests PASS\n  \n  Task 1: [test_a implementation]\n  Task 2: [test_b implementation]\n  Task 3: [test_c implementation]\n```\n\n---\n\n### 5. Assumes Context Agent Won't Have (Framework Specifics, Conventions)\n\n**Symptom:** Plan references \"the standard pattern\", \"as we do it\", or \"use the company convention\" without explaining what that actually means. Assumes engineer knows framework shortcuts, naming conventions, or project structure.\n\n**Why it fails:**\n- Fresh engineer or external contributor has no reference for \"the pattern\"\n- Different projects have different conventions; agent may mix them up\n- Engineer spends time reverse-engineering conventions instead of following a plan\n\n**How to fix:**\n- Explicitly state conventions in a \"Context\" or \"Setup\" section at the plan start\n- Name the convention if it's framework-specific: \"Django model naming: `class MyModel(models.Model)`\"\n- Provide an example: \"All API handlers follow this pattern: [example file + code snippet]\"\n- If a pattern is specific to this codebase, explain it briefly instead of assuming knowledge\n\n**Example (bad vs good):**\n`````\n❌ BAD:\n  Step 1: Create a handler using the standard pattern\n  Step 2: Follow our naming convention for tests\n\n✅ GOOD:\n  Context: This project uses Flask. All handlers live in src\u002Fhandlers\u002F and follow the pattern:\n  ```python\n  @app.route('\u002Fendpoint', methods=['POST'])\n  def handle_endpoint():\n      # Handler logic\n      return jsonify({...})\n  ```\n  \n  Step 1: Create handler in src\u002Fhandlers\u002Fmy_handler.py following the pattern above\n  Step 2: Create test in tests\u002Fhandlers\u002Ftest_my_handler.py. Naming: test_\u003Cfunction_name>_\u003Cscenario>\n`````\n\n---\n\n## Execution Handoff\n\nAfter saving the plan, offer execution choice:\n\n**\"Plan complete and saved to `docs\u002Fplans\u002F\u003Cfilename>.md`. Two execution options:**\n\n**1. Subagent-Driven (this session)** - I dispatch fresh subagent per task, review between tasks, fast iteration\n\n**2. Parallel Session (separate)** - Open new session with executing-plans, batch execution with checkpoints\n\n**Which approach?\"**\n\n**If Subagent-Driven chosen:**\n- Spawn a subagent per task, review results between tasks, fast iteration\n- Stay in this session and orchestrate\n\n**If Parallel Session chosen:**\n- Guide them to open new session in the git worktree\n- **REQUIRED SUB-SKILL:** New session uses the executing-plans skill\n",{"name":5,"description":7},"main","351d6f0a5dac78be33208c688fdbb820b9053685",".claude\u002Fskills\u002Fwriting-plans",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 writing-plans",{"tool":36,"command":37},"bunx","bunx skills add surfingalien\u002FFinSurfing --skill writing-plans",{"tool":39,"command":40},"pnpm","pnpm dlx skills add surfingalien\u002FFinSurfing --skill writing-plans","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsurfingalien\u002FFinSurfing\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwriting-plans\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",[],[]]