Cluster large log sets into likely issue groups, repeated signatures, and probable root-cause buckets. Use when logs are noisy and need fast pattern extraction.
Skills in this repository
00PrabalK00/claude-skills - Page 2
SkillsMP has collected 86 skills from 00PrabalK00/claude-skills. Open a skill to review its source and details.
00PrabalK00/claude-skillsShowing 40 of 86 collected skills.
Design factory, bench, or end-of-line validation procedures for hardware products. Use when defining manufacturing or production test coverage.
Turn goals, stakeholders, and open decisions into a tight meeting agenda with required outcomes. Use when planning a focused meeting.
Convert raw meeting notes, transcripts, or chat logs into decisions, action items, owners, due dates, risks, and follow-up questions. Use after syncs, planning sessions, retros, or stakeholder calls.
Plan and carry out technical migrations such as dependency upgrades, framework changes, runtime version bumps, routing changes, schema moves, or package reorganizations. Use when a system must transition safely with checklists, compatibility checks, and…
Validate mobile release readiness by checking build artifacts, versioning, store requirements, crash risk, config, and pre-ship blockers. Use before shipping iOS or Android releases.
Build a full internal or external newsletter from source notes, launches, events, and updates. Use when assembling recurring newsletters.
Add or improve logging, metrics, tracing, dashboards, and alert-ready instrumentation structure. Use when a service lacks visibility or incident triage is too hard.
Turn alert streams, incident notes, and partial diagnostics into a clean on-call handoff. Use during shift changes or unresolved incidents.
Draft point-by-point responses to reviewer comments using manuscript changes, evidence, and rebuttal structure. Use when responding to peer review.
Identify hot paths, bottlenecks, and likely performance wins from profiles, traces, benchmarks, and code hotspots. Use when an app is slow or a performance budget is being missed.
Run a lightweight personal operating system by reviewing tasks and notes, clustering priorities, drafting weekly plans, surfacing risks, and turning messy inputs into clear next actions. Use for weekly reviews, planning sessions, or personal task triage.
Convert transcripts into polished show notes, summaries, timestamps, and links. Use when preparing podcast publication materials.
Explain what changed between old and new policy documents and why the differences matter. Use when reviewing policy updates or compliance changes.
Review diffs like a senior engineer by checking correctness, architectural fit, style, missing tests, security smells, and migration or operational risk. Use when asked to review a pull request, patch, staged changes, or proposed code edits.
Draft polished client or stakeholder responses to proposals, questions, or requests using source notes and requirements. Use when a fast but professional response is needed.
Review SQL queries, execution plans, schema usage, and indexes to propose safer faster alternatives. Use when a database query is slow or causing load problems.
Plan and execute behavior-preserving refactors by identifying safe structural changes, staging edits incrementally, adding regression coverage, and validating outcomes. Use for legacy cleanup, module extraction, renames, or simplification where behavior must…
Generate human-readable release notes from commits, pull requests, tags, and changelog fragments. Use when preparing a release summary for users, customers, or internal teams.
Map unfamiliar repositories by identifying architecture, entry points, setup commands, environment variables, build and test workflows, ownership clues, and common traps. Use when entering a new codebase, preparing onboarding notes, or before making changes…
Gather and compare sources, extract key claims, note disagreements, flag uncertainty, and produce a concise cited brief. Use for technical research, market scans, literature reviews, or decision memos that need source-backed synthesis.
Tailor a resume package to a specific role by aligning experience, drafting role-specific bullets, creating a cover letter, outreach note, and interview story bank. Use for job applications, networking outreach, or interview preparation.
Structure strong answers for requests for proposal and vendor questionnaires from source material, policies, and product facts. Use when completing formal procurement responses.
Diagnose why a robot software stack will not bring up cleanly across environment, launch, hardware, and runtime dependencies. Use when robot bringup fails or stalls.
Inspect ROS 2 nodes, topics, services, actions, parameters, and live graph structure to explain what is running and how it is connected. Use when observing or validating a live ROS system.
Use this skill for ROS 2 workspaces, launch files, runtime graph debugging, topic or service or action decisions, parameter checks, rosbag workflows, TF issues, QoS diagnosis, ros2_control and Nav2 bringup checks, and safe ROS code or config changes. Best for…
Create operational runbooks from tribal knowledge, commands, logs, and recovery steps. Use when recurring incidents lack clean response docs.
Convert messy sales-call notes into structured CRM-ready entries with next steps, pain points, objections, and deal signals. Use when updating CRM after calls.
Structure scholarship essays from achievements, goals, and personal context into a clear narrative. Use when drafting or refining scholarship essays.
Find unsafe secret handling, config leakage, and risky environment-variable or file-based exposure patterns. Use when auditing configuration and secret hygiene.
Review systems for authentication and authorization gaps, secret handling problems, unsafe queries, insecure defaults, data exposure, dependency risk, and abuse paths. Use for code reviews, threat-focused audits, or pre-release security checks.
Create step-by-step calibration workflows, checks, and validation criteria for sensors and robot subsystems. Use when calibrating or revalidating hardware.
Map upstream and downstream service dependencies from config, code, environment variables, and network assumptions. Use when understanding system blast radius or ownership.
Compare simulation assumptions against real robot behavior, interfaces, timing, and environment differences. Use when code works in sim but fails on hardware.
Analyze SLAM and localization logs for mapping drift, sensor mismatch, TF issues, and timing or parameter failures. Use when mapping or localization is unstable.
Turn rough notes into a polished presentation, memo, report, or handout with a clear structure, narrative flow, supporting evidence, and audience-appropriate tone. Use when the user has bullets or fragments and needs a finished doc or deck.
Improve noisy, weak, or missing alert rules by inspecting SLOs, thresholds, burn-rate logic, and actionability. Use when alerting is too chatty or misses real issues.
Turn stack traces, tracebacks, and crash logs into likely root causes, suspect files, and next fixes. Use when a runtime failure needs fast explanation from terminal output or logs.
Turn large sets of support tickets into issue categories, trends, severity buckets, and ownership hints. Use when support volume needs synthesis.
Summarize open-text survey responses into themes, representative quotes, and notable outliers. Use when reviewing survey feedback.