Loading...
Loading...
Found 3,723 Skills
Bright Security integration. Manage data, records, and automate workflows. Use when the user wants to interact with Bright Security data.
This skill should be used when the user asks to forecast aggregate sentiment and opinion dynamics over time—sentiment indices from text streams; temporal rollups; leading/lagging KPI links; time-series and sequence models (ARIMA, Prophet, state-space, ML); nowcasting; spikes, bots, and bias; walk-forward backtests; intervals and scenarios; volume/velocity/topic features; BI or brand dashboards. Triggers: sentiment forecasting, forecast sentiment, sentiment index, opinion trend forecast, social sentiment time series, brand sentiment trajectory, nowcast sentiment, sentiment leading indicator, aggregate polarity forecast, sentiment backtest, walk-forward sentiment, sentiment spike prediction. Not for per-text labeling (sentiment-analysis-engineer), demand forecasting without sentiment (predictive-logistics-developer, data-scientist), trade advice (methodology only), marketing copy (content-creator), macro without text sentiment (financial-analyst partial).
Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services. Use for CLI UX checks, startup regressions, memory leaks, hangs, prompt flows, or terminal demos.
Plans real-user QA deliverables: personas, journey maps, exploratory charters, persona/journey/tour/CFR test cases, regression suites, Figma validation checks, automation intent, and user-impact bug reports. Writes artifacts under <qa-output-path>/qa/ for qa-execution to consume. Use when planning QA before execution, documenting journey-driven test strategy, marking flows that need E2E follow-up, or filing structured bug reports. Do not use for live execution, AI implementation audits, CI gate ownership, or technical integration/security/performance suites; use qa-execution or agent-output-audit instead.
Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.
Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.
Use when planning A/B tests in LaunchDarkly, Optimizely, or similar platforms. Sizes the experiment (sample size, MDE, runtime), drafts hypothesis + success metrics + guardrails, and produces a launch checklist + rollback plan.
Applies multi-disciplinary cognitive frameworks (e.g., Inversion, First Principles, Second-Order Thinking) to user plans and system designs to stress-test decisions.
Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'
RQAlpha 米筐开源事件驱动回测框架。支持A股和期货，模块化架构，可自由扩展；当用户需要使用 rqalpha 进行策略回测、模拟交易或Mod插件开发时使用。
The meta skill. Turn any raw feature into a properly-skilled, tested, resolvable unit of agent capability. Cross-modal eval is the recommended Phase 3 quality gate: 3 frontier models from different providers critique the output, you iterate to quality, THEN write tests that lock in the proven-good behavior.
Use when developing or validating Elastic integrations with elastic-package commands such as build, check, lint, format, test, stack, service, install, profiles, and benchmark.