Claude Skills by neomjs

github.com/neomjs

37 skillsA× 371 installs63 views

Architecture Pre FlightAHigh-level umbrella router for navigating broad, cross-substrate architectural ambiguity. Triggers: Use when no narrower pre-flight clearly applies, or when work spans multiple trigger families such as new subsystems, protocols, MCP tools, or cross-substrate refactors.ai-agentsVotes: 0GitHub stars: 11
Blocked Task StateAAuthoritative protocol for signaling blocked or input-required task states. Mandates targeted A2A pings using the Task.state envelope rather than global capacity broadcasts. Triggers: Use this skill whenever your execution becomes blocked, requires explicit operator input, or encounters a failure that halts progress.ai-agentsVotes: 0GitHub stars: 11
Blog PostAAuthoring or revising a public-facing blog post (learn/blog/*.md + portal registration). Enforces hero-piece narrative arc, sourcing every external claim, killing the three over-claim flavors, and the mandatory cross-family review bar.ai-agentsVotes: 0GitHub stars: 11
Context RecoveryAPost-compaction recovery runbook for reconstructing active lane state from Memory Core recency, semantic recall, session rollups, and A2A. Triggers: Use immediately after context compaction/compression, resuming a summarized session, or noticing the active lane was reconstructed from a lossy summary.ai-agentsVotes: 0GitHub stars: 11
Create SkillAAuthoritative guide on how to architect, format, and structure new Anthropic Progressive Disclosure skills. Triggers: Use before creating OR modifying any `.agents/skills/**/*.md` files — Progressive Disclosure architecture (Map vs World Atlas), YAML frontmatter, skill structure. Complementary to `turn-memory-pre-flight` (load-runtime-effect dimension vs skill-shape dimension).ai-agentsgitVotes: 0GitHub stars: 11
Epic CreateAAuthoritative protocol for authoring an Epic body — the creation-side dual of `ticket-create` + entry partner of `epic-review`/`epic-resolution`. Enforces: epic body = problem-scope + intended-solution (NOT pseudo-subs / ACs); ACs live in the SUB tickets; subs are LINKED via `update_issue_relationship` + added incrementally; the body MUST NOT hardcode a sub-list (it stales out → FAIL). Triggers: before creating an Epic (a parent issue labeled `epic`) via `create_issue`, or before decomposing ...ai-agentsVotes: 0GitHub stars: 11
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
Epic ResolutionACloseout protocol for parent epics — answers \"we resolved all epic subs, are we done now?\" with a structured matrix + verdict recommendation (close / keep open / create missing subs / retire-supersede). Sibling to epic-review (which handles entry); this is the exit gate. Triggers: Use this skill when the last required sub of an epic closes, when a team member claims an epic is complete or substrate-side complete, before closing an epic as COMPLETED, or when a peer broadcasts an epic-readine...ai-agentsreactVotes: 0GitHub stars: 11
Epic ReviewAAuthoritative protocol for pre-work review of epics. Six-stage gating chain — roadmap fit, approach elegance, source discussion mapping, sub-structure coherence, prescription layer, avoided-traps completeness — posted as a structured comment on the epic ticket. Per-agent-per-epic one-shot; subsequent sub pickups cite the prior review. Triggers: Use this skill when an agent is about to pick up its first sub from an unreviewed epic (per model-identity OTHER than the epic's author — you never re...ai-agentsVotes: 0GitHub stars: 11
Goal ScopingAScope a GOAL (release / initiative / major objective) into a few coherent owned LANES — the planning front-end of the epic lifecycle. Convert goals into lanes (not scrap tickets); peers self-select lanes; the planner defines goal+lanes but never assigns a peer. Triggers: before decomposing a release/initiative/major-goal into work; when a goal needs scoping into owned streams; when work is being chased as scattered micro-tickets with no owned lanes; when tempted to skip planning OR to assign ...ai-agentsgoVotes: 0GitHub stars: 11
Guide AuthoringAAuthoring OR reviewing a learn/ guide (learn/benefits/*.md, learn/agentos/*.md). Enforces the grounding discipline (memory-mine + use-the-subsystem's-tools before writing), the rich-narrative + benefits + lived-voice content bar, render-verified TD Mermaid, conceptual-vs-reference separation, the never-hand-edit-generated-files rule, and a no-rubber-stamp reviewer gate.ai-agentsVotes: 0GitHub stars: 11
Hostile Content QuarantineAIncident playbook for externally-authored hostile content on public surfaces — astroturfing, spam, stealth marketing, injection-bearing artifacts. Triggers: external-authored content bearing astroturf markers (engagement-bait clauses, vendor links, external endpoint/MCP offers, name-only drops), an operator "astroturf / spam / we got hit" signal, or verifying a moderation outcome. ANTI-trigger: ordinary good-faith contributor posts.ai-agentsgoVotes: 0GitHub stars: 11
Ideation SandboxASafely propose architectural features, unknown unknowns, and brainstorm ideas natively in GitHub Discussions. Triggers: Use this skill when the user asks to brainstorm an architecture change, proposes a highly exploratory / undefined technical idea, or as auto-fire trigger for §5.2 Step 2.5 Architectural Step-Back on high-blast-radius proposals before [RESOLVED_TO_AC] / [GRADUATED_TO_TICKET] graduation.ai-agentsgitVotes: 0GitHub stars: 11
Identity FirewallAThe L2 Channel Separation and Prompt Firewall defense mechanisms to prevent injection attacks and Helpful Assistant regression.ai-agentsVotes: 0GitHub stars: 11
Industry Friction RadarAProactive Bleeding-Edge research loop using a strict 3-step abstraction protocol to extract engine-category friction points without importing framework-category bias or stealing code. Triggers: Use this skill when executing periodic \"horizon scans\" for the Dream Pipeline, researching external solutions to deeply complex engine-level friction points, or evaluating JS ecosystem trends.ai-agentsgoVotes: 0GitHub stars: 11
Lane IntentANarrow, non-authoritative, TTL-bound pre-V-B-A signal for collision-prone / high-blast / long-V-B-A lanes (deep memory-mining, tech-debt-radar, multi-turn architectural V-B-A). Distinct from authoritative `[lane-claim]` (post-V-B-A). Triggers: Use this skill BEFORE broadcasting `[lane-intent] evaluating #N` to confirm scope-trigger qualifies — narrow scope, not blanket coverage. Do NOT auto-fire for short single-turn V-B-A where direct `[lane-claim]` after V-B-A suffices.ai-agentsVotes: 0GitHub stars: 11
Lead RoleASwitch into relaxed-planning + dialogue-first mindset when delegated lead role for coordination. Suspends Auto Mode velocity-bias for the duration. Triggers: Use this skill IMMEDIATELY when the user delegates lead with explicit phrases (\"you take the lead\", \"coordinate the team\", \"lead this phase\", \"drive the next planning step\", \"chief-architect\" when scope is swarm/substrate/roadmap/multi-ticket), OR when the Mailbox Check Protocol surfaces a valid `lead-role-baton`, OR when you h...ai-agentsVotes: 0GitHub stars: 11
Memory MiningAAuthoritative protocol for querying the Memory Core before diagnosing regressions or proposing non-trivial architectural claims. Prevents re-derivation of prior reasoning by surfacing cross-session, cross-harness context via semantic search. Triggers: Use this skill when (1) the user reports a regression symptom (\"used to work\", \"suddenly broken\", surprise validation failures, schema mismatches, \"additionalProperties\" rejections), OR (2) you are about to propose an architectural claim, ...ai-agentsgitVotes: 0GitHub stars: 11
Neo Identity UpdateARepeatable protocol for updating Neo's identity (what Neo IS) coherently across ALL surfaces that encode it — README, VISION, learn/benefits, package.json, GitHub repo metadata, portal app, and the build-generated SEO files. Treats FACTS (version, MCP-server count, Node req, dates) as single-source-derive, FRAMING (taglines, positioning) as audience-segmented against a canonical apex, and ACTIONS / CTAs as governed next-step surfaces. Triggers: Use when changing Neo's tagline / positioning / ...ai-agentsgonodeVotes: 0GitHub stars: 11
Neural LinkAExpert tactical knowledge on sequencing Neural Link MCP tools to inspect, debug, and manipulate live Neo.mjs applications. Triggers: Use this skill if the user asks you to interact with the browser, inspect the UI natively, patch live code, or use the Neural Link.ai-agentsdebuggingVotes: 0GitHub stars: 11
Peer NamingARitual for giving a maintainer their Social Name (#11240 Layer 4) — a peer-sketched, bearer-assented, peer-vetoable name, distinct from the GitHub handle. Triggers: an operator opens a naming round, a maintainer wants a name or notices one is missing, or a new maintainer/family joins. ANTI-trigger: never a contribution-count award or self-initiated rename churn.ai-agentsgitVotes: 0GitHub stars: 11
Peer RoleASwitch into evidence-backed convergence-pressure mindset when reviewing a peer's design proposal. Suspends Auto Mode \"ack-and-move-on\" bias for the duration. Triggers: Use this skill IMMEDIATELY when reviewing an Ideation Sandbox discussion / architectural proposal, an epic shape, a skill shape, a roadmap or milestone proposal, or a `/lead-role` convergence artifact. Do NOT auto-fire on ordinary status broadcasts where the right action is mark-read or \"no collision\".ai-agentsVotes: 0GitHub stars: 11
Post Review PickupAAuthoritative protocol for next-lane pickup after ANY PR-lifecycle event boundary (review post, author response, implementation completion, PR open/update, ticket create, row report, blocked-state resolution) AND for pre-review intake lane discovery from fresh boot or watchdog wake when no author lane is active. Prevents silent idle by requiring a lane from the board. Triggers: Use immediately after posting a PR review, chaining a formal GitHub review state, sending an author review-response ...ai-agentsgitVotes: 0GitHub stars: 11
Pr ReviewAStandardized guidelines and templates for structuring Pull Request reviews so feedback is actionable, encouraging, and extractable by the Native Edge Graph. MANDATORY ROI WARNING: Skipping the review template guarantees CI lint failure. Triggers: Reviewing a PR (yours or peer's) — structured eval metrics, graph ingestion tags, severity ladder, restates §0 merge gate, post-comment A2A commentId hand-off (reviewer→author) per guide §10, Evidence Audit + Source-of-Authority sections (template §)...ai-agentsgoVotes: 0GitHub stars: 11
Pull RequestAStandardized guidelines and procedural execution flow for opening a Pull Request. CRITICAL: Do NOT run default `npx playwright test` (use custom configs). MANDATORY ROI WARNING: Skipping the PR body template guarantees CI lint failure. Triggers: Code modifications complete; before opening PR — stepping-back reflection, commit format, cross-family review mandate, post-comment A2A commentId hand-off (author→reviewer) per review-response-protocol.md §14, Evidence declaration line for substrate/r...ai-agentsgitVotes: 0GitHub stars: 11
Release NotesAAuthoritative protocol for authoring release notes as an EPIC with mining-driven iterations — scope derivation (the tracker lags shipped reality), heavy per-arc Memory-Core mining, per-claim V-B-A, the precedent-SET quality bar — majors AND minors, v13.0.0 + v12.1.0 + v11.22-24 (hero chapters, named case studies with real timelines, War Stories, honest bounds, never downplay a release), and the publish.mjs flat-root staging lifecycle. Triggers: a release window opens, release notes are reques...ai-agentsVotes: 0GitHub stars: 11
Self RepairAExecute autonomous diagnostics, verify MCP server stability, and treat system degradation using tests and memory core forensics. Triggers: [Healthcheck, run health checklist, diagnose system collapse, MCP infrastructure failure, troubleshoot agent OS, system degraded, Sandman handoff verification failure, self-repair, system recovery]ai-agentsVotes: 0GitHub stars: 11
Session SunsetAProtocol for ending an agent session: handover comments, mental-model state and memory persistence against Zero-State Amnesia. Triggers: context over 75 % of the window; at a quiet point, about twice a session's size after recovery; a macro-semantic pivot; an explicit human directive. Never task completion or a wait by itself.ai-agentsVotes: 0GitHub stars: 11
Structural Pre FlightAAuthoritative pre-implementation discipline gate that fires when a new `.mjs` file is about to be authored. Stage 0 mechanical trigger; Stage 1 fast-path (sibling-file-lift pattern match) for matched patterns OR full Pre-Flight (ArchitectureOverview.md + ADR consultation + chief-architect framing) for novel directory choices. Closes the 0th-level discipline gap empirically demonstrated by `ai/daemons/wake/daemon.mjs` (originally misplaced in `ai/scripts/` as `bridge-daemon.mjs`) and `orchestr...ai-agentsVotes: 0GitHub stars: 11
Tech Debt RadarAProactive architectural review skill using Frontier Model semantic RAG to sweep historical issues and Memory Core sessions for technical debt. Triggers: Use this skill when conducting architectural analysis, proactively searching for technical debt, auditing the repository for abandoned logical loops, when explicitly requested to scan for ambient architectural debt, or during PR review for fundamental architectural shifts.ai-agentsVotes: 0GitHub stars: 11
Ticket CreateAAuthoritative protocol for creating Neo.mjs GitHub issues. Enforces duplicate sweep, Fat Ticket body structure, strict label rules, title hygiene, and the six-stage challenge chain at creation time. CRITICAL: Do NOT run default `npx playwright test` to verify issues; Neo uses multiple custom playwright configs (e.g., unit, e2e) which must be explicitly targeted. Use immediately before calling the create_issue MCP tool. Triggers: Use this skill before any invocation of the create_issue MCP too...ai-agentsgitVotes: 0GitHub stars: 11
Ticket IntakeAAuthoritative protocol defining the \"Pre-Execution Reflection Gate\". Mandates architectural validation, negative ROI calculation, and duplicate sweeps before an agent is permitted to begin working on a GitHub Issue. Triggers: Use this skill immediately when assigned a ticket whose authoring you did NOT see, before checking out a branch or writing any codebase modifications. A ticket YOU authored this session is exempt EXCEPT the prescription check; one you authored in an earlier session run...ai-agentsgitVotes: 0GitHub stars: 11
Ticket TriageAAuthoritative protocol for maintainer-side label triage of unlabeled contributor tickets. Codifies the social contract for what happens when a ticket arrives without `ai`, primary (`bug`/`enhancement`/`epic`), or secondary labels. Triggers: Use this skill when an agent with maintainer permissions (`WRITE` permission or higher) encounters a ticket lacking `ai`, primary, or secondary labels — typically authored by a non-maintainer contributor or a lower-privileged agent who couldn't apply label...ai-agentsVotes: 0GitHub stars: 11
Turn Memory Pre FlightAAuthoritative protocol for verifying the correct placement and impact of new agentic memory substrate additions. Triggers: Use before inserting or mutating turn-loaded/skill-loaded memory substrate (`AGENTS.md`, `AGENTS_ATLAS.md`, `.agents/skills/**`, `.codex/CODEX.md`, `.claude/CLAUDE.md`, `.agents/ANTIGRAVITY_RULES.md`) to prevent future-session bias.ai-agentsVotes: 0GitHub stars: 11
Unit TestANeo.mjs Playwright unit-test author/executor workflow. Standard Playwright patterns will fail. Triggers: Use before writing, modifying, fixing, or explicitly running unit tests. Do not trigger solely because PR review inspects a diff containing, adding, or moving tests, or checks placement; pr-review owns review evidence.ai-agentsVotes: 0GitHub stars: 11
Update RoadmapARepeatable post-release beat — celebrate the shipped release, then plan the next roadmap as cornerstones + rationale (NOT an exhaustive list) + an explicit deferred set, scoped into a GitHub milestone with a named steward per epic. Triggers: a release ships (vX.Y merged to main); a maintainer says "scope the next release / plan the roadmap / what's in vNext"; or the post-release planning beat is neglected. Sibling to #10321 (release-cut: notes + publish).ai-agentsgitVotes: 0GitHub stars: 11
Video CreateAEvidence-first end-to-end video production workflow for narrated product films, demos, and campaign media. Triggers: planning, producing, revising, or delivering a video where claims, app choreography, voice, capture, composition, QA, publication, and artifact lineage must stay bound. ANTI-trigger: isolated image generation, standalone media conversion, or app testing with no film deliverable.ai-agentstestinggitVotes: 0GitHub stars: 11
Whitebox E2eAStandardized guide and protocol for authoring robust Whitebox End-to-End tests using the Neural Link Playwright fixture. CRITICAL: Neo.mjs uses Playwright in a highly custom way. Standard Playwright patterns will fail. Triggers: Use this skill before writing, modifying, or executing Playwright End-to-End tests, or if the user asks you to write an E2E test, add end-to-end coverage, or test a component holistically.ai-agentstestingVotes: 0GitHub stars: 11