14 skills · sorted by relevance
Review prediction-market and trading-agent workflows before they handle account access, portfolio data, or trade planning. Produces structured findings on venue rules, data quality, security, privacy, and execution risks, with required safeguards and a safe next step.
Browse Itô baskets, collections of prediction-market items, and organize market data with sources and timestamps. Compare baskets with selected research or watchlists, prepare market briefs, or draft planning worksheets for manual review without investment advice or trading.
Create an HTML policy briefing deck about expanding urban tree canopy for city councils and agency reviewers. Organize public needs, evidence, policy options, and funding decisions within a consistent forest-green and cream presentation template.
Build an HTML briefing deck that organizes workplace-safety findings, supporting evidence, and corrective requirements for regulators and plant leaders. A paper-textured design with earth tones gives the slides a consistent visual style for decision discussions.
Build an HTML presentation for a public-transit funding proposal, covering ridership needs, the plan, risk controls, and the requested decision. The template uses bold poster-style colors and typography for city councils and public boards.
Create HTML slides for a hospital board or regulators, explaining patient-data risks, safeguards, responsibilities, and required approvals. The skill uses a fixed presentation template with speaker notes to organize evidence and support a clear decision.
Prepare a briefing on one litigation matter using its records and event history. Summarize recent changes, deadlines, financial exposure, and open questions, with prompts to reconsider recorded risk ratings before a meeting or update.
Use when the user asks what they are not seeing, what they forgot, what could go wrong, or what an expert would say about a plan, decision, document, code change, or setup they already have. Triggers: "what am I missing", "what don't I know", "poke holes in this", "what would an expert ask", "что я упускаю", "что я не вижу", or /clueless-blindspots. One-shot review; does not change the always-on level.
The English summary is being prepared. Showing the original description.
Review a feature or PRD for stakeholder and political risk before broad circulation.
The English summary is being prepared. Showing the original description.
Draft commercial contracts from scratch by contract type — NDAs, service agreements, vendor contracts, employment agreements, and licensing deals. Follow a clause library approach with risk-balanced terms. Use when creating new contracts. Do not replace legal counsel sign-off on finalized agreements. For reviewing existing contracts, use contract-risk-review instead.
The English summary is being prepared. Showing the original description.
Review commercial contracts, NDAs, MSAs, SOWs, and vendor agreements for obligation clarity, risk allocation, termination, data handling, and negotiation red flags. Use when a user needs a structured contract summary, red flag list, fallback positions, or clause-by-clause review. Do not use as jurisdiction-specific legal advice, litigation strategy, or final legal sign-off.
The English summary is being prepared. Showing the original description.
Identify, score, and mitigate delivery risks for a program or release. Use when the user says "risk review", "what could go wrong", "risk register", "delivery risks for this release", "program risk assessment", "identify blockers before they hit", or wants to pressure-test a plan before committing - even if they don't say "risk review". Based on "The Phoenix Project" by Kim, Behr & Spafford (unplanned work, fragile systems, single points of failure) and "The Art of Project Management" by Scott Berkun (scoping risk, milestone pressure, hidden assumptions).
The English summary is being prepared. Showing the original description.
Assess package choices and generated dependency names, publisher or release anomalies, incident exposure, and changes in package risk reports. Use before trusting a new dependency, when a release changes unexpectedly, or when investigating a supply-chain alert.
The English summary is being prepared. Showing the original description.
Reviews one deal's notes and timeline (CRM opportunity record, activity log, emails, meeting notes, forecast entries) for risk signals such as a single contact thread, no identified budget owner, slipped or missing dates, silence after a proposal, an undefined decision process or a competitor named late, and returns a DRAFT risk register: each signal with the quoted evidence and its date, a severity on a stated scale, and one proposed next action with an owner role for the user to decide on. Use when the user asks to "review the risks on this deal", "why is this opportunity stalling", "is this deal single-threaded", "deal health check before the forecast call" or "what should we do next on <opportunity>". Do not use for a whole-account plan, use account-plan-builder instead; for scoring early leads against a rubric use lead-qualification-scorer. Drafts for human review; never approves, authorises or signs off.
The English summary is being prepared. Showing the original description.