与「Gmail」相关的搜索结果

8. Gmail + Sheets + Calendar → 搭一套完整的跟进系统 提示词： “分析与 [客户或项目] 的 Gmail 对话，提取待办事项，创建 Google Sheet 跟踪进度、截止日期和状态，再在 Google Calendar 里安排跟进提醒。” 结果：不再错过截止日期，不再忘记跟进。

🚨 Gemini 已经打通 Gmail、Drive、Docs、Sheets、Calendar、Maps、YouTube 和 Search。 但大多数人根本没用上这个优势。 下面 8 个 Gemini 提示词，把它真正的能力释放出来。 先收藏 👇

我才发现 ChatGPT 现在已经会根据你日常的工作和整合的 Connector 来向你推荐应该做什么事。不过，这样是不是说它其实已经有事没事的时候就在读我的 Gmail 了？

开心。终于可以开始讨论一点真问题了。 想讨论的问题是：Muse 这类 personal agent 是否有机会日活过亿，并且有良好的商业模式。 反方代表：玉伯 核心观点： 1、邮件日历是高频需求，这个确实没错。类似国内的微信。想不明白的是，通过 Muse 处理邮件日历，带来的新体验，以及需要交出去的隐私等迁移成本，是否这个体验差足够大。大到能产生某种体验单向门：用上了就回不去了。我自己的体感是，用 Town、Muse 等产品处理邮件日历的体验，并没有这么大。热度一过，会发现 Gmail 等产品的体验也不差。 2、购物、电话催单等场景。催单看了一些案例，确实通过 Muse，有了质的飞跃，是单向门。但购物，和用千问买奶茶，不痛不痒。期待看到更多案例。 3、问答、新闻订阅等，这些 ChatGPT 都能干。Muse 在这块的优势究竟是什么。 综合亲身体验、观察及思考，我的观点是：Muse 要做成国民级应用，难。 期待大家继续打我脸。脸这东西，就是用来打的。不用客气。猛猛反驳，提出你的观察和思考。

看到大家都在说Opus5.5多么多么牛逼，说不眼红，肯定是假的，我是喜欢用Codex，但架不住它的内容交互模式确实不讨人喜欢。。。 所以，我做了一次相当充足的准备，在昨晚凌晨十二点，我重新开通了Claude Pro。 这一次，我清理了Mac基本所有的Claude配置，把Clash Verge换成了Shadowrocket且重新配置网络分流规则。 在新iPhone上面注册了新的Gmail，养了一天，然后用这个Gmail在iPhone上面新注册了Claude账号。 最后用独享的美国IP、新加坡卡，成功在Mac登入Claude账号并购买了Claude Pro会员。 截止目前，iPhone和Mac的Claude都能正常使用。 试了一下网页端的Opus5.5，这交互感觉真特喵爽啊！！！而且每一个文字感觉都比Astra优雅很多倍。。。 兄弟们，等我再用用，如果稳定了，一定给大家出保姆级教程！就是细到那种连银行卡地址怎么去找都给大家截图带提示词的程度！

I am still in talks with Fnatic and they’ve also allowed me to explore other options as well. I’m very hungry and motivated to continue to compete as an IGL, open to offers from all regions, especially EMEA and China Pretty excited! WHO WANTS ME!? Contact: contactboaster@gmail.com

Gemini Live is moving beyond conversation to handle complex tasks on your behalf. With new features in Live like Daily Brief, Gemini Spark, Personal Intelligence, and @Gmail inbox management, you can talk through your day and delegate your to-dos without missing a beat. 🧵

