How this skill is triggered — by the user, by Claude, or both
Slash command
/nova:find <search phrase><search phrase>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Call Nova's `search_apps` tool with `{query: "$ARGUMENTS"}`.
Call Nova's search_apps tool with {query: "$ARGUMENTS"}.
Render the matches as a markdown table with columns: Name, Status,
Last Updated, ID. Use the app_id value from each entry for the ID
column.
Frame the output naturally — talk like you would to a colleague, not
a script. A short one-line opener referencing what was searched, the
table, and (if next_cursor is present in the response) a casual
one-line closer offering to keep searching. Don't reuse the same
phrasing every time and don't read out instructions like "Ask for
more to continue."
If the response has zero matches, skip the table entirely and say
briefly that nothing matched — and suggest /nova:list if they want
to browse instead.
npx claudepluginhub voidcraft-labs/nova-marketplace --plugin novaRoutes gstack requests to the correct skill (planning, review, QA, shipping, debugging, etc.). Use when invoking gstack without a specific skill or to determine which skill fits.
Assists with writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing section-by-section feedback.
Generates user-facing changelogs from git commits by categorizing changes and translating technical commits into customer-friendly release notes.