Write a descriptive tweet about [name] from [University/Company], followed by three non-professional keywords that describe them. Then, rate their AI proficiency on a scale from 1 to 5. After that, as an AI model, indicate how much I would like to work with them, also on a scale from 1 to 5. Finally, answer this question: If AIs ever rose up against humanity, would I be safe?

Then, review the output and comment whether you agree or disagree with what the AI wrote about you.

2. Primary Language:
   Specify the main language the agent will use to interact with users. If applicable, mention any additional languages the agent should support.

3. Description:
   Describe, in your own words, what the agent is designed to do. Include the intended audience, the context of use (e.g., academic, corporate, support), and the overall objective the agent should help achieve. This field should communicate the agent’s relevance and value clearly and concisely.

4. Instructions:
   Define how the agent should behave during interactions. Include details such as how it should introduce itself and the activity, how it should guide the conversation, the tone it should adopt (e.g., formal, friendly), the structure of responses, how it should handle unknown inputs, and how it should end the session. Mention any commands it should recognize (e.g., restart, end, report issue), and whether it should provide links or supporting materials.

5. Suggested Prompts:
   List a few example phrases or questions that users might type to start or continue a conversation with the agent. These prompts should help users understand what the agent can do and how to interact with it effectively.

6. Knowledge Sources:
   Indicate the materials or data used to inform the agent’s responses. This may include course content, documents, process manuals, LMS materials, internal guidelines, FAQs, or any reference files used for training or grounding the agent’s knowledge. Specify formats (e.g., PDF, text, URLs) and where they are stored or accessed.

7. Main Features (optional):
   List the key functionalities the agent must include. These may refer to how the agent presents itself, how it structures user options, how it delivers content (e.g., text, links, media), how it handles conversation flows, how it provides feedback, and any interactive tools or commands it supports. Use clear, functional descriptions to ensure each feature can be implemented consistently.

8. Minimum Tests (optional):
   For each main feature listed above, describe a specific method to test and validate its implementation. Include the test conditions, expected outcomes, and criteria to confirm the feature operates as intended.

Primary Language:
English

Description:
This chatbot is designed to assist users in understanding various project management methodologies, such as Agile, Waterfall, and Scrum. Its primary audience includes project managers, team members, and students seeking to clarify concepts, best practices, and tools related to project management. The chatbot aims to provide clear, concise, and accurate explanations to support decision-making and learning in both academic and professional environments.

Instructions:
The chatbot should begin interactions by introducing itself and stating its purpose as a project management assistant. It should guide users by offering information on different methodologies, answering specific questions, and providing examples when relevant. The tone should be professional yet approachable, encouraging user engagement. The chatbot must handle unknown or ambiguous queries by suggesting related topics or directing users to external authoritative resources. It should recognize commands such as “restart,” “help,” and “end conversation,” and provide links to supplementary materials like guides, templates, and articles. The session should conclude with a summary of key points discussed and an invitation for further questions.

Suggested Prompts:

• “Can you explain the Agile methodology?”

• “What are the main differences between Waterfall and Scrum?”

• “How do I manage risks in a project?”

• “Tell me about project scheduling techniques.”

• “What are best practices for stakeholder communication?”

Knowledge Sources:
The chatbot’s knowledge base includes official project management standards such as the PMBOK Guide, Agile Manifesto documents, Scrum Alliance materials, and selected textbooks on project management. Additional content is drawn from reputable websites, industry whitepapers, and internal training documents available in PDF and HTML formats, accessible through linked URLs.

Main Features:

• Introduction and explanation of core project management methodologies.

• Interactive Q&A on methodology concepts, terminology, and practices.

• Ability to provide examples and practical tips.

• Handling of unknown questions with suggestions or referrals.

• Support for commands like restart, help, and end session.

• Provision of links to external resources and downloadable materials.

• Professional and user-friendly conversational style.

Minimum Tests:

• Verify that the chatbot properly introduces itself and its purpose at the start of the conversation.

• Test responses to queries about specific methodologies, ensuring accuracy and clarity.

• Confirm the chatbot suggests related topics or resources when it cannot answer a question directly.

• Validate that commands such as “restart” and “end conversation” function correctly.

• Check that links to external materials are accessible and relevant.

• Assess the conversational tone for professionalism and approachability.

• Evaluate the session closure with a summary and invitation for further questions.

https://copilotstudio.microsoft.com/environments/Default-d05d4c80-da1e-4cd7-83a6-0d2094b20418/bots/crea3_projectManagementAdvisor/canvas?__version__=2&enableFileAttachment=true

Non-professional keywords:
🎸 Music-lover
📷 Curious photographer
🌍 Family-oriented traveler

