Loading...
Loading...
Found 202 Skills
Builds trade area and catchment analysis workflows in CARTO. Triggers when the user mentions trade area, catchment area, isochrone, site selection, where to open, best location, billboard, OOH, audience targeting, drive time, walk time, coverage area, commercial hotspot, site scoring, location ranking, or wants to generate isochrones, score candidate locations, or identify the best sites for retail, advertising, or services.
Use when doing upstream market-research methodology — sizing a market as TAM/SAM/SOM computed BOTH top-down and bottoms-up (never a single unsourced number), planning a survey sample size with finite-population correction and per-segment minimums, or scoring candidate market segments against Kotler's measurable/substantial/accessible/differentiable/actionable criteria. Outputs always show the method and the assumptions. For market-research analysts and product-marketing at the sizing/survey/segmentation moment. Distinct from marketing-skill (campaign analytics, attribution, demand-gen) — this is the evidence-building methodology, not live-campaign optimization.
Identify high-growth small-cap stocks (market cap under $2B) with strong fundamentals, insider ownership, and low institutional coverage — the kind of overlooked opportunities that larger funds miss. Use when the user asks to find small-cap growth stocks, discover under-the-radar companies, screen for founder-led small caps, identify emerging growth companies, find low-institutional-ownership stocks, or seek multi-bagger candidates with strong fundamentals.
Track which stacks use a specific Pulumi package and at what versions, or upgrade a stack to the latest version of a package. Use when users ask about package version tracking, outdated package versions across stacks, upgrade candidates, or package usage audits. Also use when users want to upgrade/update a specific package version in a stack or project. Do NOT use for general infrastructure creation, resource provisioning, or questions about how to use a package.
Apply Porter's Value Chain Analysis to identify competitive advantage sources within an organization's activities. Use this skill when the user needs to find where value is created or lost in their operations, analyze cost structure by activity, optimize internal processes, or identify outsourcing candidates — even if they say 'where do we make money' or 'which activities should we keep in-house'.
Fundamental factor stock screening — filter value or growth stocks using PE, PB, ROE, revenue growth, net-profit growth, and dividend yield across A-share, HK, and US markets. Outputs a candidate table ranked by composite factor score. Triggers: "基本面筛选", "因子选股", "价值选股", "成长选股", "低PE选股", "高ROE", "股息筛选", "PE筛选", "PB筛选", "多条件选股", "基本面因子", "量化选股", "基本面篩選", "因子選股", "價值選股", "成長選股", "低PE選股", "股息篩選", "factor screening", "value screen", "growth screen", "low PE filter", "high ROE screen", "dividend screen", "fundamental factor", "multi-factor stock screen".
Investment idea generation — systematically surfaces new investment opportunities by combining quantitative screening (low valuation / high momentum / improving fundamentals), thematic research (sector trends / policy catalysts), and pattern recognition (historical analogues), producing a long/short candidate list. Triggers: "投资想法", "选股灵感", "投资机会", "找股票", "发掘机会", "多头机会", "空头机会", "主题投资", "投資想法", "選股靈感", "投資機會", "找股票", "多頭機會", "空頭機會", "主題投資", "investment ideas", "stock ideas", "investment opportunities", "idea generation", "long ideas", "short ideas", "thematic investing", "stock discovery", "find me stocks", "what should I buy".
Batch identify candidate stocks with mature breakout patterns, healthy volume-price structures, and good catalyst alignment, and output priorities, trigger conditions, and failure boundaries. Suitable for scenarios such as short-to-medium-term stock selection, pre-market candidate pool sorting, and screening leading candidate stocks in sector rotation.
Use this when the user wants to post a daily X/Twitter tweet inspired by one of their recently published WeChat Official Account articles. It selects the newest article that hasn't been tweeted yet, drafts 3 tweet candidates from it (from different angles — quote / metaphor / one-liner), posts the selected one via xurl, and records the action to history. Triggers — "Post a daily tweet", "Tweet from an article", "Today's tweet", "/wjs-tweeting-from-articles".
Orchestrate the release team: coordinates release-manager, qa-lead, devops-engineer, and producer to execute a release from candidate to deployment.
Given event_candidates YAML (output from discover-event-surfaces), generates a concrete instrumentation plan for priority-3 (critical) events. Acts as a Software Architect: discovers existing analytics patterns in the codebase, reads the hinted files to determine what variables are in scope, designs minimal chart-useful properties, and identifies the exact insertion point for each tracking call. Outputs a structured JSON trackingPlan. Use this as step 3 of the analytics instrumentation workflow, after discover-event-surfaces. Trigger whenever a user has event_candidates and wants to generate tracking code, asks "instrument these events", "generate tracking plan", "add analytics for these events", "where should I put the tracking calls", or any request to turn event candidates into concrete implementation guidance.
Interactively prune stale non-terminal workflows from the pipeline. Use when the user says 'prune workflows', 'clean stale workflows', 'pipeline cleanup', or runs /prune. Runs a dry-run preview, displays candidates with staleness and safeguard skips, prompts the user to proceed/abort/force, then bulk-cancels approved workflows with a workflow.pruned audit event. Safeguards skip workflows with open PRs or recent commits unless force is set.