Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Create, modify, and remove feature flags in RedisInsight. Use when adding a new feature flag, introducing a dev flag, promoting a dev flag to regular, cleaning up old flags, or the user mentions feature flags, feature toggles, or gating features.
React/Redux frontend development patterns for RedisInsight UI: component folder structure, styled-components, hooks, named exports, barrel files, layout components, and theme usage. Use when editing any file under redisinsight/ui/**, writing or modifying React components, Redux slices, styled-components, custom hooks, or when the user mentions UI, frontend, React, Redux, or styled-components.
Critical safety guardrails for protected branches: never commit, push, or force-push directly to main, latest, or release branches; no destructive history rewrites without explicit user approval. Use before any git operation that touches protected branches, before force-push, reset --hard, history rewrite, or branch deletion, or whenever the user asks about merging, pushing, or release branches.
Internationalization conventions for the RedisInsight UI (i18next). Use when adding or changing user-facing strings under redisinsight/ui/**, editing the locale files (en.json/bg.json), translating API errors or notifications, or when the user mentions i18n, translations, locales, i18next, or <Trans>.
Use when creating, modifying, debugging, deploying, or testing Redis Insight Workbench visualization plugins, plugin manifests, package.json visualizations, activationMethod functions, redisinsight-plugin-sdk usage, Parcel/Vite plugin builds, iframe rendering, Redis command parsing, Docker RedisInsight deployment, /api/plugins verification, or Playwright plugin validation.
Run, refresh, or recover from RedisInsight's per-project TypeScript error baselines (.tscheck.rec.json). Use when CI reports "baseline is outdated" or "more TS errors than previously recorded", when the user mentions tscheck / type-check / .tscheck.rec.json, when introducing or fixing TS errors, or when reviewing PRs that touch baseline files.
A skill to calculate grocery prices with country-specific taxes.
Research why the TypeScript team made a specific typing decision. Use when evaluating whether ts-reset should override a built-in type, or when triaging issues that propose type changes. Searches the microsoft/TypeScript repo for relevant issues, PRs, and team comments.
A股个股次日(T+1)走势预测 skill。当用户输入A股股票代码(如 600519、000858、300750、688981、430090)或公司名称(如"贵州茅台"、"宁德时代"、"比亚迪"),并要求预测次日走势、给出交易计划、评估盈亏概率时,触发本 skill。skill 会用 mcp__MiniMax__web_search 搜证大盘环境、龙虎榜、北向资金、融资融券、主力资金流、板块联动、公告与消息面等,按"四维分析框架"(大盘环境 30% / 资金行为 30% / 技术面 25% / 消息面 15%)交叉验证,产出可量化的方向预测(看多/看空/震荡 + 概率百分比 + 价格区间),并写入当前项目 markdown 目录下的 `a-stock-{代码}-{YYYY-MM-DD}.md`。输出包含详细逻辑推导链、中间结果与最终结果概率、专业术语小白解释、mermaid/ascii/svg 图表。适用场景:盘后复盘想做次日的方向判断与交易计划;不适用:长线基本面估值(改用 finance-core-analysis)、日内高频交易、港股/美股(改用 us-stock-prediction)。
预测A股个股次日走势，输出图文并茂的 Markdown 分析报告（含详细逻辑推导、中间结果、概率量化与操作建议），面向散户与专业投资者均适用。触发条件：用户输入A股股票名称或代码（6位数字，如600519、000858），并希望获得次日走势预测；关键词包括"预测明天走势"、"明天能涨吗"、"A股分析"、"帮我分析XX股票"、"明天该买吗"、"次日预测"、"做T建议"、"短线操作"、"明日行情"、"值得持有吗"、"止盈止损怎么设"等。即使用户只说"帮我看看贵州茅台明天怎么走"或"600519明天能不能买"，也应使用本 skill。输出 Markdown 文件保存到当前项目 markdown/ 目录，要求逻辑清晰、概率可量化、图文并茂，投资小白也能看懂。