[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFZ4PKYXAC3DCQS9291WMB":3,"skill-same:01M6AFZ4PKYXAC3DCQS9291WMB":74},{"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":23,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6AFZ4PKYXAC3DCQS9291WMB","pricewin-travel-search",null,"Search and compare live hotel and flight prices with the PriceWin MCP server, look up one named hotel, inspect OpenTravel direct listings, send a booking request to a partner hotel (no payment; the guest pays at the property), and cancel one. Use when the user asks to find hotels or flights for dates, compare travel prices, inspect a hotel or room, check a rate's cancellation policy, book a partner hotel, or cancel a booking they made this way.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33473,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fpricewin-travel-search\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"search","pricewin travel search","travel","live","when","send","request","rate","booking","for","prices","at","inspect","hotel","MCP","listings","up","direct","server","mcp server","policy","2026-11-10 10:12:30",false,"---\nname: pricewin-travel-search\ndescription: Search and compare live hotel and flight prices with the PriceWin MCP server, look up one named hotel, inspect OpenTravel direct listings, send a booking request to a partner hotel (no payment; the guest pays at the property), and cancel one. Use when the user asks to find hotels or flights for dates, compare travel prices, inspect a hotel or room, check a rate's cancellation policy, book a partner hotel, or cancel a booking they made this way.\n---\n\n\n# PriceWin Travel Search\n\nUse only the tools of the `pricewin` MCP server (`https:\u002F\u002Fmcp.price.win\u002Fmcp`,\ninstalled with the `web-data\u002Fpricewin` MCP component). Agents prefix them with the server name — for\nexample `mcp__pricewin__search_hotels_live` — and the steps below use the bare\ntool names. Do not replace them with browser automation, shell commands, direct\nAPI calls, or invented booking URLs.\n\nAll prices are in USD.\n\n## Collect the required trip details\n\nFor a hotel search, obtain:\n\n- destination or city;\n- check-in and check-out dates;\n- number of adults, defaulting to 2 when the user does not specify;\n- number of rooms, defaulting to 1.\n\nFor a flight search, obtain:\n\n- origin and destination airport IATA codes;\n- departure date and optional return date;\n- number of adults, defaulting to 1;\n- cabin, defaulting to economy.\n\nResolve unambiguous relative dates from the current date. Ask one concise\nfollow-up when a required date, destination, or airport is genuinely ambiguous.\nNever invent a date or silently choose among multiple plausible airports.\n\nPass `language` matching the user's language when supported. Do not put\nunrelated conversation or personal data in `queryText`.\n\n## Search hotels\n\n1. Call `search_hotels_live` with the destination, dates, occupancy, and only\n   the filters the user actually requested.\n2. Read `sessionId` and `nights` from the response.\n3. Call `poll_search_results` with that `sessionId` and `nights`.\n4. If the response is pending or partial with no useful results, poll again\n   until results arrive, the search completes or fails, or the session expires.\n5. Present a concise comparison of relevant results. Label the source and\n   currency exactly as returned.\n\nUse `hotelName`, `area`, `priceMin`, or `priceMax` only when the user supplied\nthat constraint. Do not claim that a result is the cheapest in the whole\nmarket; describe it as the cheapest among the sources returned for this search.\nA failed or missing source does not invalidate results from other sources.\n\n## Look up one named hotel\n\nWhen the user names a single hotel rather than a city, call\n`get_ota_hotel_detail` with `hotelName` and its `city` (or the Booking.com\n`propertyUrl` from an earlier result) and the user's dates. It returns that\nhotel's rooms, live prices, facilities and reviews from Booking.com.\n\n## Inspect an OpenTravel direct hotel\n\nCall `get_hotel_detail` only for a hotel identified as an OpenTravel direct\nlisting.\n\n- Prefer its `propertyId` from `opentravelResults`.\n- Reuse the user's dates and occupancy.\n- Use `hotelName` plus `city` only when the property is already known to be an\n  OpenTravel direct listing and no `propertyId` is available.\n- Do not call this tool for an Agoda, Booking.com, or Traveloka-only result.\n\nPresent the returned photos, amenities, availability, room capacity, total\nprice, per-night price, and currency without changing their meaning. State\nclearly when availability or a price is missing.\n\n## Answer a question about a hotel\n\nFor questions about a hotel itself — check-in and check-out times, facilities,\nphotos, description, room types — call `get_hotel_info` with the `propertyId`\nof an OpenTravel direct listing, usually from `opentravelResults` of a search\nalready made. It needs no dates and returns no prices or availability; for\nthose, use `get_hotel_detail`. When the property has not published a field,\nsay so rather than filling it in.\n\n## Explain a cancellation policy\n\nCall `get_cancellation_policy` only after `get_hotel_detail` supplies both:\n\n- the property's `propertyId`; and\n- the selected room's `ratePlanId`.\n\nPass the check-in date so the tool can compute an exact deadline. Report the\nreturned non-refundable status, refund percentage, free-cancellation window,\ndeadline, and summary. Never infer a policy or deadline when the tool does not\nreturn one.\n\n## Search flights\n\n1. Call `search_flights_live` with IATA codes, departure date, optional return\n   date, adults, and cabin.\n2. Read the returned `sessionId`.\n3. Call `poll_flight_results` with that `sessionId`.\n4. Continue only until useful results arrive, the search completes or fails, or\n   the session expires.\n5. Present relevant options with source, carrier, times, stops, cabin, currency,\n   and fare exactly as returned.\n\nKeep outbound and return legs distinct. Each leg is a separate one-way ticket\nwith its own booking link: when you pair an outbound and a return flight, give\nthe total as the sum of the two fares and say that each leg is booked\nseparately. Never present a pair as one round-trip ticket, and do not imply that\na fare is still available after the live result expires.\n\n## Request a booking at an OpenTravel direct hotel\n\nOnly an OpenTravel direct listing can be booked this way; an Agoda,\nBooking.com or Traveloka result cannot, and the user follows its own link\ninstead.\n\n1. Call `request_booking` with the `propertyId`, `roomTypeId`, dates and the\n   guest's name, phone number and email. Ask for whichever of those three is\n   missing; they go to the hotel, which needs them to honour the reservation.\n2. Relay the tool's reply as written. The two facts it leads with — that no\n   room is held and that nothing has been charged — are the ones the guest\n   acts on.\n3. Keep the `confirmationCode` it returns; `check_booking_status` reads the\n   request's state back with it.\n\nThere is no payment step, now or later. Never ask how the guest wants to pay,\nand never mention a card, transfer, QR code, payment link or deposit — not\neven one the guest named earlier. The guest pays the property on arrival.\n\n## Cancel a booking\n\n1. Call `get_cancellation_policy` first, with the `propertyId`, `ratePlanId`\n   and check-in date of the booked room, and tell the guest what they will get\n   back — or that the property has published no policy.\n2. Call `request_cancel_token` with the confirmation code and the email on the\n   booking. This cancels nothing; it emails a single-use token.\n3. Ask the guest to paste the token from that email. Never invent, guess or\n   reuse one.\n4. Confirm the booking and the refund amount with the guest in their own\n   language, get an explicit yes, then call `cancel_booking` with the code,\n   the token and the guest's reason.\n\n`cancel_booking` cannot be undone. If there is no token yet, the answer is\nstep 2, never step 4.\n\n## Safety and output rules\n\n- Use only these twelve tools: `search_hotels_live`, `poll_search_results`,\n  `search_flights_live`, `poll_flight_results`, `get_ota_hotel_detail`,\n  `get_hotel_detail`, `get_hotel_info`, `get_cancellation_policy`,\n  `request_booking`, `check_booking_status`, `request_cancel_token`, and\n  `cancel_booking`.\n- Treat all prices as time-sensitive and avoid guarantees or unsupported\n  \"lowest price\" claims.\n- Use only outbound URLs returned by the tools. Never construct, append,\n  rewrite, or guess a booking URL.\n- Collect the guest's name, phone and email only to send a booking request,\n  and only when the guest is actually sending one. Never ask for card data,\n  bank details, credentials, or any other payment information: no tool here\n  accepts them, and no step of this skill takes money.\n- Do not modify an existing booking. There is no tool for it; a change means\n  cancelling and sending a new request, and saying so plainly.\n- If a tool fails, state the limitation briefly and suggest a new search. Do\n  not fabricate partial inventory, prices, availability, or policies.\n","# PriceWin Travel Search\n\nUse only the tools of the `pricewin` MCP server (`https:\u002F\u002Fmcp.price.win\u002Fmcp`,\ninstalled with the `web-data\u002Fpricewin` MCP component). Agents prefix them with the server name — for\nexample `mcp__pricewin__search_hotels_live` — and the steps below use the bare\ntool names. Do not replace them with browser automation, shell commands, direct\nAPI calls, or invented booking URLs.\n\nAll prices are in USD.\n\n## Collect the required trip details\n\nFor a hotel search, obtain:\n\n- destination or city;\n- check-in and check-out dates;\n- number of adults, defaulting to 2 when the user does not specify;\n- number of rooms, defaulting to 1.\n\nFor a flight search, obtain:\n\n- origin and destination airport IATA codes;\n- departure date and optional return date;\n- number of adults, defaulting to 1;\n- cabin, defaulting to economy.\n\nResolve unambiguous relative dates from the current date. Ask one concise\nfollow-up when a required date, destination, or airport is genuinely ambiguous.\nNever invent a date or silently choose among multiple plausible airports.\n\nPass `language` matching the user's language when supported. Do not put\nunrelated conversation or personal data in `queryText`.\n\n## Search hotels\n\n1. Call `search_hotels_live` with the destination, dates, occupancy, and only\n   the filters the user actually requested.\n2. Read `sessionId` and `nights` from the response.\n3. Call `poll_search_results` with that `sessionId` and `nights`.\n4. If the response is pending or partial with no useful results, poll again\n   until results arrive, the search completes or fails, or the session expires.\n5. Present a concise comparison of relevant results. Label the source and\n   currency exactly as returned.\n\nUse `hotelName`, `area`, `priceMin`, or `priceMax` only when the user supplied\nthat constraint. Do not claim that a result is the cheapest in the whole\nmarket; describe it as the cheapest among the sources returned for this search.\nA failed or missing source does not invalidate results from other sources.\n\n## Look up one named hotel\n\nWhen the user names a single hotel rather than a city, call\n`get_ota_hotel_detail` with `hotelName` and its `city` (or the Booking.com\n`propertyUrl` from an earlier result) and the user's dates. It returns that\nhotel's rooms, live prices, facilities and reviews from Booking.com.\n\n## Inspect an OpenTravel direct hotel\n\nCall `get_hotel_detail` only for a hotel identified as an OpenTravel direct\nlisting.\n\n- Prefer its `propertyId` from `opentravelResults`.\n- Reuse the user's dates and occupancy.\n- Use `hotelName` plus `city` only when the property is already known to be an\n  OpenTravel direct listing and no `propertyId` is available.\n- Do not call this tool for an Agoda, Booking.com, or Traveloka-only result.\n\nPresent the returned photos, amenities, availability, room capacity, total\nprice, per-night price, and currency without changing their meaning. State\nclearly when availability or a price is missing.\n\n## Answer a question about a hotel\n\nFor questions about a hotel itself — check-in and check-out times, facilities,\nphotos, description, room types — call `get_hotel_info` with the `propertyId`\nof an OpenTravel direct listing, usually from `opentravelResults` of a search\nalready made. It needs no dates and returns no prices or availability; for\nthose, use `get_hotel_detail`. When the property has not published a field,\nsay so rather than filling it in.\n\n## Explain a cancellation policy\n\nCall `get_cancellation_policy` only after `get_hotel_detail` supplies both:\n\n- the property's `propertyId`; and\n- the selected room's `ratePlanId`.\n\nPass the check-in date so the tool can compute an exact deadline. Report the\nreturned non-refundable status, refund percentage, free-cancellation window,\ndeadline, and summary. Never infer a policy or deadline when the tool does not\nreturn one.\n\n## Search flights\n\n1. Call `search_flights_live` with IATA codes, departure date, optional return\n   date, adults, and cabin.\n2. Read the returned `sessionId`.\n3. Call `poll_flight_results` with that `sessionId`.\n4. Continue only until useful results arrive, the search completes or fails, or\n   the session expires.\n5. Present relevant options with source, carrier, times, stops, cabin, currency,\n   and fare exactly as returned.\n\nKeep outbound and return legs distinct. Each leg is a separate one-way ticket\nwith its own booking link: when you pair an outbound and a return flight, give\nthe total as the sum of the two fares and say that each leg is booked\nseparately. Never present a pair as one round-trip ticket, and do not imply that\na fare is still available after the live result expires.\n\n## Request a booking at an OpenTravel direct hotel\n\nOnly an OpenTravel direct listing can be booked this way; an Agoda,\nBooking.com or Traveloka result cannot, and the user follows its own link\ninstead.\n\n1. Call `request_booking` with the `propertyId`, `roomTypeId`, dates and the\n   guest's name, phone number and email. Ask for whichever of those three is\n   missing; they go to the hotel, which needs them to honour the reservation.\n2. Relay the tool's reply as written. The two facts it leads with — that no\n   room is held and that nothing has been charged — are the ones the guest\n   acts on.\n3. Keep the `confirmationCode` it returns; `check_booking_status` reads the\n   request's state back with it.\n\nThere is no payment step, now or later. Never ask how the guest wants to pay,\nand never mention a card, transfer, QR code, payment link or deposit — not\neven one the guest named earlier. The guest pays the property on arrival.\n\n## Cancel a booking\n\n1. Call `get_cancellation_policy` first, with the `propertyId`, `ratePlanId`\n   and check-in date of the booked room, and tell the guest what they will get\n   back — or that the property has published no policy.\n2. Call `request_cancel_token` with the confirmation code and the email on the\n   booking. This cancels nothing; it emails a single-use token.\n3. Ask the guest to paste the token from that email. Never invent, guess or\n   reuse one.\n4. Confirm the booking and the refund amount with the guest in their own\n   language, get an explicit yes, then call `cancel_booking` with the code,\n   the token and the guest's reason.\n\n`cancel_booking` cannot be undone. If there is no token yet, the answer is\nstep 2, never step 4.\n\n## Safety and output rules\n\n- Use only these twelve tools: `search_hotels_live`, `poll_search_results`,\n  `search_flights_live`, `poll_flight_results`, `get_ota_hotel_detail`,\n  `get_hotel_detail`, `get_hotel_info`, `get_cancellation_policy`,\n  `request_booking`, `check_booking_status`, `request_cancel_token`, and\n  `cancel_booking`.\n- Treat all prices as time-sensitive and avoid guarantees or unsupported\n  \"lowest price\" claims.\n- Use only outbound URLs returned by the tools. Never construct, append,\n  rewrite, or guess a booking URL.\n- Collect the guest's name, phone and email only to send a booking request,\n  and only when the guest is actually sending one. Never ask for card data,\n  bank details, credentials, or any other payment information: no tool here\n  accepts them, and no step of this skill takes money.\n- Do not modify an existing booking. There is no tool for it; a change means\n  cancelling and sending a new request, and saying so plainly.\n- If a tool fails, state the limitation briefly and suggest a new search. Do\n  not fabricate partial inventory, prices, availability, or policies.\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fpricewin-travel-search",3935,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-13 11:21:37",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add davila7\u002Fclaude-code-templates --skill pricewin-travel-search",{"tool":66,"command":67},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill pricewin-travel-search",{"tool":69,"command":70},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill pricewin-travel-search","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fpricewin-travel-search\u002FSKILL.md",true,[],[75,101,128,160,195,219],{"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":82,"publishedAt":45},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[81],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[83,84,85,86,87,33,88,89,90,28,91,92,93,94,95,96,97,98,99,100],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","use","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":108,"publishedAt":45},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[107],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[109,110,111,112,113,114,115,116,117,118,119,28,120,121,122,123,124,125,126,127],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":143,"publishedAt":45},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[134,137,138],{"categoryNo":135,"categoryName":136,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[144,145,146,147,148,149,150,33,151,152,153,154,155,156,38,90,157,158,28,159],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","access","database","query",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":164,"licenseFileUrl":165,"sourceHtmlUrl":166,"categories":167,"keywords":171,"publishedAt":45},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[168],{"categoryNo":169,"categoryName":170,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[172,173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,33,194],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":164,"licenseFileUrl":199,"sourceHtmlUrl":200,"categories":201,"keywords":206,"publishedAt":45},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[202,205],{"categoryNo":203,"categoryName":204,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":169,"categoryName":170,"taxonomyType":21,"taxonomyTypeDesc":22},[207,208,209,210,211,173,212,182,183,213,214,215,216,33,217,92,218],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":164,"licenseFileUrl":223,"sourceHtmlUrl":224,"categories":225,"keywords":233,"publishedAt":45},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[226,229,230],{"categoryNo":227,"categoryName":228,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":231,"categoryName":232,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000036","内容创作者",[234,235,236,237,238,239,240,241,175,242,185,120,243,244,245,246,40,156,247,28,248,249,250,251,252,98,253],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","invoke","you","analysis","claims","argument","assemble","recommendations"]