Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Untitled topic

news.ycombinator.com

Post reply on HN
Print view View original

1–10 of 13 posts

Re: undefined

#2

Post by CharlieDigital »

I wish all of the tooling vendors would support MCP prompts because that would solve this problem and provide a very good way of delivering aggregate feeds of skills -- dynamically, even.

Codex, for example, currently does not support this[0].

Then we can just point to an MCP server and have the MCP server dynamically compose the set of skills without needing to do any syncs, git sub-modules, etc.

[0] https://github.com/openai/codex/issues/5059

Re: undefined

#3

Post by stingraycharles »

CharlieDigital wrote: post #2

I wish all of the tooling vendors would support MCP prompts because that would solve this problem and provide a very good way of delivering aggregate feeds of skills -- dynamically, even. Codex, for example, currently does not support this[0]. Then we can just point to an MCP server and have the MCP server dynamically compose the set of skills without needing to do any syncs, git sub-modules, etc. [0] https://github.…

Skills are not (only) just prompts, the more advanced skills have scripts or other assets as well.

Re: undefined

#4

Post by climike »

CharlieDigital wrote: post #2

I wish all of the tooling vendors would support MCP prompts because that would solve this problem and provide a very good way of delivering aggregate feeds of skills -- dynamically, even. Codex, for example, currently does not support this[0]. Then we can just point to an MCP server and have the MCP server dynamically compose the set of skills without needing to do any syncs, git sub-modules, etc. [0] https://github.…

Also worth pushing for a more standardized skills command for CLIs, similar to —help, but for (agent/human) workflows, https://cliwatch.com/blog/designing-a-cli-skills-protocol (if you ship these with your CLI, you also get versioning out of the box so to say)

Re: undefined

#5

Post by hatappo »

CharlieDigital wrote: post #2

I wish all of the tooling vendors would support MCP prompts because that would solve this problem and provide a very good way of delivering aggregate feeds of skills -- dynamically, even. Codex, for example, currently does not support this[0]. Then we can just point to an MCP server and have the MCP server dynamically compose the set of skills without needing to do any syncs, git sub-modules, etc. [0] https://github.…

  Yes, I agree that MCP-based prompt/skill delivery would be a very interesting direction.

  If tooling vendors broadly supported MCP prompts, an MCP server could become a dynamic distribution layer for team-managed skills, which would remove a lot of sync-oriented workflow.

  My current assumption is that we still need something Git-native today because:
  - skills are mostly authored and reviewed in Git
  - teams need provenance and governance around them
  - tool support for MCP prompt delivery is still incomplete

  So I see Harbor more as a practical system for the current ecosystem, not necessarily the final shape.

Re: undefined

#6

Post by [deleted] »

hatappo wrote: post #5
CharlieDigital wrote: post #2

I wish all of the tooling vendors would support MCP prompts because that would solve this problem and provide a very good way of delivering aggregate feeds of skills -- dynamically, even. Codex, for example, currently does not support this[0]. Then we can just point to an MCP server and have the MCP server dynamically compose the set of skills without needing to do any syncs, git sub-modules, etc. [0] https://github.…

Yes, I agree that MCP-based prompt/skill delivery would be a very interesting direction. If tooling vendors broadly supported MCP prompts, an MCP server could become a dynamic distribution layer for team-managed skills, which would remove a lot of sync-oriented workflow. My current assumption is that we still need something Git-native today because: - skills are mostly authored and reviewed in Git - teams need proven…

[deleted]

Re: undefined

#7

Post by hatappo »

climike wrote: post #4
CharlieDigital wrote: post #2

I wish all of the tooling vendors would support MCP prompts because that would solve this problem and provide a very good way of delivering aggregate feeds of skills -- dynamically, even. Codex, for example, currently does not support this[0]. Then we can just point to an MCP server and have the MCP server dynamically compose the set of skills without needing to do any syncs, git sub-modules, etc. [0] https://github.…

Also worth pushing for a more standardized skills command for CLIs, similar to —help, but for (agent/human) workflows, https://cliwatch.com/blog/designing-a-cli-skills-protocol (if you ship these with your CLI, you also get versioning out of the box so to say)

I think TanStack Intent is quite close to that direction.

Packaging skills with libraries/CLIs and letting agents discover them from installed packages makes a lot of sense. I see Harbor as addressing a different layer on top of that: organizational collection, cataloging, provenance, governance, and safety.

Re: undefined

#8

Post by hatappo »

stingraycharles wrote: post #3
CharlieDigital wrote: post #2

I wish all of the tooling vendors would support MCP prompts because that would solve this problem and provide a very good way of delivering aggregate feeds of skills -- dynamically, even. Codex, for example, currently does not support this[0]. Then we can just point to an MCP server and have the MCP server dynamically compose the set of skills without needing to do any syncs, git sub-modules, etc. [0] https://github.…

Skills are not (only) just prompts, the more advanced skills have scripts or other assets as well.

[dead]

Re: undefined

#9

Post by CharlieDigital »

stingraycharles wrote: post #3
CharlieDigital wrote: post #2

I wish all of the tooling vendors would support MCP prompts because that would solve this problem and provide a very good way of delivering aggregate feeds of skills -- dynamically, even. Codex, for example, currently does not support this[0]. Then we can just point to an MCP server and have the MCP server dynamically compose the set of skills without needing to do any syncs, git sub-modules, etc. [0] https://github.…

Skills are not (only) just prompts, the more advanced skills have scripts or other assets as well.

Scripts are just text; skills are just text. Scripts can be inlined with the skill. Agent can create its own temp dir and extract the script to run.

Don't overthink it; it's all just text. I want to serve the text from HTTP instead of having to deploy via `git` and sync. I want to be able to dynamically generate that text on the server based on the identity of the user, their role, what team they're in, what repo they're working on.

I don't want static skills. That users have to remember to sync and keep up to date.

Post reply on HN