First, I love this concept and I think your demo is great! Collaboration with existing harnesses makes a ton of sense. Just had a conversation with some folks in the non-tech world raving about using Claude.

A few questions:

- How do you think about competing with ChatGPT Canvas or Anthropic's artifacts, when these are shareable, native experiences in their products where users already work?

- Is a "dashboard" limited to analytics or are you trying to expand it to include written reports?

Since teams are connecting MCPs like Granola, Slack, I imagine BitBoard would facilitate sharing demos, PRDs/briefs, or customer reports. This seems like a natural expansion and trivial functionally, so I'm wondering if that's part of the sell now or something you're looking at expanding into as you grow.

Thanks! Non-OP BitBoard cofounder here. Would love to hear your thoughts when you get a chance to check it out.

> How do you think about competing with ChatGPT Canvas or Anthropic's artifacts, when these are shareable, native experiences in their products where users already work?

The flexibility is amazing for static content and playing around with visuals, the experience is just more like a whiteboard than a dashboard. It's hard to do both well in the same place. For reporting I want live connections, consistent logic, the ability to trace provenance, and a more opinionated starting point for the UI.

We started with an extremely flexible surface but there are just a ton of things you don't want to leave up to the agent to implement and we gradually layered those in. It's no fun having to prompt the agent to expose a "view source" affordance, "run" button, or working data labels. But it's a lot of fun building whatever visualization you want and generating a dashboard without a billion clicks in some SQL-abstraction UI.

> Is a "dashboard" limited to analytics or are you trying to expand it to include written reports?

We weakly support written reports today (technically possible with markdown blocks in dashboards for commentary) but will do more to support them in the future for exactly the reasons you called out.

We actually built a more notebook-like artifact for this but cut it to focus on dashboards since they seemed to be a bigger pain point for users. One-off reports can be hit or miss with a chat or coding agent today but static reporting is at least supported with some effort. Live reporting with connection infrastructure, provenance, etc. is much harder to pull together.

I think this is cool! Maybe not your focus, but is there a place for using AI to help figure out who to send photos to / which pockets to send to?

Thanks! :) There could be, talking to users they would definitely like some 'magic button' that automatically organizes the photos into albums by date/location and auto-adds them to pockets. We've been trying to work on a local, opt-in solution on iOS but its definitely not an easy problem to solve, so on the back-burner for now.

Done!

Threw together some of these skills that'll just plug and play with your AI agent. You can download the skill to use them or just copy and paste the ones you like/want to edit.

Lmk if you'd like any added or modified. :-)

It's free btw! Works with any agent that supports skills.

Hey HN,

I built a skill to help you turn your preferred AI tool into a Chief of Staff. It'll work with any connectors you have.

Some pre-packaged commands:

`/debrief gm`: your morning briefing `/debrief triage`: your priority list today.

It's out-of-the-box private: all data stays between you and your agent.

If you want to use it cross-device or keep command history across agents, then you can create a free account.

Working on making the local version much better. It's free to start using!

LMK if you have any feedback, thanks! -Will

Hey HN,

This tool creates non-technical summaries of git pushes for engineers to share with their team.

Hopefully that makes status updates less cumbersome when you get pinged.

Usage — just run this in a repo you want to track (you'll need to login):

  npx @trydebrief/cli@latest init

Features:

- Local git hook (no GitHub auth)

- Option to run fully local (run your own AI script and send us results)

- ZDR: we discard code once summarized; only using models with ZDR policy

- Open source CLI

Would love your thoughts. Thanks!

Hey HN!

I built VibePM to help me turn outlines/specs in my markdown files into small tasks for Cursor to execute.

Some task managers are very heavy duty, so I made this as a lightweight alternative.

Some cool features: - Directly integrates into your editor via MCP - Reusable prompts - Lets you track task implementation

Any feedback is welcome. It's free to try! You just have to make an account.

Thanks! -Will

Hey HN,

A couple weeks ago I shared a GTM repository that *took off* here. After a bunch of user data and feedback, I wanted to offer a simple way for founders to pitch their products to each other.

It is really hard for early-stage founders to connect with buyers and partners in the B2B world.

So, I was hoping this could be a step in that direction toward making pitching, surfacing great products, & learning from each other that much easier.

Curious what y'all think. I just threw this together over a couple days, so lmk bugs too!

- Will

None - but I imagine we'll see some of these in the future, which we ought to handle (e.g. discerning marketing functions v. practical utility)

Thanks, added all this. Send me your thoughts (will at fellowry dot com)