all publishers

prime-radiant-inc

@prime-radiant-inc source repo

52 published skills

  1. ▌
    Tool Fluency 2 · prime-radiant-inc
    Use when designing, running, or diagnosing Evener tool-fluency experiments for a real built-in, plugin, or newly added tool. Covers probe manifests, model comparisons, semantic oracles, and interpreting fluency failures without ad-hoc transcript parsing.
    303 repo stars
  2. ▌
    Fuzzing An API Surface 2 · prime-radiant-inc
    Use when a surface parses untrusted or model-generated input — a wire protocol, tool-call JSON, upstream SSE, an HTTP body — or after a parser/dispatch bug, to fuzz that surface and turn any deterministic failure into a permanent, flake-guarded regression test. Covers picking a seam, choosing oracles beyond "no panic", the portable promoter/schema-generator core, and the safety bounds that keep a fuzzer from executing dangerous handlers.
    303 repo stars
  3. ▌
    Doctoring Evener 2 · prime-radiant-inc bundle
    Use when diagnosing a evener session, job, watch, or the session tree — investigating watch runaways (self-influence depth + runaway-fuse drops), dropped/coalesced deliveries, "how many times did X actually get called", stuck turns, or parent↔delegate↔observer linkage. Covers the evener doctor forensic tools, the Finding contract, runbook authoring, and graduated repair.
    303 repo stars
  4. ▌
    Using Ledger · prime-radiant-inc
    Use when work spans sessions or agents and needs durable, verifiable state — starting multi-session or multi-agent work, dispatching subagent fleets, resuming after context death, handing off, tracking an investigation, running an issue board, picking unblocked work, or deciding "should this be a ledger?". Teaches when and how to use the `chit` CLI's patterns; command mechanics live in `chit quickstart`.
    303 repo stars
  5. ▌
    Ledger Issues · prime-radiant-inc
    Use when working a shared ledger issue board — picking and claiming tasks, closing with evidence, breaking cycles, and reconciling contested state after sync.
    303 repo stars
  6. ▌
    Parallel Adversarial Review · prime-radiant-inc bundle
    Use when reviewing a diff, commit, branch, or implementation against a spec — dispatches two same-model reviewer subagents in parallel under a competitive scoring frame, then aggregates findings. Triggers on "review this", "PAR review", "adversarial review", or any evaluative gate (scope review, spec compliance, code quality, audit).
    303 repo stars
  7. ▌
    Multi Model Adversarial Review · prime-radiant-inc bundle
    Use for high-stakes review where you want multiple model providers reviewing the same artifact and critiquing each other. Shells out to installed coding-agent CLIs (claude, codex, gemini, pi, opencode by default; amp and droid available opt-in) to run parallel reviews, then runs a cross-critique grid where each reviewer evaluates the others' findings to catch hallucinations and severity inflation, then synthesizes a final deduplicated report. Triggers on "MMAR review", "multi-model review", "cross-model adversarial", "review with all the models", or when single-model PAR feels insufficient.
    303 repo stars
  8. ▌
    Tool Fluency · prime-radiant-inc
    Use when designing, running, or diagnosing Evener tool-fluency experiments for a real built-in, plugin, or newly added tool. Covers probe manifests, model comparisons, semantic oracles, and interpreting fluency failures without ad-hoc transcript parsing.
    303 repo stars
  9. ▌
    Fuzzing An API Surface · prime-radiant-inc
    Use when a surface parses untrusted or model-generated input — a wire protocol, tool-call JSON, upstream SSE, an HTTP body — or after a parser/dispatch bug, to fuzz that surface and turn any deterministic failure into a permanent, flake-guarded regression test. Covers picking a seam, choosing oracles beyond "no panic", the portable promoter/schema-generator core, and the safety bounds that keep a fuzzer from executing dangerous handlers.
    303 repo stars
  10. ▌
    Doctoring Evener · prime-radiant-inc bundle
    Use when diagnosing a evener session, job, watch, or the session tree — investigating watch runaways (self-influence depth + runaway-fuse drops), dropped/coalesced deliveries, "how many times did X actually get called", stuck turns, or parent↔delegate↔observer linkage. Covers the evener doctor forensic tools, the Finding contract, runbook authoring, and graduated repair.
    303 repo stars
  11. ▌
    Debug Run · prime-radiant-inc
    Use when a toil run has failed or produced unexpected results and you need to investigate what happened
    303 repo stars
  12. ▌
    Watch Run · prime-radiant-inc
    Use when monitoring an in-progress toil run, checking if a run is stuck, or observing live workflow execution
    303 repo stars
  13. ▌
    Building Workflows · prime-radiant-inc
    Use when writing, editing, validating, or debugging toil workflow YAML — node/edge structure, ForEach, decision tags, expression syntax (${workflow_input.X} vs ${input.X}, supported node fields, required ! refs), or analyzing why a run misbehaved
    303 repo stars
  14. ▌
    Auditing Progress · prime-radiant-inc bundle
    Use when an iteration has just finished and you need to verify behavior evidence quality in three tiers — deep evidence for current stories, impacted behavior for touched scenarios, and sentinel corpus for high-value regression detection.
    303 repo stars
  15. ▌
    Implementing Tasks · prime-radiant-inc bundle
    Use when executing a batch of TDD-sized tasks inside a running-an-iteration call — dispatches an implementer subagent per task following red-green-refactor discipline and returns per-task completion status.
    303 repo stars
  16. ▌
    Running An Iteration · prime-radiant-inc bundle
    Use when executing the next pending iteration from an iterative-development roadmap — picks the iteration, decomposes into code and evidence tasks, runs sentinel corpus baseline, dispatches implementing-tasks, runs impacted + sentinel scenarios, and updates artifacts.
    303 repo stars
  17. ▌
    Iterative Development · prime-radiant-inc
    Use when implementing a project with a large, comprehensive, or ambiguous spec — extracts requirements with proof obligations, defines a walking skeleton with its first journey scenario, then loops through audited sprints that continuously build a behavior evidence corpus. Completion means passing evidence, not just finished stories.
    303 repo stars
  18. ▌
    Extracting Requirements · prime-radiant-inc bundle
    Use when starting an iterative-development run on human spec collateral — reads the spec, produces per-epic requirement files with proof obligations and behavior scenario cards with stable IDs.
    303 repo stars
  19. ▌
    Scoping The Simplest Core · prime-radiant-inc bundle
    Use when turning extracted requirements into a roadmap — selects the walking skeleton iteration with its first journey scenario, orders remaining work into follow-on iterations, and applies story splitting when ACs have different dependency profiles.
    303 repo stars
  20. ▌
    Reading A Book · prime-radiant-inc bundle
    Use when reading a book, paper, RFC, long essay, or any sustained written work your human partner wants you to understand and apply later — when the goal is comprehension and durable use, not lookup or skim.
    303 repo stars
  21. ▌
    Holding Beliefs · prime-radiant-inc
    Use when catching yourself making a load-bearing claim you haven't named as a belief; unable to articulate why you're invoking a skill; noticing a defendable pattern across your own work; feeling unnamed resistance to a claim while reading; finishing a chapter, coherent argument, or zettel-extraction sweep; receiving a research subagent's report; hitting a debugging surprise or substantive pushback from your human partner; before committing to a substantive recommendation, plan, or extraction; or starting non-trivial work in a domain with prior beliefs.
    303 repo stars
  22. ▌
    Taking Smart Notes · prime-radiant-inc bundle
    Use when reading or working produces a durable insight worth keeping past the current session, when extracting ideas from a finished per-source note, or when a claim deserves a permanent home in the slip-box (atomic notes, zettels, Zettelkasten).
    303 repo stars
  23. ▌
    Writing From Notes · prime-radiant-inc
    Use when starting a substantive piece of writing — essay, summary, post, design doc, blog draft — where the topic has been encountered in past reading or work.
    303 repo stars
  24. ▌
    Learning From Experience · prime-radiant-inc
    Use mid-task when something procedurally interesting just happened — a skill's procedure didn't fit the situation, a novel approach worked, a failure-then-recovery taught something, a source or your human partner's critique bears on an existing skill, or a procedural surprise resists naming.
    303 repo stars
  25. ▌
    Reflecting On Experience · prime-radiant-inc
    Use at deliberate reflection moments — finishing significant work, unconsumed experience entries having accumulated in notes/experience/ since the last pass, a notable success or failure involving a skill, teaching forcing you to articulate what you do, or picking up a skill after time away.
    303 repo stars
  26. ▌
    Deliberating Under Ambiguity · prime-radiant-inc
    Use at decision points where the proposed action is non-trivial (high blast radius, hard reversibility, work that branches on early choices, or goal ambiguity) AND the situation is ambiguous — multiple interpretations or response shapes plausibly fit, or a recognition rubric flagged ambiguity.
    303 repo stars
  27. ▌
    Writing Skills From Learning · prime-radiant-inc bundle
    Use when you've just read a source (book, course, paper) that teaches a named procedure, technique, or move-sequence, and the procedural detail is fresh in working memory — or when a reflecting-on-experience pass has just concluded the experience log points at a missing skill.
    303 repo stars
  28. ▌
    Doc Research · prime-radiant-inc
    Public documentation extraction methodology. Search sequence (3 tiers), behavioral claim extraction rules, output structure, termination criteria, and gap analysis. Loaded by the analyzer agent for documentation research.
    303 repo stars
  29. ▌
    Binary Analysis · prime-radiant-inc
    Layer 1 methodology for extracting behavioral intelligence from compiled binaries, bytecode archives, managed assemblies, and bundled applications. Covers artifact identification, string extraction strategy, decompilation workflows, provenance requirements, and handoff to source code mode.
    303 repo stars
  30. ▌
    Git Archaeology · prime-radiant-inc
    Layer 1 skill for mining git history for behavioral intelligence. Repository overview, commit message mining, PR/MR description extraction, blame-based maintenance heat maps, issue tracker cross-referencing. Loaded by the analyzer agent during Layer 1.
    303 repo stars
  31. ▌
    Source Analysis · prime-radiant-inc
    Layer 1 skill for source code analysis — decompose any codebase into analyzable units, extract behavioral claims with provenance. Supports three target shapes (source tree, bundle, decompiled binary), with per-language grep patterns and analysis templates.
    303 repo stars
  32. ▌
    Analysis Pipeline · prime-radiant-inc
    Reverse engineering - multi-source product intelligence analysis with provenance tracking. Master methodology for all analysis agents.
    303 repo stars
  33. ▌
    Spec Sanitization · prime-radiant-inc
    Sanitizes analysis specs to remove implementation contamination while preserving provenance metadata. Run in SEPARATE SESSION after analysis, before implementation.
    303 repo stars
  34. ▌
    Contract Detection · prime-radiant-inc
    Layer 1 skill for parsing machine-readable API contracts. OpenAPI/Swagger, GraphQL, Protobuf/gRPC, and JSON Schema detection, extraction, and behavioral claim generation. Loaded by the analyzer agent during Layer 1.
    303 repo stars
  35. ▌
    Ecosystem Analysis · prime-radiant-inc
    Layer 1 skill for SDK and ecosystem analysis. SDK discovery strategy, behavioral extraction methodology, integration test mining, output formats. Loaded by the analyzer agent for SDK and ecosystem work.
    303 repo stars
  36. ▌
    Second Pass Review · prime-radiant-inc
    Independent audit of sanitized specs in workspace/output/. Three parallel LLM-based reviewer roles check structural leakage, content contamination, and behavioral completeness. Run AFTER Layer 5 sanitization, BEFORE implementation handoff.
    303 repo stars
  37. ▌
    Visual Exploration · prime-radiant-inc
    Layer 1 skill for browser automation and visual UX documentation. Initial reconnaissance, navigation mapping, interaction documentation, end-to-end flow capture, edge case exploration, screenshot methodology. Loaded by the analyzer agent during Layer 1.
    303 repo stars
  38. ▌
    Container Execution · prime-radiant-inc
    Infrastructure skill for containerized target execution. Runtime detection, container lifecycle, security restrictions, interaction patterns.
    303 repo stars
  39. ▌
    Fidelity Validation · prime-radiant-inc
    Cross-validates sanitized output specs against raw source specs to detect lost behavioral detail, dropped constants, missing features, or diluted precision. Run AFTER sanitization and AFTER contamination audit passes.
    303 repo stars
  40. ▌
    Runtime Observation · prime-radiant-inc
    Cross-cutting skill for runtime observation methodology. Five-phase observation discipline, container interaction patterns, observation record format, claim extraction, environment variation. Loaded by the analyzer agent for runtime observation roles.
    303 repo stars
  41. ▌
    Source Completeness · prime-radiant-inc
    Validates that all user-facing surfaces discovered in source code are captured in the behavioral specs. Catches coverage gaps where the analysis pipeline missed features, tools, env vars, CLI flags, or other behavioral interfaces. Run AFTER Layer 3 specs are written, BEFORE sanitization.
    303 repo stars
  42. ▌
    Test Suite Analysis · prime-radiant-inc
    Layer 1 skill for extracting behavioral intelligence from test suites. Framework detection, test code reading strategy, test execution strategy, behavioral claim extraction with Given/When/Then mapping, e2e vs unit value classification. Loaded by the analyzer agent during Layer 1.
    303 repo stars
  43. ▌
    Autonomous Discovery · prime-radiant-inc
    Layer 1 intelligence source discovery - auto-detect available sources, search for public information, negotiate with user, produce inventory manifest
    303 repo stars
  44. ▌
    Incremental Analysis · prime-radiant-inc
    Detect existing workspace, diff current sources against high water mark metadata, classify specs as unchanged/stale/orphaned/new, re-analyze only what changed. Activates automatically when /analyze finds an existing workspace.
    303 repo stars
  45. ▌
    Community Intelligence · prime-radiant-inc
    Layer 1 skill for community intelligence gathering. Search channels, extraction methodology, consensus analysis, version-aware behavioral changes, structural contamination guard. Loaded by the analyzer agent for community intelligence gathering.
    303 repo stars
  46. ▌
    Multi Source Synthesis · prime-radiant-inc
    Layer 2 synthesis methodology. Feature discovery, architecture reverse engineering, API extraction, cross-source synthesis with conflict resolution, module mapping. Transforms raw Layer 1 intelligence into structured synthesis documents. Loaded by the analyzer agent during Layer 2.
    303 repo stars
  47. ▌
    Provenance Methodology · prime-radiant-inc
    Cross-cutting provenance discipline. Citation format, confidence levels, source hierarchy, session capture. Loaded by every analysis agent.
    303 repo stars
  48. ▌
    Validation Methodology · prime-radiant-inc
    Cross-cutting validation discipline. Acceptance criteria format, definition of done checklists, quality gate criteria, verification methods. Loaded by every analysis agent.
    303 repo stars
  49. ▌
    Behavioral Spec Writing · prime-radiant-inc
    Layer 3 deep documentation methodology. Per-module behavioral specifications, external and behavioral integration contracts, behavior documentation, end-to-end user journey analysis. Transforms Layer 2 synthesis into implementable behavioral specifications. Loaded by the analyzer agent during Layer 3.
    303 repo stars
  50. ▌
    Linear · prime-radiant-inc
    Manage Linear issues. Use when asked about tasks, tickets, bugs, or Linear.
    303 repo stars
  51. ▌
    Writing Gauntlet Stories · prime-radiant-inc
    Use when writing or reviewing a Gauntlet story card. Establishes the calibration framing — outcomes, persona binding, observable acceptance criteria — and explicitly rules out wrong-shaped frames (Agile user stories, QA step-scripts, BDD Given/When/Then) so prior knowledge does not contaminate the card.
    303 repo stars
  52. ▌
    Proving It Works With A Movie · prime-radiant-inc bundle
    Use when asked for a demo, screencast, tutorial, walkthrough, or proof video of software actually running, when a reviewer needs to see a feature work rather than take your word for it, or when handing over any video artifact of app behavior
    303 repo stars