Loading...
Loading...
Found 10 Skills
Weekly analytics report combining GA4, Google Search Console, and Microsoft Clarity into a premium HTML email. Use for automated Sunday cron jobs that generate weekly product analytics reports. Tracks users, sessions, pageviews, SEO performance (queries, impressions, CTR, position), UX friction (dead clicks, rage clicks, quickbacks), and week-over-week trends. Includes accountability tracking (did we do what we said?), prioritized recommendations with impact/effort ratings, and actionable checklists. Persona: $15K/month SEO consultant. Outputs: HTML email + chat summary.
Automatic generation system for A-share daily briefings. It crawls real-time data from East Money and generates daily reports covering complete information such as market indices, popular sectors, and capital trends.
Automated penetration testing toolkit for security assessment, vulnerability scanning, and automated security reporting
Generate a concise 4-5 page equity research earnings preview for a single company. Analyzes the most recent earnings transcript, competitor landscape, valuation, and recent news to produce a professional HTML report.
Generate a pre-earnings briefing for any stock using Yahoo Finance data. Use this skill whenever the user wants to prepare for an upcoming earnings report, understand what analysts expect, review a company's beat/miss track record, or get a quick overview before an earnings call. Triggers include: "earnings preview for AAPL", "what to expect from TSLA earnings", "MSFT reports next week", "earnings preview", "pre-earnings analysis", "what are analysts expecting for NVDA", "earnings estimates for", "will GOOGL beat earnings", "earnings beat/miss history", "upcoming earnings", "before earnings", "earnings setup", "consensus estimates", "earnings whisper", "EPS expectations", "what's the street expecting", "earnings season preview", any mention of preparing for or previewing an earnings report, or any request to understand expectations ahead of a company's earnings date. Always use this skill when the user mentions a ticker in context of upcoming earnings, even if they don't say "preview" explicitly.
A-share Individual Stock In-depth Research System. When users mention phrases like "Analyze XXX stock", "Check XXX", "Research XXX", "Is XXX worth buying?", "How is XXX?", "XXX fundamentals", or directly provide a 6-digit A-share stock code (starting with 000/001/002/300/301/600/601/603/605/688), a three-phase process is automatically triggered: Phase 1 Data Collection (K-line/Financials/Shareholders) → Phase 2 Step 0-8 In-depth Analysis (Industrial Chain/Elasticity/Valuation/Risk-Reward Ratio/Stop-loss Signal) → Phase 3 Handwritten HTML Research Report. The generated results are data.json + report.md + report.html under output/<Stock Name>_<Code>/<YYYY-MM-DD>/. This tool is for research reference only, does not constitute securities investment consulting business, and does not constitute investment advice.
彙整今日中國宏觀經濟新聞消息，從華爾街日報、36氪等來源抓取並篩選宏觀相關新聞，輸出雜誌風格的新聞摘要。適用於交易/研究開盤前快速掌握中國宏觀動態。
Generate a periodic knowledge digest — a human-readable newsletter-style summary of what was learned, updated, and connected in your wiki over a specified period (day/week/month). Use when the user says "what did I learn this week", "give me a digest", "weekly summary", "knowledge report", "what's new in my wiki", "/wiki-digest [period]", "summarize my recent learning", or wants a readable overview of recent wiki activity. Distinct from wiki-status (which reports ingestion delta of sources) — wiki-digest summarizes *knowledge*, not sources.
Generates the Data Engineering team weekly/sprint status report from Azure DevOps. Organized by Epic, with objectives, on/off track status, risks, completed and planned items per area, clickable ADO links, and unplanned items flagged. Use when the user asks for a Data Engineering sprint report, weekly report, current sprint status, activities report, or sprint summary.
Read-only GitHub triage for issues AND PRs. 1 item = 1 background task (category: quick). Analyzes all open items and writes evidence-backed reports to /tmp/{datetime}/. Every claim requires a GitHub permalink as proof. NEVER takes any action on GitHub - no comments, no merges, no closes, no labels. Reports only. Triggers: 'triage', 'triage issues', 'triage PRs', 'github triage'.