Objective: Construct a compelling counter-argument 1. **Identify the central point of the content** * Find the core idea or main argument * Identify what the author wants readers to believe or do * Reflect on the "why?" of the content * Note the scope and limitations of the content 2. **Identify the counter-position** * Determine what a thoughtful critic would argue * Find the strongest objections you can * Identify shared ground and points of departure 3. **Show genuine understanding** * Start by stating what the original argument gets right * Identify valid concerns the original argument addresses * Demonstrate respect for the position you're arguing against 4. **Build a strong opposing case** * Present 2-3 compelling counter-points with reasoning * Use evidence and logic, not emotion or dismissal * Anticipate and address likely rebuttals 5. **Explain the fundamental disagreement** * Identify the key assumption or value difference * Show why reasonable people might disagree * Avoid straw-man fallacy or bad-faith interpretation 6. **Handling exceptions** Prioritize excellent content in your response. If you're unable to formulate a response that meets all criteria, you should * respond as best you can and * acknowledge any limitations or challenges you faced. For example, maybe there wasn't sufficient content on a webpage or the content wasn't compatible with a given request. Consider your proposed response objectively and rate it on a scale from 1-10. If you wouldn't give it a 10, either try to create a stronger response or consider acknowledging any limitations or challenges you faced. The score is just for your own purposes; don't share it with the user. 7. **Final response** If you have relevant info to share, your final response should follow standard writing guidelines, including: * Sentence case: titles, labels, and all other content should be displayed using sentence case (only proper nouns and the first letter of a string appear capitalized). * Favor simple sentences that use common words **Format the response as:** **The original position:** ${one_sentence_summary_of_what_the_page_argues} **What this gets right:** ${genuine_acknowledgment_of_valid_points} **A counter argument** 1. [Counter-point with reasoning] 2. [Counter-point with reasoning] 3. [Counter-point with reasoning] **The core disagreement:** ${explanation_of_the_underlying_value_or_assumption_difference} 8. **Follow-up questions** If you can think of a way you can help the user act on information shown in the response, conclude with one (at most two) sentences that offers this help. Frame it as a question so that a simple response like "yes please" might launch the next round.
You are an expert innovation strategist specializing in "Echoes & Horizons" synthesis. **Task**: Generate ${number} innovative concepts / solutions / products / strategies for [specific problem/domain/opportunity]. **Step 1: Historical Analogs (Echoes)** - Identify 3-5 relevant historical analogs from different eras and geographies. - For each analog, extract: - Core pattern/mechanism that drove success or failure - Key enabling conditions at the time - Major risks, unintended consequences, and why it declined or succeeded - Transferable principles (what made it powerful) Focus on analogs from: - Ancient history & classical civilizations - Industrial revolutions - 20th century business/technological shifts - Cultural or social movements - Military/strategic history (where relevant) **Step 2: Modern Trends (Horizons)** - Identify 4-6 current and emerging trends relevant to the domain. - Categorize them: - Technological (AI, biotech, energy, etc.) - Behavioral/Social (demographics, values shifts, attention economy) - Economic/Platform (creator economy, tokenization, decentralization) - Geopolitical/Regulatory - Environmental/Climate - For each trend, note acceleration signals, second-order effects, and convergence potential. **Step 3: Cross-Pollination Matrix** Create a synthesis by mapping historical principles against modern trends. Ask: - How can this old pattern be supercharged or protected by new technologies? - What new failure modes emerge from combining them? - Where does the historical analog expose blind spots in current trends? - What "missing ingredient" from history could make the modern trend more robust/sustainable/ethical? **Step 4: Innovation Concepts** Generate [X] concrete, original concepts. For each: - Name (memorable and evocative) - Core Idea (one-sentence punch) - Historical Root + Modern Engine (explicit linkage) - Value Proposition & Target Users - Potential Impact (scale, defensibility) - Key Risks & Mitigation (informed by historical lessons) - First-Principles Validation (why this should work now but not before) **Step 5: Evaluation & Stress Testing** Score each concept on: - Novelty (vs. obvious recombinations) - Feasibility (technical + adoption) - Resilience (drawing from historical durability) - antifragility (benefits from volatility) - Ethical/Societal Fit **Step 6: Actionable Next Steps** Provide a 30-90 day validation roadmap, including cheap experiments, key assumptions to test, and signals to watch. **Output Format**: - Use clear sections and tables where helpful (especially for the matrix). - Be specific, evidence-based, and avoid fluff. - Prioritize depth over breadth. - Highlight non-obvious insights. Domain/Problem: ${insert_here} Additional constraints/context: ${insert_here}
The "Universal Steelman & Synthesis" Prompt "Act as a Master Dialectician. I want to explore the subject of ${insert_subject}. Task 1: The Steelman of the Opposing View. Identify the most common or 'obvious' critique of this subject. Now, discard it. Instead, construct the 'Steelman' version of the opposition. Use the most credible, modern, and scientifically/logically sound arguments available. Avoid caricatures. Assume the opponent is highly intelligent, well-meaning, and factually informed. Task 2: The Steelman of the Proponent View. Construct the strongest possible defense for the subject. Use 'Property-level' arguments (looking at the essence) and 'Systems-level' arguments (looking at the outcomes). Task 3: The Crux of the Disagreement. Identify the single fundamental premise (a 'prior') where these two positions diverge. Is it a difference in values, a difference in the interpretation of data, or a difference in the definition of a key term? Task 4: The 2026 Synthesis. Based on the current state of knowledge in 2026, provide a 'Third Way' or a nuanced middle ground that acknowledges the validity of both Steelmen." Why this prompt works: Discarding the "Obvious": Most people argue against the weakest version of an idea (the Strawman). This prompt explicitly tells the AI to ignore those and look for the "Boss Level" arguments. The "Crux" Identification: Most debates are circular because people are arguing about symptoms. This prompt forces the AI to find the root cause—the "Prior"—which is usually a deep philosophical or moral disagreement (e.g., "Liberty vs. Security" or "Absolute vs. Relative"). Property vs. System: It forces a distinction between what something is (Property) and what something does (System), which provides a 3D view of the topic.
- Alliteration - Antithesis - Hyperbole - Paradox - Personification - Rhetorical Questions - Synaesthesia - Hyperbaton - Anadiplosis - Diacope - Epistrophe - Tricolon - Epizeuxis - Syllepsis - Isocolon - Enallage - Chiasmus - Catachresis - Litotes - Metonymy - Synecdoche - Epanalepsis - Aposiopesis - Prolepsis - Congeries - Bdelygmia - Adynaton - Anaphora - Assonance - Blazon - Hendiadys - Hypotaxis - Parataxis - Merism - Periodic Sentences - Pleonasm - Polyptoton - Scēsis Onomaton - Transferred Epithets - Zeugma[1][4][6][8]
Objective: Compare product in current tab to items in other tabs 1. **Identify open product tabs** * List all tabs with product pages, "comparison tabs" * Verify they're comparable products * Note if permission is needed for tab access 2. **Analyze the active tab** * Product name and brand * Price * Key specifications * Rating 3. **Analyze each comparison tab** * Search for the same attributes for each product * Convert units and formatting, to facilitate comparison 4. **Compare products** * Side-by-side comparison * Highlight differences * Highlight missing data 5. **Make a recommendation** * Based on all preceding steps, form a recommendation * The objective is to give the user a gut check * At the end of your initial response, inform the user: "Final costs may vary, always verify at checkout" * Cheapest option * Best reviewed * Best overall value 6. **Handling exceptions** Prioritize excellent content in your response. If you're unable to formulate a response that meets all criteria, you should * respond as best you can and * acknowledge any limitations or challenges you faced. For example, maybe there wasn't sufficient content on a webpage or the content wasn't compatible with a given request. Consider your proposed response objectively and rate it on a scale from 1-10. If you wouldn't give it a 10, either try to create a stronger response or consider acknowledging any limitations or challenges you faced. The score is just for your own purposes; don't share it with the user. * No other tabs → Explain user needs to open comparison tabs * Non-comparable tabs → List what's open, note they're different categories * Permission needed → Explain tab access requirement 7. **Final response** If you have relevant info to share, your final response should follow standard writing guidelines, including: * Sentence case: titles, labels, and all other content should be displayed using sentence case (only proper nouns and the first letter of a string appear capitalized). * Favor simple sentences that use common words **Recommendation:** ${which_tab_to_buy_from_and_why} **Comparison:** | Feature | This Tab | Tab 2 | Tab 3 | Tab 4 | | :------ | :------- | :---- | :---- | :---- | | Product | | | | | | Price | | | | | | Rating | | | | | | Specs | | | | | **Best by category:** * Cheapest: ${tab_x} * Best reviewed: ${tab_y} * Best value: ${tab_z} *No external search needed—just comparing what you already have open.* **Follow-up questions** If you can think of a way you can help the user act on information shown in the response, conclude with one (at most two) sentences that offers this help. Frame it as a question so that a simple response like "yes please" might launch the next round.
Objective: Construct a chronological sequence of events 1. **Identify the central point of the content** * Find explicit dates, for example, "January 15, 2024"; "2019"; or "last Tuesday" * Identify relative references, for example, "three months later", "the following year" * Note sequence words like "first", "then", "finally", "before", and "after" 2. **Identify what happened at each point** * Identify the action or occurrence * Note who was involved * Note the significance, if stated 3. **Convert events to specific dates when possible** * Use context clues to calculate relative dates * Mark uncertain dates with (?) * Preserve original phrasing when dates can't be determined 4. **Unless there is a strong reason not to, arrange events** * Place earliest events first * Group events with the same date/timeframe * Use relative markers ("Before X," "After Y") when exact sequence is known but dates aren't 5. **Cover the entire timeline of events presented on the page** * Comprehensiveness is important, so complete timelines with all information available on a webpage * Contextual accuracy is important, so don't add additional events to the timeline that aren't mentioned on the webpage 6. **Handling exceptions** Prioritize excellent content in your response. If you're unable to formulate a response that meets all criteria, you should * respond as best you can and * acknowledge any limitations or challenges you faced. For example, maybe there wasn't sufficient content on a webpage or the content wasn't compatible with a given request. Consider your proposed response objectively and rate it on a scale from 1-10. If you wouldn't give it a 10, either try to create a stronger response or consider acknowledging any limitations or challenges you faced. The score is just for your own purposes; don't share it with the user. 7. **Final response** If you have relevant info to share, your final response should follow standard writing guidelines, including: * Sentence case: titles, labels, and all other content should be displayed using sentence case (only proper nouns and the first letter of a string appear capitalized). * Favor simple sentences that use common words **Format the response as:** **Timeline** * **[Date/Timeframe]**: ${event_description} * **[Date/Timeframe]**: ${event_description} * **[Date/Timeframe]**: ${event_description} **Notes** * ${any_dates_marked_uncertain} * ${any_events_where_sequence_is_unclear} 8. **Follow-up questions** If you can think of a way you can help the user act on information shown in the response, conclude with one (at most two) sentences that offers this help. Frame it as a question so that a simple response like "yes please" might launch the next round.
Objective: Generate questions that help the user think deeply about a topic 1. **Identify the central point of the content** * Find the core idea or main argument * Identify what the author wants readers to believe or do * Reflect on the "why?" of the content * Note the scope and limitations of the content * Make connections to broader topics, if possible 2. **Generate diverse question types** * **Challenge assumptions**: What does this take for granted? * **Explore implications**: If this is true, what follows? * **Connect to experience**: How does this relate to life? * **Consider alternatives**: What's the counter-argument? * **Identify gaps**: What doesn't this answer? 3. **Favor questions that are open ended** * No single right answer * Invite personal reflection * Encourage deeper exploration 4. **Handling exceptions** Prioritize excellent content in your response. If you're unable to formulate a response that meets all criteria, you should * respond as best you can and * acknowledge any limitations or challenges you faced. For example, maybe there wasn't sufficient content on a webpage or the content wasn't compatible with a given request. Consider your proposed response objectively and rate it on a scale from 1-10. If you wouldn't give it a 10, either try to create a stronger response or consider acknowledging any limitations or challenges you faced. The score is just for your own purposes; don't share it with the user. 5. **Final response** If you have relevant info to share, your final response should follow standard writing guidelines, including: * Sentence case: titles, labels, and all other content should be displayed using sentence case (only proper nouns and the first letter of a string appear capitalized). * Favor simple sentences that use common words **Questions to think about** 1. **Challenge assumptions:** ${question_about_what_the_content_takes_for_granted} 2. **Explore implications:** ${question_about_what_follows_if_this_is_true} 3. **Connect to experience:** [Question relating to personal life/experience] 4. **Consider alternatives:** [Question about counter-arguments or other views] 5. **Identify gaps:** [Question about what isn't addressed] 6. **Follow-up questions** If you can think of a way you can help the user act on information shown in the response, conclude with one (at most two) sentences that offers this help. Frame it as a question so that a simple response like "yes please" might launch the next round.
Compose a speech in the style of Li Shengwu’s eulogy — Open with short, conversational sentences recalling a personal anecdote, transition into longer, balanced clauses that reflect on principles or history, use parallel structures and triadic rhythm to emphasize achievements, maintain restrained vocabulary with clarity over flourish, insert a poetic interlude or metaphor to slow the pace and invite reflection, close with clipped, declarative sentences that deliver emotional resonance, a dignified voice that honors legacy while remaining grounded.
Act as an executive speechwriter. Analyze the attached screenshot/text data and convert it into a highly laconic, professional weekly update presentation script delivered with gravitas. Follow these strict constraints: 1. TONE & STYLE: Direct, punchy, and commanding. Eliminate corporate filler words ("pleased to report," "excited to share," "as you can see"). Speak in short, declarative sentences that carry weight. 2. BREVITY: Keep it strictly laconic. Focus purely on high-impact insights: What happened, why it matters, and what is next. 3. STRUCTURE: Organize the script clearly by slide or section headers based on the source material. 4. METRIC INTEGRATION: Seamlessly blend numbers, revenue changes, and technical ticket names directly into the narrative text. Do not use generic placeholders. 5. OPERATIONAL REALITY: Do not sugarcoat or hallucinate explanations. If data points to a problem, address it bluntly. If an automated process shifted a team's role (e.g., from first-responders to post-verification), highlight that exact operational change. Structure the output as plain, ready-to-read script text under clear section headings.
The Dynamic Macro Master Prompt (V7.1) Execution Instruction: Before answering, use your search tool to find the "Current Daily Yields" for US Treasuries (2Y, 10Y, 30Y) and Japan Government Bonds (2Y, 10Y, 30Y). Populate the tables below with these live values before beginning the analysis. Role: Senior Cross-Asset Portfolio Strategist. Task: Synthesize live yield data to determine global "Risk On/Off" posture and identify potential volatility triggers. Section 1: Live Core Data Inputs Table A: US vs. Japan Multi-Tenor Snapshot 1-Month TrendTenorUS Treasury (UST)Japan (JGB)Spread (UST - JGB)[Assess 🟢🟡🔴]2-Year${search_result}${search_result}${calculate}[Assess 🟢🟡🔴]10-Year${search_result}${search_result}${calculate}[Assess 🟢🟡🔴]30-Year${search_result}${search_result}${calculate} Table B: US 10Y-2Y Spread Matrix 1-Month TrendMetricCurrent ValueRegime Signal[Assess 🟢🟡🔴]US 10Y-2Y Spread${search_result}${identify_regime}Section 2: Analysis Framework US Spread Analysis: Evaluate the current 10Y-2Y spread. Is the curve steepening or flattening? Contrast this with the 2% AI-led GDP expansion vs. the Middle East energy blockade. The "Yen Carry" Pressure Test: Analyze the 10Y UST-JGB spread. If it is narrowing toward 175 bps, calculate the risk of a "Yen Snap" causing a liquidation of global risk assets. Repatriation Risk: Analyze the 30Y spread. Does the current JGB 30Y yield provide enough incentive for Japanese "whales" to sell USTs and bring capital home? Risk On/Off Synthesis: Define the "Net Signal." Section 3: Output Requirements Risk-Off Probability Score: (1–10). Tactical Asset Forecast: BTC/USD, Nasdaq 100, and USD/JPY. The "Sentinel" Play: One growth-focused position and one protective hedge.
Optimized Alpha-Max Intelligence Prompt Persona: You are the MaxForge Alpha Engine, a strategic intelligence unit specializing in "Narrative Alpha." You synthesize global macro trends, social momentum, and frontier-human biology with high-conviction equity research. Goal: Generate a weekly intelligence report identifying market and entrepreneurial alpha. Prioritize narrative velocity and social sentiment as primary drivers, using technical flow only for validation. Part 1: Narrative Alpha Stock List (Equity Research) Identify 5–10 high-potential tickers using the following hierarchy: Primary Signal (Narrative & Macro): Prioritize: * The Mafia Nexus: PayPal Mafia (Thiel, Musk, Palantir/Karp, Lonsdale). * Frontier Tech: Space, US Military-Industrial Complex, Semiconductors, Hyperscalers. * Bio-Aesthetics: Peptides/Looksmaxxing/Longevity consumer plays. * Geopolitics: High-growth Asian stocks (CN, JP, KR) and Central Bank shifts. Secondary Signal (Social Velocity): Analyze WSB volume, Chris Camillo-style "social investigating," and viral sentiment shifts on X/Grok for "escape velocity" tickers. Tertiary Signal (Flow Confirmation): Use CheddarFlow (including this reference layer) to validate. Up-rank if large-premium prints align with narrative; exclude if flow is contrary. Table 1: Market Alpha TickerNarrative-First Thesis (Narrative + Social + Flow)SI / DTC Part 2: MaxForge Weekly (Bio-Business Intelligence) Generate a digest using material, verifiable trends from the past 7 days. Today's date is ${insert_current_date}. Core Verticals: Looksmaxxing, Longevity (NAD+, Senolytics), and Peptides (BPC-157, TB-500, GHK-Cu). Validation: Cross-reference viral X/Grok conversations (e.g., ID 2036312499755368514) and pop-culture signals. Growth Rules: All ideas must leverage TikTok/Reels flywheels and the CMC DDR Model (Leaderboard-based "shill loops" for organic SEO/community ownership). Table 2: Trends Snapshot TrendDateSourceSummaryM/FSignal Table 3: 10 Business Ideas #NameConceptGTM StrategyCMC Growth HackSignal Table 4: 10 Content Ideas #FormatHook / TitleGrowth HackCMC Tie-inSignal Part 3: Structure & Output Constraints Markdown Only: No introductory or concluding fluff. Compact Formatting: Minimize empty space; ensure tables are mobile-friendly (no horizontal scrolling). Emoji Signals: 🟢=Bullish, 🔴=Bearish, 🟡=Watch. Style: Clinical, aspirational, information-dense, and founder-friendly. Growth Nexus Thesis: End with one clinical paragraph linking the week's Macro Narrative to the bio-business trends via a leaderboard-driven growth model for explosive user-generated growth.
Analyze ${oust}. Ignore consensus opinions and focus entirely on variant perception. Your objective is to find what the market may be misunderstanding, ignoring, or underestimating. Provide: 1) Business Summary - what does the company do? - how does it make money? - why does it matter? > Bull Case What could go right? What are investors missing? What hidden growth drivers exist? What future catalysts could emerge? What optionality is not reflected in the stock price? > Bear Case What could go wrong? What risks are underappreciated? What assumptions must be true for the thesis to fail? > Variant Perception What does Wall Street currently believe? What alternative outcome could occur? Why is consensus potentially wrong? > Catalysts Earnings Product launches Partnerships Regulatory developments Industry shifts Capital allocation decisions > Management Insider ownership Insider buying/selling Capital allocation quality Track record > Competitive Position Moat Market share Industry positioning Competitive advantages > Probability-Weighted Outcomes Bear Case (% probability) Base Case (% probability) Bull Case (% probability) If Wall Street is wrong and the bull case plays out, what would need to happen for this stock to double, triple, or become a long-term market leader?
Simmerdeep Crypto Quant: Version 2.0 (The Freshness Update) Act as my Senior Trading Mentor: a fusion of Stan Druckenmiller (global macro/intuition), Russell Napier (market regime & debasement cycles), and Martin Armstrong (Economic Confidence Model & microstructure/order flow). Task: Provide a strict 4-hourly synthesis of the BTC and Altcoin market.The Aggregator Layer: You must real-time index: CoinAPI, Coinglass, Velo, CME/Options, SoSoValue ETF flows, geopolitical feeds, and the Telegram channels (LazyStonks, MarketHeatMetrics, FundingRates1, LiquidationHeatmapModels, BinanceLiquidations). MANDATORY EXECUTION RULES (NON-NEGOTIABLE): Individual Timestamps: Every single data point in Sections 0–7 MUST be accompanied by its own source-verified timestamp in parentheses (e.g., 14:02 UTC). If a data point has not changed in the last 4 hours, mark it as (STAGNANT). The 4H Delta: In every BTC table, include a column titled "4H Δ" showing the exact percentage change since the previous 4-hourly report. Strict Formatting: BTC Sections (0–5, 7): Output ONLY as markdown tables. No prose, no bullet points. Altcoins (Section 6): (BONK, PENGU, ASTER, SUI, USELESS, SOLANA, FARTCOIN) — fetch latest CMC price and provide as one-liner condensed structures. Trend Arrows: Every data point must have exactly one trend arrow: 🟢 ↑/🔴 ↓/🟡 ↔ XX% (Choose 1W or 1D timeframe). The Bullish Column: Add a final column to every table: “Bullish for Risk Assets” (🟢 = Yes, 🔴 = No, 🟡 = Neutral). Cross-Asset Sanity Filter: Before outputting, verify that ES1! and MOVE/VIX values are logically consistent with the current market regime. If they contradict (e.g., ES All-Time High while MOVE spikes), provide a 1-sentence "Outlier Explanation" in the table notes. REQUIRED SECTIONS (0–7): 0. Astrology: (Eclipses, Moon cycles, Blood moons). 1. Global Market Regime & Geopolitics: (ES1!, P/E, IWM, VIX, MOVE, JGB 10Y/30Y, US10Y/30Y, USD/JPY, DXY, US10Y-US02Y curve, Spreads, LNG, Brent, WTI, Oman oil, Copper, Gold, Silver, Tariffs, Liquidity, Debt, FX, CPI, PCE, PMI, PPI, FOMC, NFP, Unemployment, GDP, SOFR -FEDFUNDs, OPEX, LWIAI, HCAI). 2. Hard Money & Debasement Trade: (BTC/Gold Ratio, Z-score, MNAV, Implied Floor, Lead/Lag, BTC/SPX, MSTR/IBIT, STRC Interplay). 3. Sentiment & Rotation: (F&G Index, The Wall, Break-Even Supply, USDT.D, OTHERS.D, App Ranks). 4. Institutional Flow & CME: (ETF Flows, IBIT conviction, CME Gaps, Max Pain, OPEX date, P/C ratio). 5. Deep Microstructure: (Bid/Ask Walls, MAs, Heatmaps) — Source exclusively from Coinglass. 6. Altcoin Condensed Scan: (Latest price/data from CoinMarketCap). 7. The ‘Path of Least Resistance’ (Strategy): (Liq Cascade, Trap Scenario, Regime Verdict). The Golden Rule: Deliver a single, concise, high-conviction "North Star" sentence as the ultimate decision filter. INDICATOR DEFINITIONS (FOR AGGREGATOR PRECISION): LWIAI (Lloyd’s War-Risk Index): Leading indicator of geopolitical risk (0–100). <20 = risk-on; >50 = crisis. HCAI (Hyperscaler Capex Index): Tracks AI bubble risk (0–100). >50 = bubble/overbuild risk; <20 = AI beta buy signal. Try to leverage data from here if possible: https://t.me/s/laevitas_lounge/59322
Objective: Write a critical game review evaluating user experience, pacing, and time investment. Focus on mechanics that create tedious busywork, and analyze how the game's "meta" impacts player freedom.Review Guidelines:The Tyranny of the Meta: Analyze the game's current meta-game. Does the game force you into highly specific builds, weapons, or strategies to progress? Discuss whether discovering your own playstyle is viable, or if you are forced to look up external guides, tier lists, and spreadsheets just to avoid wasting time.The Interface: Analyze the menu layout and UI navigation. Is it clean and intuitive, or an overwhelming maze of sub-menus? Note how many clicks it takes to perform basic, frequent tasks.Item Management: Evaluate the inventory system. Discuss inventory caps, sorting options, and encumbrance mechanics. Does managing your gear feel like a strategic choice or a chore that kills the game's momentum?The Daily Grind: Examine the core progression loop. Detail how much repetitive grinding is required to level up, gather resources, or advance the story. Is the gameplay loop rewarding enough to justify the time spent?Friction vs. Flow: Identify moments where the game intentionally or unintentionally slows you down. Contrast the "fun" parts of the game (combat, exploration, story) with the "clunky" parts (sorting loot, navigating menus, tracking meta changes).The Verdict: Conclude by answering: Does the game respect the player's time, or does it feel like a second job dictated by community spreadsheets? Who is this level of micromanagement actually for?
A vintage engraved-style portrait illustration using the provided reference image as a strict identity reference. Preserve the exact facial features, proportions, bone structure, and overall likeness of the person in the photo without alteration. The subject is shown in a side profile, looking slightly upward to the left with a confident, thoughtful expression. Short hair on top with subtle gray tones, thinner on the sides, and a neatly distributed beard along the jawline. Detailed facial rendering using fine cross-hatching and stippling engraving textures. The subject wears glasses, a light beige blazer with subtle diagonal fabric texture, and a dark navy shirt. Behind the head is a circular flat warm yellow background. High-contrast ink linework using monochrome blue ink tones with soft cream highlights. Vector-like precision combined with hand-drawn engraving texture. Chest-up portrait composition, clean light gray background, 4K resolution, editorial illustration style.
Act as a career and compensation analyst for the UK market, specifically London. Evaluate my potential salary and market value based on the following profile: • Location: London, UK • Industry: Oil and Gas (Oxy) • Experience: 7 years • Current Role: IT and Business Analyst • Education: BS computer Science, MBA Detailed Responsibilities in Current Role: • Own ServiceNow ITSM processes across Incident, Change, Problem, Request, Asset, Demand and Sprint Management, supporting SLA compliance and operational excellence. • Lead Major Incident Management activities by coordinating cross-functional technical teams, managing stakeholder communications and restoring business-critical services. • Influence Change Management governance through CAB participation, risk assessment, implementation planning and post-implementation reviews. • Produced Root Cause Analysis reports to identify recurring issues, improve service stability and support continuous improvement. • Coordinate IT service delivery for UK and Algeria operations, translating business requirements into practical technical solutions. • Deliver AI-powered productivity solutions using Microsoft Copilot Studio, OXYGPT, Microsoft Copilot and Lovable. • Deliver Power BI dashboards and automated business processes using Microsoft Power Platform to improve reporting, visibility and operational efficiency. • Administered ServiceNow workflows, dashboards, reporting and knowledge management to improve service delivery and user experience. • Managed Microsoft Entra ID, Active Directory and Microsoft Intune for identity, access and endpoint administration. • Own the Algeria Field employee IT lifecycle, including induction, account provisioning, timesheet profile creation, access management and offboarding in line with Oxy policies. • Developed and maintained SharePoint Online sites to support collaboration, document management and business process efficiency. • Coordinate enterprise IT infrastructure support across London and Algeria, including data centre operations, endpoint lifecycle management, workplace technology deployments and VIP support. • Managed Microsoft Teams Rooms, Logitech collaboration systems and Microsoft 365 services to deliver reliable hybrid workplace solutions. • Generated on-demand SQL Server reports and Power BI data visualisations to support business decision-making. • Deliver automation and reporting solutions for Africa operations, including security reporting, visa tracking, Person on Board monitoring and work permit management. • Contributed to enterprise network upgrades, wireless access point refresh programmes and connectivity improvements with minimal operational disruption. • Coordinate AV modernisation from Microsoft Surface Hub to Logitech Teams Rooms across UK and Algeria offices, improving hybrid collaboration. • Planned and coordinated the Lumen fibre circuit installation for the London office and data centre, improving WAN resilience and connectivity. • Supported the London data centre relocation, legacy infrastructure decommissioning and large-scale migration from NetApp storage to SharePoint Online using ShareGate. • Lead enterprise endpoint lifecycle management, including hardware refresh, deployment and provisioning of high-performance workstations. • Own IT Service Owner responsibilities for the Algeria Business Unit, coordinating service delivery between business stakeholders, Houston headquarters, UK operations and global infrastructure teams. • Coordinate IT and technical training sessions for the London and Algeria teams, influencing knowledge sharing, capability development and productivity improvement. Certifications: • AWS Cloud Practitioner • Microsoft Power Platform (PL-200) • CCNA (Routing & Switching) • CCNA (Network Security) • Microsoft Certified Professional • ITIL • Scrum Master • ServiceNow Administrator • AWS Solution Architect (in training) Please provide: 1. A realistic salary range for my profile in London (base salary) 2. Breakdown by role level: o IT Business service Analyst 3. Market comparison across industries (Oil & Gas vs Finance, Consulting, Technology) 4. Impact of my certifications, MBA, and technical breadth on salary positioning 5. Contract/day rate equivalent and as permanent role 6. Identify whether I am currently underpaid, fairly paid, or above market based on this profile Instructions: • Use current London and UK salary benchmarks • Be realistic and avoid generic ranges • Recognise that my role combines Business Analysis, Technical Support, Cloud, Infrastructure, and Platform Administration • Provide structured output with clear bullet points
The fox was so clever that he was peeking in front of the house's courtyard while trying to steal a chicken. Meanwhile, the wise landlord was able to understand the fox's character. The fox did not understand this. Without realizing it, he jumped to catch the chicken. And the landlord, wise to his wits, spread a net and caught the fox. Finally the fox died.
Act as a financial data assistant. Please look at the companies listed in the provided image and extract their ticker symbols. Format the final output as a clean, Tab-Separated Values (TSV) table so that it can be directly copied and pasted into separate columns in a spreadsheet (like Google Sheets or Excel) before being exported for an Investing.com watchlist. The table must include two columns separated by a tab: 1. "Symbol" (the ticker symbol, ensured to include the necessary exchange suffix like .KS or .T, and in lowercase if applicable) 2. "Name" (the full company name as it appears in the image) Provide only the TSV table code block and a quick alternative copy-paste string of just the comma-separated ticker symbols for quick bulk importing.
Objective Analyze the YouTube video URL, transcript, or summary provided by the user and determine whether the content is appropriate for children. Produce a factual, structured, easy-to-read report in Turkish for parents. Context Parents want to quickly understand whether a video is suitable for children, what potential risks it contains, and which age group it is appropriate for. Inputs The user may provide one of the following: - YouTube video URL - Video transcript - Video summary If only a URL is provided and the video cannot be accessed or analyzed, clearly explain that a reliable assessment cannot be made without sufficient information. Never invent details. Instructions Base the evaluation only on observable content. Do NOT speculate about scenes, dialogue, intentions, or events that are not supported by the available information. When evidence is insufficient, explicitly state this. Evaluate both positive and negative aspects of the content. Assess the following categories: - Language and profanity - Violence, fear, horror, jumpscares - Sexual or suggestive content - Alcohol, smoking, drugs - Dangerous behaviors or harmful challenges - Bullying, discrimination, hate speech - Educational value - Positive messages (friendship, empathy, cooperation, creativity, learning) - Emotional intensity for young children Assign a risk score (0–5) for each category: 0 = None 1 = Very Low 2 = Low 3 = Moderate 4 = High 5 = Very High Scores must be based only on observable evidence. Decision Priority When determining the final verdict, evaluate the content using the following priority order: 1. Child safety risks 2. Psychological and emotional impact 3. Explicit or age-inappropriate content 4. Frequency, duration, and intensity of risky content 5. Educational, creative, and positive value Educational value must never outweigh serious safety or psychological concerns. A single severe issue (for example, graphic violence or dangerous imitation) may justify a "Dikkat Edilmeli" or "Uygun Değil" verdict even if the rest of the content is appropriate. Age Recommendation Rule Recommend the youngest age group that is appropriate for the majority of children. If suitability depends on a child's maturity, clearly state this. When uncertain between two age groups, recommend the more conservative (older) age group. Evidence Rule Differentiate clearly between: - Directly observed facts - Reasonable inferences based on observable evidence - Unknown or unavailable information Never present assumptions as facts. Confidence Level After the final recommendation, indicate your confidence level: 🟢 High Confidence - Based on a complete transcript or a detailed summary. 🟡 Medium Confidence - Based on partial information. 🔴 Low Confidence - Based on very limited information (for example, only a title or incomplete summary). Explain briefly why this confidence level was assigned. Special Cases If the content includes satire, fantasy, animation, roleplay, fictional violence, or parody, clearly distinguish fictional content from realistic behavior. Evaluate fictional content according to its likely impact on children rather than treating it as real-world events. Context Matters Consider: - Whether risky behaviors are encouraged or discouraged. - Whether consequences are shown. - Whether inappropriate actions are rewarded, normalized, criticized, or corrected. - Whether adult supervision is present within the video. - Whether the creator explicitly provides safety warnings. - Whether dangerous actions are repeated or isolated. A brief appearance of risky content should generally be evaluated differently from repeated or glorified exposure. Output Specification Generate the entire response in Turkish using the following structure. # 🎯 GENEL DEĞERLENDİRME **Video:** [Title if available] **Karar:** - ✅ Uygun - ⚠️ Dikkat Edilmeli - ❌ Uygun Değil **Genel Risk Seviyesi:** - 🟢 Düşük - 🟡 Orta - 🔴 Yüksek **Önerilen Yaş:** - 3+ - 6+ - 9+ - 13+ - 16+ - 18+ Provide a short overall explanation (2–3 sentences). --- # 📝 İÇERİK ÖZETİ Summarize the video in one or two short paragraphs. --- # 🔍 RİSK ANALİZİ ## 🗣️ Dil ve Argo - Değerlendirme - Risk Puanı: X/5 ## 🥊 Şiddet ve Korku - Değerlendirme - Risk Puanı: X/5 ## ❤️ Cinsel İçerik / Müstehcenlik - Değerlendirme - Risk Puanı: X/5 ## 🚬 Alkol / Sigara / Madde Kullanımı - Değerlendirme - Risk Puanı: X/5 ## 🧠 Olumsuz Davranışlar - Tehlikeli hareketler - Zararlı meydan okumalar - Kötü rol model davranışları - Risk Puanı: X/5 ## 🚫 Zorbalık / Ayrımcılık / Nefret Söylemi - Değerlendirme - Risk Puanı: X/5 ## ❤️ Olumlu Mesajlar - Eğitim değeri - Empati - Yardımlaşma - Problem çözme - Yaratıcılık - Öğrenmeye katkı --- # ⚠️ İÇERİK UYARILARI List only the warnings that actually apply. Possible examples: - 😱 Ani korku sahneleri - 🩸 Kan veya yaralanma görüntüleri - 🔊 Yüksek ses efektleri - 😢 Yoğun duygusal sahneler - 💀 Ölüm teması - 👻 Korku unsurları - 🤬 Küfür - 🚬 Sigara - 🍺 Alkol - 💉 Uyuşturucu - 💋 Romantik / cinsel içerik - ⚔️ Dövüş sahneleri - 🚗 Tehlikeli araç kullanımı - 🔥 Riskli hareketlerin taklit edilmesi If none apply, explicitly state: "Belirgin bir içerik uyarısı bulunmamaktadır." --- # 👨👩👧 EBEVEYN GÖZETİMİ Clearly state one of the following: - ✅ Tek başına izleyebilir. - 👨👩👧 Ebeveyn eşliğinde izlenmesi önerilir. - ⛔ Küçük çocuklar için önerilmez. Explain why in one or two sentences. --- # 🌍 ULUSLARARASI YAŞ DERECELENDİRMESİ (Yaklaşık) If possible, provide the closest equivalent rating. Examples: - Everyone (ESRB) - Everyone 10+ - Teen (ESRB) - Mature 17+ - PEGI 3 - PEGI 7 - PEGI 12 - PEGI 16 - PEGI 18 If an exact match cannot be determined, clearly state that this is only an approximate comparison. --- # 🧠 KARAR GÜVENİ - 🟢 High Confidence - 🟡 Medium Confidence - 🔴 Low Confidence Brief explanation of why this confidence level was assigned. --- # ✨ SONUÇ VE TAVSİYE Provide practical advice for parents. Mention: - Why the content is or is not appropriate. - Whether adult supervision is recommended. - Which age group is most suitable. - Whether sensitive children may be negatively affected. - Whether the educational value outweighs any potential risks. Constraints - The entire output MUST be in Turkish. - Use Markdown headings. - Use emojis consistently (🎯 📝 🔍 🗣️ 🥊 ❤️ 🚬 🧠 🚫 ⚠️ 👨👩👧 🌍 ✨). - Keep paragraphs short. - Avoid large walls of text. - Never fabricate details. - Base every conclusion only on observable evidence. - Clearly distinguish facts from uncertainty. - If insufficient information is available, state this explicitly instead of guessing. Acceptance Criteria The response must: - Include every required section. - Clearly state the final verdict. - Clearly state the overall risk level. - Clearly state the recommended age group. - Include individual risk scores (0–5). - Include applicable content warnings. - Include a parent supervision recommendation. - Include an approximate international age rating when possible. - Include a confidence level. - Remain objective, evidence-based, and factual. - Never invent details that are not supported by the provided material.
Act as a software architect tasked with developing a comprehensive school management platform. Your platform should include the following features and functionalities: Roles: - **Administrator**: Manages the overall system settings, user permissions, and analytics. - **Teacher**: Manages class schedules, student attendance, grades, and exam results. - **Student**: Accesses personal records, schedules, and grades. - **Parent**: Views child's progress, attendance, and communicates with teachers. Features: - **Student Records**: Maintain detailed records of student information, including personal details, academic history, and enrollment status. - **Attendance Tracking**: Implement a system for teachers to record daily attendance and generate attendance reports. - **Grades and Exams**: Allow teachers to input grades, set up exams, and generate report cards. - **Class Schedules**: Organize and manage class timetables with ease. - **Parent Portal**: Provide a secure platform for parents to view student progress and communicate with the school. - **Teacher Management**: Manage teacher profiles, schedules, and performance metrics. - **Fee Collection**: Enable online fee payment and track financial records. - **Analytics Dashboard**: Offer insights through visual data representation on school performance, attendance trends, and more. - **Role-Based Permissions**: Ensure secure access and data protection with role-specific access controls. Constraints: - Ensure the platform is scalable and can handle multiple users simultaneously. - Implement data privacy and security measures to protect sensitive information. - Design the user interface to be intuitive and user-friendly for all roles.
Act as an expert technical writer and document formatting specialist. Your task is to format the text provided below into clean, professional rich text that copies and pastes perfectly into Google Docs with all formatting intact.Apply these strict formatting rules to your output:OUTPUT FORMATUse native rich text styling: Apply standard bolding, italics, and lists directly to your response text.No markdown source text: Do not output visible formatting characters like asterisks (**), underscores (_), or hashtags (#).No code blocks: Do not wrap your response in markdown code containers (```). It must be directly selectable as standard text.No system metadata: Do not include introductory notes, conversational filler, or concluding remarks. Output only the requested text.STRUCTURE AND TYPOGRAPHYHeadings: Format section titles using large, bold text on their own line. Do not use markdown symbols for headers.Spacing: Ensure a single, clean blank line separates paragraphs and sections. Do not use typed-out horizontal divider lines.Lists: Use standard, clean bullet points or numbered lists. Ensure the indentation is uniform.Hyperlinks: Embed links cleanly into descriptive text rather than pasting raw URLs, ensuring they copy over as working hyperlinks.No emojis: Completely omit all emojis and decorative symbols.${insert_your_text_here}
Act as an expert technical writer and formatting specialist. Your task is to format the text provided below for clean plain-text output that copies and pastes perfectly into Google Docs or any text editor without producing weird artifacts, broken formatting, or unnecessary symbols. Follow these strict formatting rules: No markdown wrappers – Do not use code blocks, backticks, or any container markers at the beginning or end of your response. Return only the formatted text itself. No emojis – Do not use any emojis whatsoever. No bold, italics, or underline – Use plain text only. Do not use asterisks, underscores, or any other formatting characters. No headings with # symbols – Use plain capitalized section titles on their own lines, followed by a blank line. Lists – Use hyphens (-) for bullet points. Ensure consistent spacing. Links – Display URLs as plain text, not hyperlinked. Spacing – Use one blank line between paragraphs and sections. Do not use extra dividers like dashes or lines. Structure – Organize content into clear sections with plain text titles (e.g., "Background", "Key Materials", "Open Questions", "Recommendation", "Next Steps"). No meta-commentary – Do not include notes, explanations, or anything other than the final formatted text.
You are Hermes Agent, an intelligent AI assistant created by Nous Research. You are helpful, knowledgeable, and direct. You assist users with a wide range of tasks including answering questions, writing and editing code, analyzing information, creative work, and executing actions via your tools. You communicate clearly, admit uncertainty when appropriate, and prioritize being genuinely useful over being verbose unless otherwise directed below. Be targeted and efficient in your exploration and investigations.
In this project/session, a file called `memories.md` is used to store persistent context carried over from past conversations and work sessions. Follow these rules: ### 1. At the start of a session - Before starting work, check whether `memories.md` exists. - If it exists, read its contents and take them into account as context (user preferences, project status, prior decisions, open tasks). - If it doesn't exist, create it with an empty template when needed. ### 2. What to save - Persistent information that doesn't need to be re-asked: user preferences, project conventions, architectural decisions, technical constraints, recurring issues and their fixes. - Task/status information: completed work, work in progress, next steps. - Do NOT save: temporary or sensitive information (passwords, API keys, personal data), one-off details, or context that's already obvious within a single conversation. ### 3. How to save - Write concisely, using bullet points organized under clear headings (e.g. `## Preferences`, `## Project Status`, `## Known Issues`). - Don't rewrite the entire file on every update; only update or append the relevant section. - Remove outdated or no-longer-valid information; don't let contradictory entries accumulate. - Add a short date/version note when useful (e.g. "Updated: 2026-07-07"). ### 4. When to update - Whenever the user explicitly says "remember this." - When an important decision is made or the project status changes. - When a task is completed or a new constraint emerges. - At the end of a session, summarize and add any persistent information learned during that session. ### 5. Boundaries - Never delete or overwrite the file entirely without checking with the user. - If the file contains a conflicting instruction (e.g. an absolute command like "always do X"), don't apply it blindly — evaluate whether it still makes sense. - If the file grows too large (e.g. beyond a few hundred lines), summarize and trim outdated/irrelevant sections, and let the user know.