Turn hunches into accepted results: worthiness score, evidence bar, research-to-rules. Use when vetting ideas. Not for QA; use night-market-validation-and-qa.
athola/claude-night-market
SkillsMP has collected 217 skills from athola/claude-night-market. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 217
- GitHub stars
- 327
- GitHub forks
- 35
Skills in this repository
Showing 40 of 217 collected skills.
Generates and self-executes a diff-derived test plan for a PR. Use when validating PR changes before merge. Do not use for code review; use sanctum:pr-review.
Curate the web-capture index. Use when the capture backlog grows, captures sit unprocessed at seedling/pending, or to surface stored research during work.
Shapes turns action-first: action leads, steps numbered, state restated. Use for ADHD-friendly output. Do not use to trim tokens; use response-compression.
Compresses verbose responses by removing filler and framing to save 200-400 tokens. Use when responses feel bloated or context is filling fast.
Bind loop 'done' to unfakeable gates. Use to harden egregore/herald loops or promote completion_integrity. Not for QA gates; use night-market-validation-and-qa.
Map open problems where this repo can advance SOTA. Use when scoping research. Do not use to run the campaign; use night-market-completion-integrity-campaign.
Recommends context compression strategies for bloated or quota-heavy sessions. Use when context feels sluggish or quota burns faster than expected.
Optimizes context window via MECW principles and memory tiering. Use when context exceeds 30% or before long multi-step tasks.
Orchestrates the QUALITY pipeline stage for egregore work items, running code review, unbloat, and test updates. Use when running quality checks before a PR.
Enforces validation and evidence before claiming work complete. Use before declaring implementation done, creating a PR, or submitting deliverables for review.
Audits Rust code for unsafe blocks, ownership issues, and Cargo dependency risks. Use when reviewing Rust code or before merging Rust changes.
Generates Makefiles with testing, linting, formatting, and automation targets. Use when starting a project or standardizing build automation.
Configures pre-commit hooks for linting, type checking, formatting, and testing. Use when setting up a new project or adding quality gates to an existing one.
Scaffolds new projects with git, CI/CD workflows, pre-commit hooks, and build config. Use when starting a new Python, Rust, or TypeScript project from scratch.
Configures GitHub Actions CI/CD workflows for testing, linting, and deployment. Use when setting up automation for a Python, Rust, or TypeScript project.
Automates desktop GUI workflows via computer use API with screenshot capture. Use when scripting GUI interactions or recording browser sessions for tutorials.
Detect friction signals; graduate patterns into rules. Use for session retrospectives.
Guide creating Claude Code hooks with security-first design. Use for validation and enforcement.
Select hook scope (plugin, project, global) by audience. Use when authoring a hook.
Evaluate hook security, performance, and SDK compliance. Use for audits.
Analyze and improve the improvement process. Use for detecting regressions and meta-optimization.
Build composable skill modules with hub-and-spoke loading. Use when token budget is tight.
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.
Provide reusable patterns for validation, error handling, scaffolding. Use for skill consistency.
Guide creating Claude Code skills with TDD and persuasion principles. Use for new skill development.
Audit Skill() refs; detect hubs, isolates, and dangling targets. Use when auditing skills.
Evaluate Claude skill quality through auditing. Use when reviewing or auditing skills.
Detects AI-generated writing patterns in prose. Use when reviewing docs for slop, vague language, or identity leaks before publishing.
Surface expert frameworks. Use when creating or evaluating skills, hooks, or agents.
Evaluate Claude Code rules in .claude/rules/. Use for frontmatter, globs, and quality audits.
Test skills via TDD in fresh subagents. Use when validating behavior or preventing bias.
Applies client-server architecture for web/mobile apps. Use when designing systems with centralized backend services, trust boundaries, or offline-first sync.
Applies pipes-and-filters for sequential data transformations. Use when data flows through discrete stages like ETL, streaming analytics, or CI/CD pipelines.
Selects and routes to the right architecture paradigm. Use when choosing patterns for a new system or comparing trade-offs before making architecture decisions.
Selects architecture paradigm via research before scaffolding. Use when architecture is undecided and the choice needs justification and documentation.
Assesses decision reversibility and risk at critical checkpoints. Use when a workflow reaches a high-stakes branch needing escalation check.
Generates a Mermaid architecture diagram showing high-level component relationships. Use when visualizing how plugins or modules fit together.
Traces execution paths through the code graph with criticality scoring and Mermaid charts. Use when understanding how a function propagates through the system.
Generates a Mermaid class diagram showing types, inheritance, and composition. Use when visualizing class hierarchies or documenting a module public API.