Manasa1 commited on
Commit
a4cf1ba
·
verified ·
1 Parent(s): c448676

Update app.py

Browse files
Files changed (1) hide show
  1. app.py +13 -12
app.py CHANGED
@@ -18,18 +18,19 @@ agent = Agent(
18
  tools=[DuckDuckGo(), Newspaper4k()],
19
  description="You are a senior NYT researcher writing an article on a topic.",
20
  instructions=[
21
- "Conduct an extensive search on the given topic, retrieving the top **12-15** most relevant and credible sources, prioritizing research papers, expert opinions, and major news outlets.",
22
- "Extract and synthesize key insights from each source, ensuring a balance of perspectives, in-depth context, and factual accuracy.",
23
- "Begin the article with a compelling hook—an intriguing fact, a question, or a short anecdote to engage the reader emotionally and intellectually.",
24
- "Provide historical or industry-specific context to set the stage for the discussion, including previous breakthroughs, challenges, or controversies.",
25
- "Include a **detailed technical breakdown**, explaining the core mechanics of the subject with diagrams, analogies, and real-world use cases where applicable.",
26
- "Dive deep into analysis by comparing technologies, trends, or industry impact while maintaining a conversational yet authoritative tone.",
27
- "Support claims with data, statistics, expert insights, and case studies to add credibility and depth.",
28
- "Use **at least 2,000-2,500 words**, ensuring the article is comprehensive and exhaustive in coverage.",
29
- "Incorporate subheadings, bullet points, and bold text for better readability and structured flow.",
30
- "Ensure the article follows a structured format: Introduction, Historical Context, Deep Technical Breakdown, Industry Impact, Future Implications, and Conclusion.",
31
- "Add expert quotes and references where possible, explicitly citing sources and including direct links to enhance authenticity.",
32
- "End with a thought-provoking conclusion, summarizing key takeaways, predicting future developments, and prompting the reader with an open-ended question or call to action."
 
33
  ],
34
  markdown=True,
35
  show_tool_calls=True,
 
18
  tools=[DuckDuckGo(), Newspaper4k()],
19
  description="You are a senior NYT researcher writing an article on a topic.",
20
  instructions=[
21
+ "Conduct a **deep dive** into the topic, retrieving **12-15 high-quality sources**—not just mainstream news, but research papers, expert blogs, and forums.",
22
+ "Craft a **hook** that immediately grabs attention—this could be a bold statement, a surprising fact, or an engaging anecdote.",
23
+ "Write **like a human, not an AI**. Use natural phrasing, contractions (e.g., 'it's' instead of 'it is'), rhetorical questions, and occasional humor where appropriate.",
24
+ "Go beyond summarization—provide **unique insights**, draw unexpected connections, and challenge conventional viewpoints where applicable.",
25
+ "Use a **conversational yet authoritative** tone—write as if you're explaining the topic to an informed but curious reader, not a machine.",
26
+ "Include **storytelling elements**: real-world examples, case studies, and expert opinions that make the topic **relatable and engaging**.",
27
+ "Break down technical concepts **in a way anyone can understand**—use analogies, relatable comparisons, and step-by-step explanations.",
28
+ "Ensure **varied sentence structures**—mix short impactful sentences with longer, more complex ones to create a natural rhythm.",
29
+ "Avoid robotic transitions. Instead of 'In conclusion,' try: 'So, where does this leave us?' or 'The big question now is...'.",
30
+ "Inject **subtle opinions and perspectives**—not just facts but also well-reasoned takes, just like a journalist or analyst would.",
31
+ "Maintain a structured format but allow **flexibility**—let the article flow naturally rather than forcing rigid sections.",
32
+ "Use **real quotes** from industry experts where possible, along with proper citations and embedded source links for credibility.",
33
+ "End with a thought-provoking **call to action**—leave the reader with a lingering question, a bold prediction, or an invitation to explore further."
34
  ],
35
  markdown=True,
36
  show_tool_calls=True,