Public screening report
This public cut includes only skills that can be explained without private URLs, credentials, trading logic, routing internals, customer material, or secret-like literals. The checked-in sources are the manifest, Markdown content, and local SVG cover art in this repo.
Seeded skills
1. public-catalog-curation - Public-safe because it teaches how to separate a public catalog from a larger private library. - The page stays generic and avoids internal repository names or operator notes.
2. markdown-skill-rendering - Public-safe because it documents Markdown to HTML rendering at build time. - The page does not include any private templates, prompt text, or internal content sources.
3. manifest-search-filtering - Public-safe because it explains search and filter logic against a checked-in manifest. - The page uses only local data and no live customer or account data.
4. static-assets-worker-routing - Public-safe because it covers a minimal Worker plus static assets deployment pattern. - The page leaves out secrets, auth, queues, databases, and internal infra helpers.
5. accessibility-preflight - Public-safe because it is a generic launch checklist for contrast, focus order, motion, and empty states. - The page contains no client names, hidden workflows, or proprietary test data.
6. seo-sitemap-publishing - Public-safe because it covers sitemap, robots, and canonical metadata generation. - The page is written as a reusable publishing pattern, not as a copy of any private site map.
7. public-screening-reporting - Public-safe because it documents the filtering rules used to keep this catalog clean. - The page itself is the public record of what was included and why.
Excluded content
- Proprietary trading skills and execution helpers were excluded because they carry operational risk and are not public catalog material.
- Routing and profile management notes were excluded because they expose internal topology and operator names.
- Customer or client material was excluded because it is not safe to publish in a public reference catalog.
- Credential-bearing strings, secret-like literals, tokens, keys, and private URLs were excluded because they must never ship in public assets.
- Executable infrastructure helpers were excluded because the public catalog should describe skills, not distribute control-plane shortcuts.
- Atlas-style private repository content was not copied wholesale. Each seeded page was authored from scratch with only the public-safe pattern preserved.
Copy hygiene
Visible copy avoids em-dashes, secret literals, and internal identifiers. The public pages use checked-in manifest data, Markdown files, and local SVG cover art. Outbound links remain intentional and include GitHub, the Minte.Dev blog, and the source URLs listed on each skill page.