Collected a new list of Grok Bot pro tips shared by the @bot team: 1) Ask Grok Bot to set up Peekaboo on your Mac to enable more OpenClaw like features 2) Use bots as roles (designer, engineer, or PM.) Each has its own system prompt and routines 3) Use channels to organize projects and workstreams. Same bot can work across many different channels 4) Avoid scheduled routines that run too frequently. Hourly or a few times a day is usually good enough 5) For recurring tasks, try giving that to a fresh bot, while you continue your chat with your main bots (like a chief of staff) 6) Set up customizable rules to allow or deny actions. For bots that are connected to X, Gmail, etc. consider blocking any write/destructive actions and have it ask for approval first 7) Feed your Bot examples from your previous handwritten content, it will get better over time 8) Make a Chief of Agents. Give it the rules you want every bot to follow: draft only, naming, voice, what tools they’re allowed to touch. For any new Bots, ask it to create them for you with same rules. 9) For routines, ask yourself if a real human teammate could do this job? If yes, build it. If no, optimize it first. Never run a routine every 5 minutes. 10) Name-driven behavior. Bots act proactively just from the name given at creation. The role is legible from the name, and that alone helps steers behavior. tips sourced from @naoufal_elh @kiaraplds @johnbai @shaoruu @poteto @pengzheng_ @leerob

Github上这个AI找工作的仓库火了🔥 我原本以为 AI 求职就是帮你改改简历，结果有人直接把整个找工作流直接搭出来了！ 作者自己就是第一批小白鼠：2025 年底被裁后，用这套东西跑了 69 份定制申请 → 20 次一面 → 最后拿到合同，2026 年 6 月转成 AI Engineer。这个仓库 3 月才创建，现在已经 3.4 万+ Stars。 把自己的 LinkedIn、学历、过去申请记录丢进去，它先建立一份长期职业档案。之后 /scrape 自动找岗位并去重，/rank 按你的技能、经历、地点、语言和职业目标批量打分，真正值得投的再进 /apply。 最爽的是 /apply 不是“给我写一份简历”这么简单。 它会先判断匹配度，再针对 JD 重写 CV 和求职信，然后再拉一个 Reviewer Agent 当招聘经理挑刺，检查关键词、经历真实性、公司针对性，修改完还会编译成 PDF、检查 ATS 能不能正常读取。 而且这套系统会记账：投过什么、面了几轮、被拒还是拿 Offer，都能留下来。后面面试时，它直接拿当时那份 JD + 你真正投出去的 CV + 求职信 + 前几轮反馈给你准备，而不是重新瞎猜。 甚至还能读 Gmail 找面试邀请、拒信和 Offer，再同步到自己的求职 Pipeline。 这才是我觉得这个项目最聪明的地方：它不是拿 AI 帮你写求职材料，而是把“找工作”本身做成了一套 Agent 工作流。 GitHub：

Grok Bot might be the first tool that lets one non-technical person run an entire business with a team of AI agents. My friend Billy runs his whole newsletter business on Grok Bot agents, and I think we're about to see 100,000+ businesses like his. BEST PRACTICES: 1. The agents run on a shared cloud computer, so running your newsletter, your X, and your receipts all in one place creates context bloat and burns tokens fast. One mission per setup. 2. Start with a Chief of Staff. Give it access to your existing docs (Notion, Slack, Gmail), have it audit the business, then tell you the top three agents to build first to drive revenue. 3. Perfect a task with the Chief of Staff before spinning up a new agent. Have it do the outbound sales once, review it, and only then say "now build a bot that does exactly that." You earn each new hire by proving the task works first. 4. Constraints are the feature. You get a limited number of agents, one thread per bot, like DMs with a teammate. It forces you to stay mission-oriented instead of spinning up a bot for every random idea. 5. You make the decisions, not the agent. Billy's team spent three weeks unable to pick where content should live. At some point you say "we're doing Notion, no more tinkering" and move on. 6. Run week one with no new agents. Build the team, learn to fly the plane, just execute. Week three is when you find the real gaps and expand, someone to man the inbox, someone for the Shopify shop. 7. Then add routines so it works while you sleep. Ask your Chief of Staff what recurring jobs would move the business forward overnight, and it builds the automations that run without you. Thanks to @billyjhowell for sharing the sauce on @startupideaspod (follow for more). Grokbot is really cool. Watch below: