[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M736WA5XE11BHEW2RKEGDVR0":3,"skill-same:01M736WA5XE11BHEW2RKEGDVR0":49},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M736WA5XE11BHEW2RKEGDVR0","recsys-pipeline-architect",null,"Design composable recommendation, ranking, and feed pipelines using the six-stage Source→Hydrator→Filter→Scorer→Selector→SideEffect framework popularized by xAI's open-sourced For You algorithm. Use this skill whenever the user is building any system that picks \"the top K items for a (user, context)\" — social feeds, content CMSs, RAG rerankers, task prioritizers, notification triage, search reranking, ad ranking.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frecsys-pipeline-architect\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: recsys-pipeline-architect\ndescription: Design composable recommendation, ranking, and feed pipelines using the six-stage Source→Hydrator→Filter→Scorer→Selector→SideEffect framework popularized by xAI's open-sourced For You algorithm. Use this skill whenever the user is building any system that picks \"the top K items for a (user, context)\" — social feeds, content CMSs, RAG rerankers, task prioritizers, notification triage, search reranking, ad ranking.\norigin: community\n---\n\n# recsys-pipeline-architect\n\nA spec-and-scaffold skill for building composable recommendation, ranking, and feed pipelines. It encodes the **six-stage pattern** — Source → Hydrator → Filter → Scorer → Selector → SideEffect — popularized by xAI's open-sourced [For You algorithm](https:\u002F\u002Fgithub.com\u002Fxai-org\u002Fx-algorithm) (Apache 2.0). This skill is an independent reimplementation of the pattern (MIT) — no code copied from the original.\n\nUpstream: \u003Chttps:\u002F\u002Fgithub.com\u002Fmturac\u002Frecsys-pipeline-architect>\n\n## When to Use\n\n- User wants to build any system that picks \"the top K items for a user\u002Fcontext\"\n- User asks \"how should I rank X\" or describes a feed\u002Fpersonalization problem\n- User has a scoring function and needs the pipeline plumbing around it\n- User wants to migrate from a single relevance score to multi-action prediction with tunable weights\n- User is wrapping an LLM\u002FML scorer and needs filters, hydrators, side-effects, and a runnable scaffold in their stack (TypeScript \u002F Go \u002F Python)\n- Triggers: \"recommendation system\", \"feed algorithm\", \"ranking pipeline\", \"for you feed\", \"candidate pipeline\", \"content recommender\", \"pipeline architecture for recsys\", \"RAG retrieval reranker\"\n\n## When NOT to Use\n\n- Model architecture work (transformer design, two-tower retrieval, embedding training) — this skill is plumbing *around* the model, not the model itself\n- Pure ML training pipelines — the scoring function is the user's responsibility\n- Operating a deployed pipeline (monitoring, autoscaling) — out of scope\n\n## The six-stage framework\n\n| # | Stage | Job | Parallel? |\n|---|---|---|---|\n| 1 | **Source** | Fetch candidates from one or more origins | Yes — multiple sources run in parallel |\n| 2 | **Hydrator** | Enrich each candidate with metadata needed for filtering and scoring | Yes — independent hydrators run in parallel |\n| 3 | **Filter** | Drop candidates that should never be shown (blocked, expired, duplicate, ineligible) | Sequential — each filter sees fewer items |\n| 4 | **Scorer** | Assign each surviving candidate one or more scores | Sequential — later scorers see earlier scores |\n| 5 | **Selector** | Sort by final score, return top K | Single op |\n| 6 | **SideEffect** | Cache served IDs, log impressions, emit events, update counters | Async — must never block the response |\n\n### Why this exact order\n\n- Sources before hydration: know what candidates exist before paying to enrich them\n- Hydration before filtering: many filters need metadata the source did not provide\n- Filtering before scoring: scoring is the expensive stage; drop the ineligible first\n- Scorer chain (not single scorer): real systems compose ML scoring + diversity reranking + business rules\n- Selector after scoring: keeps scoring deterministic and cacheable\n- SideEffects last and async: side effects must never block the user response\n\n## Workflow when invoked\n\nWalk the user through these eight steps:\n\n1. **Clarify the use case** (one round, three questions): items being ranked? input context? language\u002Fruntime?\n2. **Identify the candidate sources**: usually in-network (followed\u002Fowned\u002Fsubscribed) + out-of-network (ML retrieval \u002F trending \u002F similar-to-liked)\n3. **List required hydrations**: for each filter and scorer, what data does it need that the source did not provide?\n4. **List the filters**: duplicate, self, age, block\u002Fmute, previously-served, eligibility. Order matters — cheap before expensive.\n5. **Design the scorer chain**: primary (ML) → combiner (multi-action with weights) → diversity → business rules\n6. **Selector**: sort descending by final score, take top K (or stratified mix for in-network\u002Fout-of-network)\n7. **SideEffects**: cache served IDs, emit impression events, update counters, log analytics — all fire-and-forget\n8. **Generate the scaffold** in the user's stack\n\n## Key trade-offs to surface (don't default silently)\n\n### 1. Single score vs multi-action prediction\n\n- **Single score**: train one model to predict relevance. To change behavior → retrain.\n- **Multi-action**: predict `P(action)` for many actions (read, like, share, skip, report), combine with weights at serving time. To change behavior → change weights. No retraining.\n\nThe X For You system uses multi-action with both positive and negative weights. Recommend multi-action when the user expects to tune frequently.\n\n### 2. Candidate isolation in scoring\n\n- **Isolated**: each candidate scored independently. Deterministic, cacheable.\n- **Joint**: candidates attend to each other during scoring (e.g., transformer over batch). More expressive but non-deterministic across batches.\n\nDefault to isolation. Joint only when there's a specific reason (e.g., explicit batch-aware diversity).\n\n### 3. Online vs offline\n\n- **Request-time (online)**: pipeline runs on each request. Latency budget: 100–300ms. Default.\n- **Pre-computed (offline batch)**: pipeline runs periodically, results cached. Lower latency, lower freshness.\n- **Hybrid**: candidate retrieval offline, ranking online.\n\n## Hard rules\n\n1. **Do not invent benchmark numbers.** \"How much faster?\" → \"depends on workload, run it yourself.\"\n2. **Attribution discipline.** When the pattern is referenced, attribute as \"popularized by xAI's open-sourced For You algorithm\" \u002F `github.com\u002Fxai-org\u002Fx-algorithm` (Apache 2.0).\n3. **No trademark use.** Do not name the user's artifact \"X-like\" or use \"For You\" branding. Pattern is free; brand is not. Suggested naming: \"candidate pipeline\", \"feed pipeline\", \"ranking pipeline\", \"recsys pipeline\".\n4. **Surface trade-offs.** Multi-action vs single, isolation vs joint, online vs offline — never default silently.\n5. **The generated scaffold must run.** No pseudocode passing as code.\n6. **Filter order matters.** Cheap before expensive. Universal before user-specific.\n7. **Side effects never block.** Wrap in fire-and-forget patterns (goroutines \u002F promises without await \u002F asyncio tasks).\n\n## Anti-Patterns\n\n- Scoring before filtering (wastes compute on candidates that will be dropped anyway)\n- Synchronous side effects (cache writes \u002F impression emits blocking the response)\n- A single \"relevance\" score when the product needs to tune for multiple objectives (engagement vs safety vs diversity vs ads)\n- Joint scoring as default (non-deterministic, harder to cache, doesn't compose with reranking stages)\n- Generating pseudocode \"for illustration\" — the scaffold must actually run\n\n## Upstream contents\n\nThe upstream repository at \u003Chttps:\u002F\u002Fgithub.com\u002Fmturac\u002Frecsys-pipeline-architect> ships:\n\n- Full `SKILL.md` with the complete 8-step workflow\n- 5 load-on-demand reference docs: interfaces in 4 languages (TS\u002FGo\u002FPython\u002FRust), multi-action scoring pattern, candidate isolation, filter cookbook (12 patterns), scorer cookbook (weighted sum, MMR, diversity penalty, position debiasing)\n- 3 runnable example scaffolds, every one green on its test suite:\n  - Strapi v5 plugin (TypeScript \u002F Jest — 3\u002F3 pass)\n  - Zentra-compatible pipeline (Go with generics — 3\u002F3 pass)\n  - PMAI task prioritizer (Python \u002F FastAPI \u002F pytest — 3\u002F3 pass)\n- v0.1.0 release tagged\n- MIT license; pattern attributed to xAI X For You algorithm (Apache 2.0)\n\nInstall via skills.sh: `npx skills add mturac\u002Frecsys-pipeline-architect`\n","# recsys-pipeline-architect\n\nA spec-and-scaffold skill for building composable recommendation, ranking, and feed pipelines. It encodes the **six-stage pattern** — Source → Hydrator → Filter → Scorer → Selector → SideEffect — popularized by xAI's open-sourced [For You algorithm](https:\u002F\u002Fgithub.com\u002Fxai-org\u002Fx-algorithm) (Apache 2.0). This skill is an independent reimplementation of the pattern (MIT) — no code copied from the original.\n\nUpstream: \u003Chttps:\u002F\u002Fgithub.com\u002Fmturac\u002Frecsys-pipeline-architect>\n\n## When to Use\n\n- User wants to build any system that picks \"the top K items for a user\u002Fcontext\"\n- User asks \"how should I rank X\" or describes a feed\u002Fpersonalization problem\n- User has a scoring function and needs the pipeline plumbing around it\n- User wants to migrate from a single relevance score to multi-action prediction with tunable weights\n- User is wrapping an LLM\u002FML scorer and needs filters, hydrators, side-effects, and a runnable scaffold in their stack (TypeScript \u002F Go \u002F Python)\n- Triggers: \"recommendation system\", \"feed algorithm\", \"ranking pipeline\", \"for you feed\", \"candidate pipeline\", \"content recommender\", \"pipeline architecture for recsys\", \"RAG retrieval reranker\"\n\n## When NOT to Use\n\n- Model architecture work (transformer design, two-tower retrieval, embedding training) — this skill is plumbing *around* the model, not the model itself\n- Pure ML training pipelines — the scoring function is the user's responsibility\n- Operating a deployed pipeline (monitoring, autoscaling) — out of scope\n\n## The six-stage framework\n\n| # | Stage | Job | Parallel? |\n|---|---|---|---|\n| 1 | **Source** | Fetch candidates from one or more origins | Yes — multiple sources run in parallel |\n| 2 | **Hydrator** | Enrich each candidate with metadata needed for filtering and scoring | Yes — independent hydrators run in parallel |\n| 3 | **Filter** | Drop candidates that should never be shown (blocked, expired, duplicate, ineligible) | Sequential — each filter sees fewer items |\n| 4 | **Scorer** | Assign each surviving candidate one or more scores | Sequential — later scorers see earlier scores |\n| 5 | **Selector** | Sort by final score, return top K | Single op |\n| 6 | **SideEffect** | Cache served IDs, log impressions, emit events, update counters | Async — must never block the response |\n\n### Why this exact order\n\n- Sources before hydration: know what candidates exist before paying to enrich them\n- Hydration before filtering: many filters need metadata the source did not provide\n- Filtering before scoring: scoring is the expensive stage; drop the ineligible first\n- Scorer chain (not single scorer): real systems compose ML scoring + diversity reranking + business rules\n- Selector after scoring: keeps scoring deterministic and cacheable\n- SideEffects last and async: side effects must never block the user response\n\n## Workflow when invoked\n\nWalk the user through these eight steps:\n\n1. **Clarify the use case** (one round, three questions): items being ranked? input context? language\u002Fruntime?\n2. **Identify the candidate sources**: usually in-network (followed\u002Fowned\u002Fsubscribed) + out-of-network (ML retrieval \u002F trending \u002F similar-to-liked)\n3. **List required hydrations**: for each filter and scorer, what data does it need that the source did not provide?\n4. **List the filters**: duplicate, self, age, block\u002Fmute, previously-served, eligibility. Order matters — cheap before expensive.\n5. **Design the scorer chain**: primary (ML) → combiner (multi-action with weights) → diversity → business rules\n6. **Selector**: sort descending by final score, take top K (or stratified mix for in-network\u002Fout-of-network)\n7. **SideEffects**: cache served IDs, emit impression events, update counters, log analytics — all fire-and-forget\n8. **Generate the scaffold** in the user's stack\n\n## Key trade-offs to surface (don't default silently)\n\n### 1. Single score vs multi-action prediction\n\n- **Single score**: train one model to predict relevance. To change behavior → retrain.\n- **Multi-action**: predict `P(action)` for many actions (read, like, share, skip, report), combine with weights at serving time. To change behavior → change weights. No retraining.\n\nThe X For You system uses multi-action with both positive and negative weights. Recommend multi-action when the user expects to tune frequently.\n\n### 2. Candidate isolation in scoring\n\n- **Isolated**: each candidate scored independently. Deterministic, cacheable.\n- **Joint**: candidates attend to each other during scoring (e.g., transformer over batch). More expressive but non-deterministic across batches.\n\nDefault to isolation. Joint only when there's a specific reason (e.g., explicit batch-aware diversity).\n\n### 3. Online vs offline\n\n- **Request-time (online)**: pipeline runs on each request. Latency budget: 100–300ms. Default.\n- **Pre-computed (offline batch)**: pipeline runs periodically, results cached. Lower latency, lower freshness.\n- **Hybrid**: candidate retrieval offline, ranking online.\n\n## Hard rules\n\n1. **Do not invent benchmark numbers.** \"How much faster?\" → \"depends on workload, run it yourself.\"\n2. **Attribution discipline.** When the pattern is referenced, attribute as \"popularized by xAI's open-sourced For You algorithm\" \u002F `github.com\u002Fxai-org\u002Fx-algorithm` (Apache 2.0).\n3. **No trademark use.** Do not name the user's artifact \"X-like\" or use \"For You\" branding. Pattern is free; brand is not. Suggested naming: \"candidate pipeline\", \"feed pipeline\", \"ranking pipeline\", \"recsys pipeline\".\n4. **Surface trade-offs.** Multi-action vs single, isolation vs joint, online vs offline — never default silently.\n5. **The generated scaffold must run.** No pseudocode passing as code.\n6. **Filter order matters.** Cheap before expensive. Universal before user-specific.\n7. **Side effects never block.** Wrap in fire-and-forget patterns (goroutines \u002F promises without await \u002F asyncio tasks).\n\n## Anti-Patterns\n\n- Scoring before filtering (wastes compute on candidates that will be dropped anyway)\n- Synchronous side effects (cache writes \u002F impression emits blocking the response)\n- A single \"relevance\" score when the product needs to tune for multiple objectives (engagement vs safety vs diversity vs ads)\n- Joint scoring as default (non-deterministic, harder to cache, doesn't compose with reranking stages)\n- Generating pseudocode \"for illustration\" — the scaffold must actually run\n\n## Upstream contents\n\nThe upstream repository at \u003Chttps:\u002F\u002Fgithub.com\u002Fmturac\u002Frecsys-pipeline-architect> ships:\n\n- Full `SKILL.md` with the complete 8-step workflow\n- 5 load-on-demand reference docs: interfaces in 4 languages (TS\u002FGo\u002FPython\u002FRust), multi-action scoring pattern, candidate isolation, filter cookbook (12 patterns), scorer cookbook (weighted sum, MMR, diversity penalty, position debiasing)\n- 3 runnable example scaffolds, every one green on its test suite:\n  - Strapi v5 plugin (TypeScript \u002F Jest — 3\u002F3 pass)\n  - Zentra-compatible pipeline (Go with generics — 3\u002F3 pass)\n  - PMAI task prioritizer (Python \u002F FastAPI \u002F pytest — 3\u002F3 pass)\n- v0.1.0 release tagged\n- MIT license; pattern attributed to xAI X For You algorithm (Apache 2.0)\n\nInstall via skills.sh: `npx skills add mturac\u002Frecsys-pipeline-architect`\n",{"name":5,"origin":24,"description":7},"community","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa",".claude\u002Fskills\u002Frecsys-pipeline-architect",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill recsys-pipeline-architect",{"tool":41,"command":42},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill recsys-pipeline-architect",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill recsys-pipeline-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frecsys-pipeline-architect\u002FSKILL.md",true,[],[50,58,65,73,81,89],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":54,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":69,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]