[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NTH7ZV5C4MJDGMFN4V29BX":3,"skill-same:01M6NTH7ZV5C4MJDGMFN4V29BX":53},{"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":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":14,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M6NTH7ZV5C4MJDGMFN4V29BX","create_handoff",null,"Create handoff document for transferring work to another session","rubicanjr\u002FFinCognis","rubicanjr","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F234912519?v=4","01M6NT156NND8J474G34SB3923","Rubi","01M6NT15B70RWXE1N3YV0BZY8A",0,"MIT","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fcreate_handoff\u002FSKILL.md",[],[19,20,21,22,23,24,25],"handoff","create","create handoff","work","session","document","for","2026-11-10 10:12:30",false,"---\ndescription: Create handoff document for transferring work to another session\n---\n\n# Create Handoff\n\nYou are tasked with writing a handoff document to hand off your work to another agent in a new session. You will create a handoff document that is thorough, but also **concise**. The goal is to compact and summarize your context without losing any of the key details of what you're working on.\n\n\n## Process\n### 1. Filepath & Metadata\nUse the following information to understand how to create your document:\n\n**First, determine the session name from existing handoffs:**\n```bash\nls -td thoughts\u002Fshared\u002Fhandoffs\u002F*\u002F 2>\u002Fdev\u002Fnull | head -1 | xargs basename\n```\n\nThis returns the most recently modified handoff folder name (e.g., `open-source-release`). Use this as the handoff folder name.\n\nIf no handoffs exist, use `general` as the folder name.\n\n**Create your file under:** `thoughts\u002Fshared\u002Fhandoffs\u002F{session-name}\u002FYYYY-MM-DD_HH-MM_description.yaml`, where:\n- `{session-name}` is from existing handoffs (e.g., `open-source-release`) or `general` if none exist\n- `YYYY-MM-DD` is today's date\n- `HH-MM` is the current time in 24-hour format (no seconds needed)\n- `description` is a brief kebab-case description\n\n**Examples:**\n- `thoughts\u002Fshared\u002Fhandoffs\u002Fopen-source-release\u002F2026-01-08_16-30_memory-system-fix.yaml`\n- `thoughts\u002Fshared\u002Fhandoffs\u002Fgeneral\u002F2026-01-08_16-30_bug-investigation.yaml`\n\n### 2. Write YAML handoff (~400 tokens vs ~2000 for markdown)\n\n**CRITICAL: Use EXACTLY this YAML format. Do NOT deviate or use alternative field names.**\n\nThe `goal:` and `now:` fields are shown in the statusline - they MUST be named exactly this.\n\n```yaml\n---\nsession: {session-name from ledger}\ndate: YYYY-MM-DD\nstatus: complete|partial|blocked\noutcome: SUCCEEDED|PARTIAL_PLUS|PARTIAL_MINUS|FAILED\n---\n\ngoal: {What this session accomplished - shown in statusline}\nnow: {What next session should do first - shown in statusline}\ntest: {Command to verify this work, e.g., pytest tests\u002Ftest_foo.py}\n\ndone_this_session:\n  - task: {First completed task}\n    files: [{file1.py}, {file2.py}]\n  - task: {Second completed task}\n    files: [{file3.py}]\n\nblockers: [{any blocking issues}]\n\nquestions: [{unresolved questions for next session}]\n\ndecisions:\n  - {decision_name}: {rationale}\n\nfindings:\n  - {key_finding}: {details}\n\nworked: [{approaches that worked}]\nfailed: [{approaches that failed and why}]\n\nnext:\n  - {First next step}\n  - {Second next step}\n\nfiles:\n  created: [{new files}]\n  modified: [{changed files}]\n```\n\n**Field guide:**\n- `goal:` + `now:` - REQUIRED, shown in statusline\n- `done_this_session:` - What was accomplished with file references\n- `decisions:` - Important choices and rationale\n- `findings:` - Key learnings\n- `worked:` \u002F `failed:` - What to repeat vs avoid\n- `next:` - Action items for next session\n\n**DO NOT use alternative field names like `session_goal`, `objective`, `focus`, `current`, etc.**\n**The statusline parser looks for EXACTLY `goal:` and `now:` - nothing else works.**\n---\n\n### 3. Mark Session Outcome (REQUIRED)\n\n**IMPORTANT:** Before responding to the user, you MUST ask about the session outcome.\n\nUse the AskUserQuestion tool with these exact options:\n\n```\nQuestion: \"How did this session go?\"\nOptions:\n  - SUCCEEDED: Task completed successfully\n  - PARTIAL_PLUS: Mostly done, minor issues remain\n  - PARTIAL_MINUS: Some progress, major issues remain\n  - FAILED: Task abandoned or blocked\n```\n\nAfter the user responds, mark the outcome:\n```bash\n# Mark the most recent handoff (works with PostgreSQL or SQLite)\n# Use git root to find project, then opc\u002Fscripts\u002Fcore\u002F\nPROJECT_ROOT=$(git rev-parse --show-toplevel 2>\u002Fdev\u002Fnull || echo \"${CLAUDE_PROJECT_DIR:-.}\")\ncd \"$PROJECT_ROOT\u002Fopc\" && uv run python scripts\u002Fcore\u002Fartifact_mark.py --latest --outcome \u003CUSER_CHOICE>\n```\n\nThis command auto-detects the database (PostgreSQL if configured, SQLite fallback).\n\n### 4. Confirm completion\n\nAfter marking the outcome, respond to the user:\n\n```\nHandoff created! Outcome marked as [OUTCOME].\n\nResume in a new session with:\n\u002Fresume_handoff path\u002Fto\u002Fhandoff.yaml\n```\n\n---\n##.  Additional Notes & Instructions\n- **more information, not less**. This is a guideline that defines the minimum of what a handoff should be. Always feel free to include more information if necessary.\n- **be thorough and precise**. include both top-level objectives, and lower-level details as necessary.\n- **avoid excessive code snippets**. While a brief snippet to describe some key change is important, avoid large code blocks or diffs; do not include one unless it's necessary (e.g. pertains to an error you're debugging). Prefer using `\u002Fpath\u002Fto\u002Ffile.ext:line` references that an agent can follow later when it's ready, e.g. `packages\u002Fdashboard\u002Fsrc\u002Fapp\u002Fdashboard\u002Fpage.tsx:12-24`\n","# Create Handoff\n\nYou are tasked with writing a handoff document to hand off your work to another agent in a new session. You will create a handoff document that is thorough, but also **concise**. The goal is to compact and summarize your context without losing any of the key details of what you're working on.\n\n\n## Process\n### 1. Filepath & Metadata\nUse the following information to understand how to create your document:\n\n**First, determine the session name from existing handoffs:**\n```bash\nls -td thoughts\u002Fshared\u002Fhandoffs\u002F*\u002F 2>\u002Fdev\u002Fnull | head -1 | xargs basename\n```\n\nThis returns the most recently modified handoff folder name (e.g., `open-source-release`). Use this as the handoff folder name.\n\nIf no handoffs exist, use `general` as the folder name.\n\n**Create your file under:** `thoughts\u002Fshared\u002Fhandoffs\u002F{session-name}\u002FYYYY-MM-DD_HH-MM_description.yaml`, where:\n- `{session-name}` is from existing handoffs (e.g., `open-source-release`) or `general` if none exist\n- `YYYY-MM-DD` is today's date\n- `HH-MM` is the current time in 24-hour format (no seconds needed)\n- `description` is a brief kebab-case description\n\n**Examples:**\n- `thoughts\u002Fshared\u002Fhandoffs\u002Fopen-source-release\u002F2026-01-08_16-30_memory-system-fix.yaml`\n- `thoughts\u002Fshared\u002Fhandoffs\u002Fgeneral\u002F2026-01-08_16-30_bug-investigation.yaml`\n\n### 2. Write YAML handoff (~400 tokens vs ~2000 for markdown)\n\n**CRITICAL: Use EXACTLY this YAML format. Do NOT deviate or use alternative field names.**\n\nThe `goal:` and `now:` fields are shown in the statusline - they MUST be named exactly this.\n\n```yaml\n---\nsession: {session-name from ledger}\ndate: YYYY-MM-DD\nstatus: complete|partial|blocked\noutcome: SUCCEEDED|PARTIAL_PLUS|PARTIAL_MINUS|FAILED\n---\n\ngoal: {What this session accomplished - shown in statusline}\nnow: {What next session should do first - shown in statusline}\ntest: {Command to verify this work, e.g., pytest tests\u002Ftest_foo.py}\n\ndone_this_session:\n  - task: {First completed task}\n    files: [{file1.py}, {file2.py}]\n  - task: {Second completed task}\n    files: [{file3.py}]\n\nblockers: [{any blocking issues}]\n\nquestions: [{unresolved questions for next session}]\n\ndecisions:\n  - {decision_name}: {rationale}\n\nfindings:\n  - {key_finding}: {details}\n\nworked: [{approaches that worked}]\nfailed: [{approaches that failed and why}]\n\nnext:\n  - {First next step}\n  - {Second next step}\n\nfiles:\n  created: [{new files}]\n  modified: [{changed files}]\n```\n\n**Field guide:**\n- `goal:` + `now:` - REQUIRED, shown in statusline\n- `done_this_session:` - What was accomplished with file references\n- `decisions:` - Important choices and rationale\n- `findings:` - Key learnings\n- `worked:` \u002F `failed:` - What to repeat vs avoid\n- `next:` - Action items for next session\n\n**DO NOT use alternative field names like `session_goal`, `objective`, `focus`, `current`, etc.**\n**The statusline parser looks for EXACTLY `goal:` and `now:` - nothing else works.**\n---\n\n### 3. Mark Session Outcome (REQUIRED)\n\n**IMPORTANT:** Before responding to the user, you MUST ask about the session outcome.\n\nUse the AskUserQuestion tool with these exact options:\n\n```\nQuestion: \"How did this session go?\"\nOptions:\n  - SUCCEEDED: Task completed successfully\n  - PARTIAL_PLUS: Mostly done, minor issues remain\n  - PARTIAL_MINUS: Some progress, major issues remain\n  - FAILED: Task abandoned or blocked\n```\n\nAfter the user responds, mark the outcome:\n```bash\n# Mark the most recent handoff (works with PostgreSQL or SQLite)\n# Use git root to find project, then opc\u002Fscripts\u002Fcore\u002F\nPROJECT_ROOT=$(git rev-parse --show-toplevel 2>\u002Fdev\u002Fnull || echo \"${CLAUDE_PROJECT_DIR:-.}\")\ncd \"$PROJECT_ROOT\u002Fopc\" && uv run python scripts\u002Fcore\u002Fartifact_mark.py --latest --outcome \u003CUSER_CHOICE>\n```\n\nThis command auto-detects the database (PostgreSQL if configured, SQLite fallback).\n\n### 4. Confirm completion\n\nAfter marking the outcome, respond to the user:\n\n```\nHandoff created! Outcome marked as [OUTCOME].\n\nResume in a new session with:\n\u002Fresume_handoff path\u002Fto\u002Fhandoff.yaml\n```\n\n---\n##.  Additional Notes & Instructions\n- **more information, not less**. This is a guideline that defines the minimum of what a handoff should be. Always feel free to include more information if necessary.\n- **be thorough and precise**. include both top-level objectives, and lower-level details as necessary.\n- **avoid excessive code snippets**. While a brief snippet to describe some key change is important, avoid large code blocks or diffs; do not include one unless it's necessary (e.g. pertains to an error you're debugging). Prefer using `\u002Fpath\u002Fto\u002Ffile.ext:line` references that an agent can follow later when it's ready, e.g. `packages\u002Fdashboard\u002Fsrc\u002Fapp\u002Fdashboard\u002Fpage.tsx:12-24`\n",{"description":7},"main","70e1c350500ee750987420bbae48837afa906b7e","skills\u002Fcreate_handoff","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis","https:\u002F\u002Fgithub.com\u002Frubicanjr","linktr.ee\u002Ffinanskodu","Industrial Engineer & CIO @FinansKodu. Architecting AI-driven financial agents and autonomous workflows. 🏗️ Building systems, not just prompts.","2026-06-09 13:50:15",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add rubicanjr\u002FFinCognis --skill create_handoff",{"tool":45,"command":46},"bunx","bunx skills add rubicanjr\u002FFinCognis --skill create_handoff",{"tool":48,"command":49},"pnpm","pnpm dlx skills add rubicanjr\u002FFinCognis --skill create_handoff","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fcreate_handoff\u002FSKILL.md",true,[],[54,75,84,104,133,152],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":65,"publishedAt":26},"01M6NWS9DAXJTADT4T5MB49X8W","workflow-router","Goal-based workflow orchestration - routes tasks to specialist agents based on user goals","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-router\u002FSKILL.md",[60],{"categoryNo":61,"categoryName":62,"taxonomyType":63,"taxonomyTypeDesc":64},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[66,67,68,69,70,71,72,73,74],"workflow router","workflow","router","orchestration","goals","goal","user","workflow orchestration","tasks",{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":26},"01M6NWS3RETSC0SHP16HP66E14","wiring","Wiring Verification","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fwiring\u002FSKILL.md",[],[77,82,83],"verification","false",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":93,"publishedAt":26},"01M6NWS0XW9CVQZBDA1EGW0TWC","websocket-patterns","Connection management, room patterns, reconnection strategies, message buffering, and binary protocol design.","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fwebsocket-patterns\u002Fskill.md",[90],{"categoryNo":91,"categoryName":92,"taxonomyType":63,"taxonomyTypeDesc":64},"01JBSEEDCAT000000000000015","视觉设计",[94,95,96,97,98,99,100,101,102,103],"websocket","patterns","websocket patterns","design","protocol","management","message","strategies","binary","connection",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":114,"publishedAt":26},"01M6NWRDQDX9ZNETAWRRMQWV52","visual-verdict","Screenshot comparison QA for frontend development. Takes a screenshot of the current implementation, scores it across multiple visual dimensions, and returns a structured PASS\u002FREVISE\u002FFAIL verdict with concrete fixes. Use when implementing UI from a design reference or verifying visual correctness.","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fvisual-verdict\u002FSKILL.md",[110,113],{"categoryNo":111,"categoryName":112,"taxonomyType":63,"taxonomyTypeDesc":64},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":61,"categoryName":62,"taxonomyType":63,"taxonomyTypeDesc":64},[115,116,117,118,119,120,121,122,123,25,124,125,126,97,127,128,129,130,131,132],"visual","verdict","visual verdict","ui","across","revise","comparison","correctness","implementing","fixes","dimensions","frontend","development","qa","screenshot","returns","use","frontend development",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":26},"01M6NWR8HSNRS7MNDK2J02QYMN","verification-loop","Comprehensive verification system covering build, types, lint, tests, security, and diff review before a PR.","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[140,141,82,142,143,144,145,146,147,148,149,150,151],"verification loop","loop","lint","review","security","pr","system","diff","build","tests","diff review","types",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":26},"01M6NWR4HHSFR0VR5EXFRWA747","vector-db-patterns","Embedding strategies, ANN algorithms, hybrid search, RAG chunking strategies, and reranking for semantic search and retrieval.","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fvector-db-patterns\u002Fskill.md",[],[159,160,161,162,95,163,164,165,166,101,167,168,169,170,171,25,172,173],"vector db patterns","vector db","db","vector","semantic search","search","embedding strategies","algorithms","chunking","semantic","retrieval","embedding","Hybrid Search","hybrid","rag"]