[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EJSXG76797ZY9WPS3FCX3F":3,"skill-same:01M7EJSXG76797ZY9WPS3FCX3F":44},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7EJSXG76797ZY9WPS3FCX3F","ui-design",null,"Use when a UI is to be designed, specified, or restyled before it is built: choosing colours, spacing, type or a look, setting up dark mode, writing down what two products must share, or deciding what a new panel, page, or CLI output should follow. Triggers: design the UI, decide colours and spacing, dark mode, design tokens, style guide, make it look like the rest, same look on web and desktop, navrhni vzhled, design system, jak ma vypadat. Writes the design source that builds and audits read. Measuring a running UI is ui-audit and ux-audit; accessibility criteria are a11y-audit; syntax is the family skills.","qsmark-labs\u002Fqsm-marketplace","qsmark-labs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F348383745?v=4","01M7EJDK5MKZ67A7JBGC3ZB1RP","QSM-LABS","01M7EJDK6649PCGA2ENGFMFA7E",0,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Fqsmark-labs\u002Fqsm-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fqsm-uix\u002Fskills\u002Fui-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ui-design\ndescription: \"Use when a UI is to be designed, specified, or restyled before it is built: choosing colours, spacing, type or a look, setting up dark mode, writing down what two products must share, or deciding what a new panel, page, or CLI output should follow. Triggers: design the UI, decide colours and spacing, dark mode, design tokens, style guide, make it look like the rest, same look on web and desktop, navrhni vzhled, design system, jak ma vypadat. Writes the design source that builds and audits read. Measuring a running UI is ui-audit and ux-audit; accessibility criteria are a11y-audit; syntax is the family skills.\"\n---\n\n# UI Design\n\nA UI built from taste drifts: components choose their own greys, gaps and dark values. This skill\nserves the person who builds accessible interfaces. It writes one design source before the first\ncomponent, for builders to follow and audits to measure. It chooses constraints, not palettes,\nfont pairings or frameworks; the maintainer picks the hues. It does not audit a running UI.\n\n## Decide in this order\n\nWork top-down: a late concern costs a rebuild, an early one a sentence.\n\n1. **Accessibility floor.** What every user must be able to do (keyboard only, screen reader,\n   reduced motion, larger text, no reliance on colour). It goes into `## Requirements` first, so\n   every later choice is made inside it.\n2. **Interaction.** The one primary action per surface, how states read, target sizes, feedback.\n3. **Tokens and scales.** The values everything traces to.\n4. **Layout and hierarchy.** Grouping, rhythm, reserved space.\n5. **Style.** The look, last, because it is the cheapest to change and the easiest to argue about.\n\n## Detect before you ask\n\nFind the existing design folder, theme, tokens or screenshot before assuming a stack. Extend an\nexisting design source, never regenerate it. Ask only what changes it: surfaces, audience, fixed\nbrand colours. Keep the source stack-neutral and mark assumptions in the draft, so the person\ncorrects concrete tokens and ratios rather than a questionnaire.\n\n## The design source\n\nOne markdown set: `design\u002FMASTER.md` for everything global, `design\u002Fpages\u002F\u003Csurface>.md` for what\none surface changes. The page file wins on conflict, so a surface can differ without forking the\nmaster. Read both before editing either, and never overwrite a file the person wrote without\ntheir say-so, because the source is their decision record, not output.\n\nUse these headings, because the audits and the stack skills look for them:\n\n| Heading | Holds |\n| --- | --- |\n| `## Tokens` | the palette (a neutral ladder and named hues, light and dark), then roles: name, meaning, light, dark, each a palette name. Roles, not hues: `surface`, `primary`, `danger` |\n| `## Pairs` | fill, on-fill, ratio in light, ratio in dark |\n| `## Scales` | space, type, radius, elevation, layer, icon size, motion, density |\n| `## Style` | the one container separation, constraints, the requirements it brings, do not use for |\n| `## Requirements` | the accessibility floor the source commits to |\n\n## Rules\n\n- **The palette's structure is ui-palette's.** Role sentences, neutrals against hues, components\n  reading roles, one container separation and a theme from an image: this source holds the result\n  in `## Tokens` and `## Style`.\n- **Hover is for a fine hovering pointer.** A hover effect applies only where the device has one\n  (animate and review-animations point here), because a touch screen fires hover on tap and shows\n  it as a false positive.\n- **Every colour is a token, and a fill token never travels alone.** Define `primary` with\n  `on-primary` and record the ratio per theme: 4.5 for text, 3 for large text, icons, control\n  borders and focus indicators (WCAG 1.4.3, 1.4.11). Why: contrast belongs to a pair, so a colour\n  checked alone is checked against nothing. Compute the ratio with the WCAG relative-luminance\n  formula, never estimate it (`qsm-uix contrast` reads pixels of an image, so it verifies the built\n  pair later).\n- **Design each theme on its own column.** Write dark values by choosing them against dark\n  surfaces, then check them; an inverted light palette fails because shadows vanish, saturated\n  fills glare, and light borders turn into holes. Parity means every pair passes in each theme\n  and a border, divider, or state visible in one is visible in the other. High contrast, if\n  wanted, is a third column.\n- **Every dimension is a scale, and a component picks a step.** Use the product's spacing and type\n  scales, naming the adopted system. Carbon's 2\u002F4\u002F8 spacing multiples and Modular Scale's 1.125\n  major-second ratio are choices, not universal floors; USWDS uses non-geometric type steps.\n  Define one set each for radius, elevation, layer (z-order), icon size, motion and density. Why: a\n  literal in a component is a decision nobody reviewed, and a scale is how one change reaches\n  every surface. Density is an axis of the scale (compact, regular), not a second design.\n- **Every pressable has a pressed state, and no state moves its neighbours.** The press shrinks\n  the element to 0.95 to 0.98 of its size at once, as a transform on the pressed state that does\n  not change layout bounds (animate owns it); hover, focus and disabled change colour, opacity or\n  elevation and keep the box. The focus indicator reaches 3:1 against its neighbours. Why: a\n  press with no response feels like the UI did not hear the person.\n- **Defaults carry the design; options are for the few.** Most people never change a setting, so\n  the defaults must already be the best the design has.\n- **A component's character is one personality.** A professional dashboard is crisp and dense, a\n  playful tool may be looser; a rule right in isolation reads wrong beside another character.\n- **A raised surface (overlay, popover) separates by a soft shadow, not a solid border.** A\n  semi-transparent shadow reads as depth; an opaque border reads as a box drawn around the content\n  (emilkowalski\u002Fskills README.md names a solid border over a shadow as an agent mistake). In a dark\n  theme an overlay also gets a 1 px low-alpha light edge, because a shadow vanishes on a dark\n  surface, and the edge is never opaque. A low-alpha separator on a card is decorative: WCAG 1.4.11\n  applies to the boundaries of controls and inputs, so the 3:1 rule is for those.\n- **A wait shows feedback by its length.** No busy indicator under 150 to 300 ms, because a\n  flash reads as a glitch (Vercel guidelines README: 150 to 300 ms, and once shown 300 to 500 ms);\n  over 1 s always feedback; a progress bar with a count past about 10 s when the length is known.\n  The 1 s and 10 s limits are the owner's decision. The families write the form.\n- **Handle edge cases where nobody looks.** A hover that must survive the gap between stacked\n  items, a timer that pauses when the view is hidden, a drag that continues outside its box.\n- **Targets carry a floor.** 44 px on touch (Vercel web-interface-guidelines README); 24 px is\n  the WCAG 2.5.8 floor, labelled as such. The source records any override per project with its\n  reason, because a threshold silently changed is a regression nobody can find.\n- **One primary action per surface.** Secondary actions are visibly subordinate and a destructive\n  one is separated and named as such. Why: when two things shout, the user has to decide what\n  the design should have decided.\n- **Colour is never the only carrier of meaning.** Each status token comes with a word, glyph or\n  shape (error is red and says what failed).\n- **An icon stands alone only where everyone reads it the same** (close, play, volume), and then\n  it has a tooltip and an accessible name; otherwise the control is a text label. Never icon and\n  label on one button, because the pair says one thing twice and costs width.\n- **A number comes from a named source.** Before choosing a colour, size, offset or duration, name\n  the token, reference file or mockup it comes from. With none, show two candidates live and wait\n  for the owner's pick; never tune a value from geometry alone, because the owner then supplies\n  the number anyway.\n- **Pastel or alive is a target, not an adjective.** Give each role a chroma and lightness range\n  (OKLCH) and check each accent is visible on the surface it sits on. Grey or dull is a finding,\n  and a role never shown is one too.\n- **Repeated list items are separated by one named device**: a gap, a hairline, or a surface step\n  (own body, a slight shadow allowed). A shadow alone is not a separator, and adjacent items\n  differ at rest.\n- **A token or colour pass changes values only.** List every visible element (separators,\n  handles, glass edge, readouts, layout) before and after and confirm each survives.\n- **The owner's chat ruling beats an older source line, and the source changes by principle.**\n  Edit the line in place in the same change and quote the owner; an overruled line is out of date,\n  not authority. Trace a complaint to the principle it broke and change the token that carries it\n  (\"the sidebar warning is too loud\" breaks \"a status colour marks a state, never a region\", so\n  `warning` changes, not a sidebar exception), because a line per complaint stacks.\n- **Prefer the platform's control to a custom one**, unless the source says why not. The system\n  one brings keyboard, focus, scaling and screen reader behaviour for free.\n- **A style is a constraint set, never a name.** Write what the look requires (for example \"raised\n  surfaces separate by a soft shadow, never an opaque border\"), the accessibility it brings, and\n  where it must not be used (dense data, small text, high-contrast users). Why: a named fad such as\n  \"glass\" says nothing the audit can measure; a constraint can fail a pair.\n\n## Output\n\nWrite `design\u002FMASTER.md` (and a page file only when a surface differs). When no file can be written,\ngive the same content in the reply. Keep it short: tokens in a table, not prose. Mark each threshold\nas default or override. Close with `## Requirements`, then tell the person what to do next: build\nwith the stack skill, then run ui-audit against this file, which is the expected column.\n\n## Red flags\n\n- When you reach for a hex literal in a component description, name a token instead, because the\n  literal is invisible to the audit and to the next theme.\n- When the draft names a framework, a stack's property or component type, move it to the stack\n  skill, because the source must survive a change of stack.\n- When you are about to list palettes, font pairings, or \"styles for SaaS\", stop and write the\n  token roles and constraints, because the person picks the look and the source holds its rules.\n\n## Say it in the reply\n\n- The path of the design source written, and which parts are defaults versus the person's choices.\n- The contrast ratio per pair and theme, computed, with the tool or formula used.\n- What was assumed, what was asked, and the open decisions left for the person.\n- What is not covered: no running UI was measured, so nothing is verified until ui-audit runs.\n\nHow each rule is built and exposed on a stack is its family: desktop (desktop-ui, qml-ui),\nterminal (cli-ui, tui-ui), web (css-ui, react-ui, web-motion).\n","# UI Design\n\nA UI built from taste drifts: components choose their own greys, gaps and dark values. This skill\nserves the person who builds accessible interfaces. It writes one design source before the first\ncomponent, for builders to follow and audits to measure. It chooses constraints, not palettes,\nfont pairings or frameworks; the maintainer picks the hues. It does not audit a running UI.\n\n## Decide in this order\n\nWork top-down: a late concern costs a rebuild, an early one a sentence.\n\n1. **Accessibility floor.** What every user must be able to do (keyboard only, screen reader,\n   reduced motion, larger text, no reliance on colour). It goes into `## Requirements` first, so\n   every later choice is made inside it.\n2. **Interaction.** The one primary action per surface, how states read, target sizes, feedback.\n3. **Tokens and scales.** The values everything traces to.\n4. **Layout and hierarchy.** Grouping, rhythm, reserved space.\n5. **Style.** The look, last, because it is the cheapest to change and the easiest to argue about.\n\n## Detect before you ask\n\nFind the existing design folder, theme, tokens or screenshot before assuming a stack. Extend an\nexisting design source, never regenerate it. Ask only what changes it: surfaces, audience, fixed\nbrand colours. Keep the source stack-neutral and mark assumptions in the draft, so the person\ncorrects concrete tokens and ratios rather than a questionnaire.\n\n## The design source\n\nOne markdown set: `design\u002FMASTER.md` for everything global, `design\u002Fpages\u002F\u003Csurface>.md` for what\none surface changes. The page file wins on conflict, so a surface can differ without forking the\nmaster. Read both before editing either, and never overwrite a file the person wrote without\ntheir say-so, because the source is their decision record, not output.\n\nUse these headings, because the audits and the stack skills look for them:\n\n| Heading | Holds |\n| --- | --- |\n| `## Tokens` | the palette (a neutral ladder and named hues, light and dark), then roles: name, meaning, light, dark, each a palette name. Roles, not hues: `surface`, `primary`, `danger` |\n| `## Pairs` | fill, on-fill, ratio in light, ratio in dark |\n| `## Scales` | space, type, radius, elevation, layer, icon size, motion, density |\n| `## Style` | the one container separation, constraints, the requirements it brings, do not use for |\n| `## Requirements` | the accessibility floor the source commits to |\n\n## Rules\n\n- **The palette's structure is ui-palette's.** Role sentences, neutrals against hues, components\n  reading roles, one container separation and a theme from an image: this source holds the result\n  in `## Tokens` and `## Style`.\n- **Hover is for a fine hovering pointer.** A hover effect applies only where the device has one\n  (animate and review-animations point here), because a touch screen fires hover on tap and shows\n  it as a false positive.\n- **Every colour is a token, and a fill token never travels alone.** Define `primary` with\n  `on-primary` and record the ratio per theme: 4.5 for text, 3 for large text, icons, control\n  borders and focus indicators (WCAG 1.4.3, 1.4.11). Why: contrast belongs to a pair, so a colour\n  checked alone is checked against nothing. Compute the ratio with the WCAG relative-luminance\n  formula, never estimate it (`qsm-uix contrast` reads pixels of an image, so it verifies the built\n  pair later).\n- **Design each theme on its own column.** Write dark values by choosing them against dark\n  surfaces, then check them; an inverted light palette fails because shadows vanish, saturated\n  fills glare, and light borders turn into holes. Parity means every pair passes in each theme\n  and a border, divider, or state visible in one is visible in the other. High contrast, if\n  wanted, is a third column.\n- **Every dimension is a scale, and a component picks a step.** Use the product's spacing and type\n  scales, naming the adopted system. Carbon's 2\u002F4\u002F8 spacing multiples and Modular Scale's 1.125\n  major-second ratio are choices, not universal floors; USWDS uses non-geometric type steps.\n  Define one set each for radius, elevation, layer (z-order), icon size, motion and density. Why: a\n  literal in a component is a decision nobody reviewed, and a scale is how one change reaches\n  every surface. Density is an axis of the scale (compact, regular), not a second design.\n- **Every pressable has a pressed state, and no state moves its neighbours.** The press shrinks\n  the element to 0.95 to 0.98 of its size at once, as a transform on the pressed state that does\n  not change layout bounds (animate owns it); hover, focus and disabled change colour, opacity or\n  elevation and keep the box. The focus indicator reaches 3:1 against its neighbours. Why: a\n  press with no response feels like the UI did not hear the person.\n- **Defaults carry the design; options are for the few.** Most people never change a setting, so\n  the defaults must already be the best the design has.\n- **A component's character is one personality.** A professional dashboard is crisp and dense, a\n  playful tool may be looser; a rule right in isolation reads wrong beside another character.\n- **A raised surface (overlay, popover) separates by a soft shadow, not a solid border.** A\n  semi-transparent shadow reads as depth; an opaque border reads as a box drawn around the content\n  (emilkowalski\u002Fskills README.md names a solid border over a shadow as an agent mistake). In a dark\n  theme an overlay also gets a 1 px low-alpha light edge, because a shadow vanishes on a dark\n  surface, and the edge is never opaque. A low-alpha separator on a card is decorative: WCAG 1.4.11\n  applies to the boundaries of controls and inputs, so the 3:1 rule is for those.\n- **A wait shows feedback by its length.** No busy indicator under 150 to 300 ms, because a\n  flash reads as a glitch (Vercel guidelines README: 150 to 300 ms, and once shown 300 to 500 ms);\n  over 1 s always feedback; a progress bar with a count past about 10 s when the length is known.\n  The 1 s and 10 s limits are the owner's decision. The families write the form.\n- **Handle edge cases where nobody looks.** A hover that must survive the gap between stacked\n  items, a timer that pauses when the view is hidden, a drag that continues outside its box.\n- **Targets carry a floor.** 44 px on touch (Vercel web-interface-guidelines README); 24 px is\n  the WCAG 2.5.8 floor, labelled as such. The source records any override per project with its\n  reason, because a threshold silently changed is a regression nobody can find.\n- **One primary action per surface.** Secondary actions are visibly subordinate and a destructive\n  one is separated and named as such. Why: when two things shout, the user has to decide what\n  the design should have decided.\n- **Colour is never the only carrier of meaning.** Each status token comes with a word, glyph or\n  shape (error is red and says what failed).\n- **An icon stands alone only where everyone reads it the same** (close, play, volume), and then\n  it has a tooltip and an accessible name; otherwise the control is a text label. Never icon and\n  label on one button, because the pair says one thing twice and costs width.\n- **A number comes from a named source.** Before choosing a colour, size, offset or duration, name\n  the token, reference file or mockup it comes from. With none, show two candidates live and wait\n  for the owner's pick; never tune a value from geometry alone, because the owner then supplies\n  the number anyway.\n- **Pastel or alive is a target, not an adjective.** Give each role a chroma and lightness range\n  (OKLCH) and check each accent is visible on the surface it sits on. Grey or dull is a finding,\n  and a role never shown is one too.\n- **Repeated list items are separated by one named device**: a gap, a hairline, or a surface step\n  (own body, a slight shadow allowed). A shadow alone is not a separator, and adjacent items\n  differ at rest.\n- **A token or colour pass changes values only.** List every visible element (separators,\n  handles, glass edge, readouts, layout) before and after and confirm each survives.\n- **The owner's chat ruling beats an older source line, and the source changes by principle.**\n  Edit the line in place in the same change and quote the owner; an overruled line is out of date,\n  not authority. Trace a complaint to the principle it broke and change the token that carries it\n  (\"the sidebar warning is too loud\" breaks \"a status colour marks a state, never a region\", so\n  `warning` changes, not a sidebar exception), because a line per complaint stacks.\n- **Prefer the platform's control to a custom one**, unless the source says why not. The system\n  one brings keyboard, focus, scaling and screen reader behaviour for free.\n- **A style is a constraint set, never a name.** Write what the look requires (for example \"raised\n  surfaces separate by a soft shadow, never an opaque border\"), the accessibility it brings, and\n  where it must not be used (dense data, small text, high-contrast users). Why: a named fad such as\n  \"glass\" says nothing the audit can measure; a constraint can fail a pair.\n\n## Output\n\nWrite `design\u002FMASTER.md` (and a page file only when a surface differs). When no file can be written,\ngive the same content in the reply. Keep it short: tokens in a table, not prose. Mark each threshold\nas default or override. Close with `## Requirements`, then tell the person what to do next: build\nwith the stack skill, then run ui-audit against this file, which is the expected column.\n\n## Red flags\n\n- When you reach for a hex literal in a component description, name a token instead, because the\n  literal is invisible to the audit and to the next theme.\n- When the draft names a framework, a stack's property or component type, move it to the stack\n  skill, because the source must survive a change of stack.\n- When you are about to list palettes, font pairings, or \"styles for SaaS\", stop and write the\n  token roles and constraints, because the person picks the look and the source holds its rules.\n\n## Say it in the reply\n\n- The path of the design source written, and which parts are defaults versus the person's choices.\n- The contrast ratio per pair and theme, computed, with the tool or formula used.\n- What was assumed, what was asked, and the open decisions left for the person.\n- What is not covered: no running UI was measured, so nothing is verified until ui-audit runs.\n\nHow each rule is built and exposed on a stack is its family: desktop (desktop-ui, qml-ui),\nterminal (cli-ui, tui-ui), web (css-ui, react-ui, web-motion).\n",{"name":5,"description":7},"main","c385fc50aadaee7296445e049153ce0560a9c80c","plugins\u002Fqsm-uix\u002Fskills\u002Fui-design","https:\u002F\u002Fgithub.com\u002Fqsmark-labs\u002Fqsm-marketplace","https:\u002F\u002Fgithub.com\u002Fqsmark-labs","2026-11-13 18:31:51",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add qsmark-labs\u002Fqsm-marketplace --skill ui-design",{"tool":36,"command":37},"bunx","bunx skills add qsmark-labs\u002Fqsm-marketplace --skill ui-design",{"tool":39,"command":40},"pnpm","pnpm dlx skills add qsmark-labs\u002Fqsm-marketplace --skill ui-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fqsmark-labs\u002Fqsm-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fqsm-uix\u002Fskills\u002Fui-design\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7EJWPJ0B4E1P148MWQ3GMR8","worktrunk","Use when working with git worktrees or wt (worktrunk): creating, switching, merging or removing a branch workspace, configuring wt (project or personal config, workflow hooks around switch, commit and merge, commit-message generation, hook approvals), or a wt command that failed. Triggers: make a worktree for this branch, wt merge, wt remove, configure wt, .config\u002Fwt.toml, run tests before merge, install deps when a worktree is created, wt hook, wt switch does not cd, nastav wt, wt nefunguje.","https:\u002F\u002Fgithub.com\u002Fqsmark-labs\u002Fqsm-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fqsm-worktrunk\u002Fskills\u002Fworktrunk\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7EJWD4F683TF21N89JGWZB2","web-ladder","Use when a task needs something the internet holds: look something up, search the web, find which page answers a question, read a page, check a library's current docs, a page that needs a browser or shows a captcha. Runs one research loop: searxng search, keywords, cases, search again up to three times, Context7 for a library, Tavily when the keywords will not come, one page in a browser, the person on a wall. Triggers: look this up, search the web, find out online, read this page, check the docs, the page is blocked, captcha, najdi na webu, otevri tu stranku. A multi-round question goes to the qsm-web:web-research agent; one tool's commands are its own skill (searxng, browserbox, opensrc).","https:\u002F\u002Fgithub.com\u002Fqsmark-labs\u002Fqsm-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fqsm-web\u002Fskills\u002Fweb-ladder\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7EJW9G0K6AS5Z4H0B0K6NDB","searxng","Use when running a web search through the person's own SearXNG instance with qsm-web searxng: choosing a search profile or engines, the instance, time range or language, reading its JSON, a suspended engine. Triggers: search with searxng, qsm-web searxng, search profile, niche search, academic search, IT search, vyhledavaci profil, searxng is down, which engines. The research loop around it is the web-ladder skill.","https:\u002F\u002Fgithub.com\u002Fqsmark-labs\u002Fqsm-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fqsm-web\u002Fskills\u002Fsearxng\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7EJW40RD3DRBQVVCW6K7NMG","opensrc","Use when the source code of an open-source library or repository is needed on disk to read: the docs are silent, the behaviour must be checked in code, the version the project pins. Runs qsm-web opensrc get with a package spec or a repository address. Triggers: get the source of this package, clone this library, read the library's code, qsm-web opensrc, stahni zdrojak knihovny. Library docs are the Context7 skill; the research loop is the web-ladder skill.","https:\u002F\u002Fgithub.com\u002Fqsmark-labs\u002Fqsm-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fqsm-web\u002Fskills\u002Fopensrc\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":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7EJVZWD6J7W91G69GMBWBQS","browserbox","Use when one page needs a real browser through qsm-web browserbox: content built by script, a page that blocks plain fetching, a captcha to solve or hand to the person, a scripted sequence of clicks, a login the person is present for. Triggers: open it in a browser, the page is empty without JavaScript, captcha, take over the browser, run these steps on the page, log in to this site, browserbox. When to reach for a browser at all is the web-ladder skill.","https:\u002F\u002Fgithub.com\u002Fqsmark-labs\u002Fqsm-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fqsm-web\u002Fskills\u002Fbrowserbox\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7EJVSZC1E8ZGVE8KXVFPR9S","usage","Use when the user wants a review of how they use Claude Code, or setup hands over after a first install: review my Claude Code usage, audit my setup, what does my setup cost, where did my tokens go, clean up my Claude Code, usage report, zkontroluj moje pouzivani. One walkthrough of four stages (machine, work, habits, extensions), questions after each, then one plan. A question about one topic (which hooks are slow) goes to that topic's skill; this session's tokens alone is `\u002Fqsm-usage`.","https:\u002F\u002Fgithub.com\u002Fqsmark-labs\u002Fqsm-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fqsm-usage\u002Fskills\u002Fusage\u002FSKILL.md",[],[]]