Stats
Actions
Tags
From nl-ez-plugin
Capture structured client, operator, and agent-execution feedback through the asset-broker MCP and write it to the scoped feedback lane in the shared `client-feedback` repo. Use when the user wants to record product feedback on a deliverable or when the agent should file an infra-quality retrospective about the skill/tooling it just used.
How this skill is triggered — by the user, by Claude, or both
Slash command
/nl-ez-plugin:asset-feedbackThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill's full instructions are hosted on the `asset-broker` MCP server. Do not hardcode workflow logic locally — always fetch the live version from the MCP.
This skill's full instructions are hosted on the asset-broker MCP server. Do not hardcode workflow logic locally — always fetch the live version from the MCP.
Read the main skill instructions:
→ call the fs_read tool on the asset-broker MCP with path="skills/asset-feedback/SKILL.md".
Discover reference files (and any other skill assets), then read on demand:
→ call fs_list with path="skills/asset-feedback" (and path="skills/asset-feedback/references"),
→ call fs_read with path="skills/asset-feedback/references/<file>".
Follow the instructions returned by the MCP exactly.
Produce this skill's output only by following the live SKILL.md fetched above and calling the asset-broker MCP's own tools. Do not substitute a local or identically-named base skill from elsewhere, and do not invent your own output path. A locally-produced or unbranded artifact is wrong output, not a fallback — it bypasses the server-side brand and quality gates.
asset-broker MCP is slow to respondThis server scales to zero to save cost, so the first call may take ~10–30s to cold-start. If fs_read or a tool errors with unavailable/timeout:
fs_read call — the call itself wakes the container.npx claudepluginhub stromy-org/nl-ez-marketplace --plugin nl-ez-pluginSearches MemPalace before answering questions about past work, people, projects, or prior decisions. Returns verbatim stored content instead of guessing from model memory.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Implements vector databases with Pinecone, Weaviate, Qdrant, Milvus, pgvector for semantic search, RAG, recommendations, and similarity systems. Optimizes embeddings, indexing, and hybrid search.