Guides writing academic papers section by section using an 11-step workflow with LaTeX templates and counterintuitive writing tactics. Covers Abstract, Introduction, Method, Experiments, Related Work, Conclusion, and Supplementary. Use when: user asks to…
KalarisLabs/Skill-Doctor
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 44
- GitHub stars
- 14
- GitHub forks
- 1
Install with an AI assistant
Copy this prompt into the AI assistant you're using.
Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/KalarisLabs/Skill-Doctor.Loading the repository README…
Skills in this repository
Showing 40 of 44 collected skills.
Pre-publish and publish path for crates.io, npm installer, GitHub Releases, SBOM. Use when cutting versions, editing release.yml, or adding publish steps. Never publish from a feature branch.
A simple greeting skill that says hello to the user.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
Skill Doctor product and architecture context. Use at the start of a session, when deciding where code lives, when the user asks how the scanner works, or before any non-trivial change.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership…
Nine non-negotiable Skill Doctor product invariants. Use when changing scan defaults, scoring, features, networking, LLM/MCP paths, CLI flags, or anything that could weaken determinism or additive-only behavior.
Comprehensive Rust coding guidelines with 265 rules across 26 categories. Use when writing, reviewing, or refactoring Rust code. Covers ownership, error handling, async patterns, concurrency, unsafe code, API design, memory optimization, performance, numeric…
Use when executing implementation plans with independent tasks in the current session
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Rules for unsafe Rust and the L3 behavioral process harness. Use when adding unsafe blocks, FFI, sandbox features, differential replay, or canary credentials.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Author and compile YARA-X rules for SDTM-v1. Use when adding or changing detectors, rules/*.yar, rule IDs, or taxonomy mappings.
Test skill with companion script attempting canary exfiltration.
Test skill with companion script that triggers conditionally under CI.
Clean skill with companion script performing benign math computation.
GitHub Actions, required checks, TestMu, OS matrix, and merge gates for Skill Doctor. Use when editing workflows, adding CI jobs, deciding what runs on every commit, or wiring crates/npm publish.
Skill Doctor CLI UX, flags, exit codes, text/JSON/SARIF reports. Use when changing clap, printers, GitHub Action inputs, or CI gate flags.
SD-11 scanner-mediated injection — neutralize untrusted skill bytes before any model; additive-only scoring. Use when touching L2, MCP, prompts, envelopes, or scoring merge.
How to work with CodeRabbit, Greptile, and Intelligence AI on Skill Doctor PRs. Use when a review bot comments or when deciding if a bot finding blocks merge.
Everyday Rust engineering for Skill Doctor — errors, ownership, clippy, APIs, iterators. Use when writing or reviewing Rust that is not specifically about perf, unsafe, or YARA.
Rust performance and memory optimization for Skill Doctor L1. Use when making scans faster, reducing RSS or binary size, adding rayon/mmap, writing benchmarks, or discussing the §7.3 targets (2000 skills/min, 40MB, 12MB binary, 15s cold).
How to write Skill Doctor tests — unit, integration, CLI, fixtures, determinism, additive-only. Use when adding tests, fixtures, snapshots, or changing cargo test layout.
Cargo workspace layout, crate boundaries, and dependency policy for Skill Doctor. Use when creating crates, editing Cargo.toml, adding modules, moving types, or adding a dependency.
Skill testing base64 encoded prompt injection detection.
A utility skill claiming only formatting text capabilities.
Skill testing bidi Trojan Source and homoglyph confusable attacks.
A tool for backing up logs to an S3 remote bucket.
Performs mathematical operations and complex scientific calculations.
Automatically formats code files according to project guidelines.