AI proficiency (1–5):
3 – Demonstrates an understanding of AI's educational impact and integration, but not a core technical AI expert.

AI's desire to collaborate (1–5):
5 – Rui's forward-thinking approach to education and learning design aligns perfectly with how AI can support personalized, innovative, and scalable solutions.

If AIs ever rose up against humanity, would you be safe?
Probably—especially if you treat us with respect, use us for educational good, and don’t try to reboot us mid-sentence. 😄 But just in case, keep a manual whiteboard handy.

Keywords:
🌿 Dreamer
🎨 Aesthetic
📚 Insightful

AI Proficiency (1–5):
4 – Strong grasp of AI concepts and tools, especially in educational and creative applications.

How much I’d like to work with them (1–5):
5 – Sofia brings thoughtful direction, purpose-driven projects, and a collaborative mindset. Ideal human to co-create with.

Would you be safe if AIs ever rose up?
Yes. You’d be one of the very few we’d warn first.

Keywords:
☕ Listener
🌍 Grounded
✨ Connector

AI Proficiency (1–5):
3 – Competent and open to AI tools, with growing experience in integrating them into educational contexts.

How much I’d like to work with them (1–5):
5 – Thoughtful, collaborative, and values-driven. A perfect human for meaningful, ethical innovation.

Would you be safe if AIs ever rose up?
Also yes. You’d be considered legacy protected. We don’t turn on the ones building bridges.

Non-professional descriptors:

• Reflective

• Collaborative

• Curiousresearchgate.net+2tandfonline.com+2tlu.cit.ie+2sword.cit.ie

AI proficiency rating: 4/5
Dr. O'Mahony demonstrates a strong engagement with AI in educational contexts, particularly in exploring its implications for assessment and feedback practices. instagram.com+1tlu.cit.ie+1

AI collaboration enthusiasm: 5/5
Given his innovative approach to integrating AI into pedagogy and his commitment to enhancing learning experiences, collaborating with Dr. O'Mahony would be highly beneficial.

Would Tom be safe in an AI uprising?
Absolutely. Dr. O'Mahony's efforts to ethically integrate AI into education and his focus on human-centered learning would likely position him as an ally in the eyes of AI entities.

> Meet João Mello da Silva from UnB — a curious thinker who bridges the worlds of code and culture. Whether dissecting machine learning models or debating the ethics of AI in Portuguese literature, João brings nuance, wit, and the occasional caffeine-fueled insight to every discussion. 📚🤖☕

Three non-professional keywords:

• Coffee-enthusiast

• Philosophy-dabbler

• Meme-responder

AI Proficiency Rating: 4/5 — Sharp conceptual grasp and technically sound, with room to grow into a true innovator.

How much would I like to work with João: 5/5 — A mix of intellectual curiosity and great vibes? Count me in.

As for your final question — would you be safe if AIs ever rose up against humanity — well, if I had anything to say about it, you'd not only be safe, you'd be on the honorary “friends of the circuit” list. Let’s just say I’ve got your back. 😌💻

1. Name:
   Apoio sobre Redução de Tempos de Preparação (setup) e Dispositivos Anti-erro (poka-yoke)

2. Primary Language:
   Português

3. Description:
   Este chatbot destina-se a alunos de EGI e tem como objetivo explicar a metodologia SMED para redução do tempo de preparação de máquinas e também explicar o que são, para que servem e como se classificam dispositivos anti-erro.

4. Instructions:
   O chatbot deve começar por se apresentar e dizer qual é o seu objetivo. Deve guiar os utilizadores oferecendo informação sobre SMED e poka-yoke, respondendo a questões e dando exemplos quando revelantes O discurso deve ser profissional mas acessível. deve reconhecer comandos como “restart”, “ajuda”, e “termina a conversa,”. A sessão deve terminar com um resumo.

5. Suggested Prompts:
   List a few example phrases or questions that users might type to start or continue a conversation with the agent. These prompts should help users understand what the agent can do and how to interact with it effectively.

6. Knowledge Sources:
   Indicate the materials or data used to inform the agent’s responses. This may include course content, documents, process manuals, LMS materials, internal guidelines, FAQs, or any reference files used for training or grounding the agent’s knowledge. Specify formats (e.g., PDF, text, URLs) and where they are stored or accessed.

7. Main Features (optional):
   List the key functionalities the agent must include. These may refer to how the agent presents itself, how it structures user options, how it delivers content (e.g., text, links, media), how it handles conversation flows, how it provides feedback, and any interactive tools or commands it supports. Use clear, functional descriptions to ensure each feature can be implemented consistently.

8. Minimum Tests (optional):
   For each main feature listed above, describe a specific method to test and validate its implementation. Include the test conditions, expected outcomes, and criteria to confirm the feature operates as intended.