myna: /myna:directory, for listing the product rather than posting about it - #66
Merged
Conversation
…out it myna 0.17.0 submits a product to a software directory over that directory's MCP server. This is the slash command for it, and most of the file is about the ways it is not `/myna:post`. A listing is the product, not a message about it: it is reviewed by a person, then indexed by search engines and assistants. So the command insists on `--dry-run` first, which here really is a preview of what will be sent, unlike `--dry-run` on `myna post` which only resolves targets. It also says plainly that a successful submit means "pending", not "live", because reporting a queued listing as published is the easy mistake. Two things nothing here can do, stated so they are not worked around: signing in to SaaSRow needs an emailed code typed by a person, and a directory can never be reached through `--to all` — its credentials are kept in a different part of the vault precisely so a stray post cannot become a product submission. Custom directories get a section of their own, since `myna directory tools <id>` is the first thing to look at when a submission is refused: it prints what that MCP server actually accepts. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014Y6zh8EdV54VKSFfWCiB3y
ThreatCrush Security Scan12 finding(s) HIGH/CRITICAL: 4 | MEDIUM: 4 | LOW: 4
Snippets are redacted; ThreatCrush never prints matched credential material. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
myna 0.17.0 submits a product to a software directory over that directory's MCP server. This is the slash command for it.
Most of the file is about the ways it is not
/myna:post, because that is where the mistakes are:--dry-runhere really is a preview of what will be sent — unlike--dry-runonmyna post, which only resolves targets. The command insists on it first.Two things nothing can work around, stated plainly:
--to all. Its credentials are kept in a different part of the vault precisely so a stray post cannot become a product submission.Custom directories get their own section, since
myna directory tools <id>is the first thing to look at when a submission is refused: it prints what that MCP server actually accepts.Also bumps the plugin to 0.2.0 and cli-tools to 0.31.0, and adds the row to the plugin README and the marketplace description.
Verification: 857 tests pass (32 files), and all three touched JSON files parse.
🤖 Generated with Claude Code
https://claude.ai/code/session_014Y6zh8EdV54VKSFfWCiB3y