johnjungles
Joined 9 years ago
Karma
75
Submissions
79
Member since
Dec 28
Recent submissions
Comment · 1 year ago
Building https://check.supply: the easiest way to mail a real paper check from your iPhone. Link your bank, type the amount, and we print + mail it for you — with optional certified or express USPS tracking
Comment · 1 year ago
PR fatigue is a real thing
Comment · 1 year ago
Talk to your skip
Comment · 1 year ago
Maybe we should have models govern models to prevent models from going haywire and falling into a loop of a repetitive pattern or influencing society towards swarm like behavior patterns
Comment · 1 year ago
If you want to try out mcp (model context protocol) with little to no setup:
I built https://skeet.build/mcp where anyone can try out mcp for cursor and dev tools.
We did this because of a painpoint I experienced as an engineer having to deal with crummy mcp setup, lack of support you have no idea how hard it is to set up SSE, deal with API keys and scope issues, and then to find things like the tool that you want isn’t even coded yet.
And so one of the areas we found it to be useful was to do the soft communications with tools like Jira linear slack - updating stakeholders and all that friction that engineers hate doing. Some other areas people use a lot of tools with sequential thinking
Mostly for workflows that I like:
* start a PR with a summary of what I just did * slack or comment to linear/Jira with a summary of what I pushed * pull this issue from sentry and fix it * Find a bug a create a linear issue to fix it * pull this linear issue and do a first pass * pull in this Notion doc with a PRD then create an API reference for it based on this code * Postgres or MySQL schemas for rapid model development
Everyone seems to go for the hype but ease of use, practical pragmatic developer workflows, and high quality polished mcp servers are what we’re focused on
Lmk what you think!
Comment · 1 year ago
ArgoCD
Comment · 1 year ago
We built https://skeet.build/mcp that allows you to connect mcp easily to figma, Notion, Jira, etc…
Seems like though people want more integration to more local tools
Comment · 1 year ago
https://skeet.build
Building a tool to supercharge your Cursor, Windsurf, Claude and other developer tools by connecting it to polished, high quality mcp servers for linear, slack, DBs, and other useful workflows.
Comment · 1 year ago
If you want to try out mcp (model context protocol) with little to no setup:
I built https://skeet.build/mcp where anyone can try out mcp for cursor and dev tools.
We did this because of a painpoint I experienced as an engineer having to deal with crummy mcp setup, lack of support you have no idea how hard it is to set up SSE, deal with API keys and scope issues, and then to find things like the tool that you want isn’t even coded yet.
And so one of the areas we found it to be useful was to do the soft communications with tools like Jira linear slack - updating stakeholders and all that friction that engineers hate doing. Some other areas people use a lot of tools with sequential thinking
Mostly for workflows that I like:
* start a PR with a summary of what I just did * slack or comment to linear/Jira with a summary of what I pushed * pull this issue from sentry and fix it * Find a bug a create a linear issue to fix it * pull this linear issue and do a first pass * pull in this Notion doc with a PRD then create an API reference for it based on this code * Postgres or MySQL schemas for rapid model development
Everyone seems to go for the hype but ease of use, practical pragmatic developer workflows, and high quality polished mcp servers are what we’re focused on
Lmk what you think!
Currently working on a desktop app so everything runs on a native Mac app!
Comment · 1 year ago
If you want to try out mcp (model context protocol) with little to no setup hosted for you:
I built https://skeet.build/mcp where anyone can try out mcp for cursor and dev tools.
We did this because of a painpoint I experienced as an engineer having to deal with crummy mcp setup, lack of support you have no idea how hard it is to set up SSE, deal with API keys and scope issues, and then to find things like the tool that you want isn’t even coded yet.
And so one of the areas we found it to be useful was to do the soft communications with tools like Jira linear slack - updating stakeholders and all that friction that engineers hate doing. Some other areas people use a lot of tools with sequential thinking
Mostly for workflows that I like:
* start a PR with a summary of what I just did * slack or comment to linear/Jira with a summary of what I pushed * pull this issue from sentry and fix it * Find a bug a create a linear issue to fix it * pull this linear issue and do a first pass * pull in this Notion doc with a PRD then create an API reference for it based on this code * Postgres or MySQL schemas for rapid model development
Everyone seems to go for the hype but ease of use, practical pragmatic developer workflows, and high quality polished mcp servers are what we’re focused on
Lmk what you think!
Comment · 1 year ago
I built https://skeet.build which lets your connect your favorite tools via mcp to Cursor. We focus exclusively on developers and dev tools to build high quality “it just works” experiences for mcp because we found that community mcp quality is low, many mcps were not useful for devs, and SSE remote mcp took a lot of effort to get it to a point where it’s reliable and working well.
[Sequential thinking](https://skeet.build/docs/integrations/sequentialthinking) - it’s like enabling thinking but without the 2x cost
[Memory](https://skeet.build/docs/integrations/memory) - I use this for repo / project specific prompts and workflows
[Linear](https://skeet.build/docs/integrations/linear)- be able to find and issue, create models a branch and do a first pass, update linear with a comment on progress
[github](https://skeet.build/docs/integrations/github) - create a PR with a summary of what o just did
[slack](https://skeet.build/docs/integrations/slack) - send a post to my teams channel with the linear and GitHub PR link with a summary for review
[Postgres](https://skeet.build/docs/integrations/postgres) / [redis](https://skeet.build/docs/integrations/redis) - connect my staging dbs and get my schema to create my models and for typing. Also use it to write tests or do quick one off queries to know the Redis json I just saved.
[Sentry](https://skeet.build/docs/integrations/sentry) - pull the issue and events and fix the issue, create bug tickets in linear / Jira
[Figma](https://skeet.build/docs/integrations/figma) - take a design and implement it in cursor by right clicking copying the link selection
[Opensearch](https://skeet.build/docs/integrations/opensearch) - query error logs when I’m fixing a bug
Comment · 1 year ago
If you want to try out mcp (model context protocol) with little to no setup:
I built https://skeet.build/mcp where anyone can try out mcp for cursor and now OpenAI agents!
We did this because of a painpoint I experienced as an engineer having to deal with crummy mcp setup, lack of support and complexity trying to stand up your own.
Mostly for workflows like:
* start a PR with a summary of what I just did * slack or comment to linear/Jira with a summary of what I pushed * pull this issue from sentry and fix it * Find a bug a create a linear issue to fix it * pull this linear issue and do a first pass * pull in this Notion doc with a PRD then create an API reference for it based on this code * Postgres or MySQL schemas for rapid model development
Everyone seems to go for the hype but ease of use, practical pragmatic developer workflows, and high quality polished mcp servers are what we’re focused on
Lmk what you think!
Comment · 1 year ago
I actually think that most problems that took 5-20 mins are now a few minutes and it’s more about how many of those intense minutes and loops you’re going through.
Also, right now engineers are hyper optimized in the code aspects but not thinking about the context into cursor and context out of cursor.
Like the amount of copy paste from Notion / JIRA / Sentry and the amount of output like summarizing the git commits and PRs, slack and other “over communication” you have to do these days. This is the area I think we can more easily automate away.
Comment · 1 year ago
Thanks for putting this together!
Have you also looked at mcp?
https://modelcontextprotocol.io/introduction
https://github.com/appcypher/awesome-mcp-servers
mcp.run glams.ai smithery.ai skeet.build (disclaimer: I built this one)