Chigurupati Nandan Sai
Community@Nandansai08
I am a Computer Science & Engineering undergraduate at the Indian Institute of Technology (ISM), Dhanbad (Batch of 2025–2029), originally from Hyderabad.
Agent Skills by Chigurupati Nandan Sai
Showing 118 vetted skills indexed across 1 GitHub repositories.
using-these-skills
Routes task types to the correct skill across 14 categories and enforces repo-wide workflow rules.
research-question-framing
Converts vague research topics into pinned, answerable questions with decision links and timeboxes.
citation-management
Organizes source capture, claim-to-citation binding, and link rot defense for auditable documents.
experiment-design
Design controlled experiments with hypotheses, confound hunting, randomization, and pre-registration to establish causation.
survey-design
Designs unbiased survey questionnaires with analysis plans, sampling honesty, and pilot testing.
literature-review
Surveys research literature into synthesis matrices with graded evidence and claim-weighted conclusions.
note-synthesis
Convert accumulated research and meeting notes into claim-based outlines for documents.
technology-evaluation
Evaluates libraries, frameworks, and tools for adoption through criteria, maintenance vitals, exit costs, and spikes.
source-credibility-check
Audit a single source or claim by tracing citations to their primary origin.
production-debugging
Diagnose live system failures using logs, metrics, and traces without a local repro.
on-call-handoff
Structures on-call rotation handoffs with a fixed template covering incidents, risks, and access checks.
alerting-design
Designs symptom-based alerts with SLO burn-rate thresholds and three-lane routing.
incident-triage
Structure the first fifteen minutes of a production incident with severity declaration, role assignment, and mitigation-first workflow.
blameless-postmortem
Writes blameless incident postmortems with timelines, contributing factors, and tracked action items.
capacity-planning
Forecasts system capacity against expected load using demand modeling, load testing, and headroom targets.
slo-definition
Defines service reliability targets by selecting SLIs, setting SLOs, and attaching error budget policies.
runbook-authoring
Writes operational runbooks with verify-mitigate-diagnose-escalate procedures for on-call incident responders.
spark-etl-debugging
Diagnose Spark job failures and slowdowns using Spark UI task-duration distributions.
data-cleaning-pipeline
Transforms messy raw data into analysis-ready datasets through scripted, reproducible cleaning stages.
exploratory-data-analysis
Profiles new datasets through grain, null, distribution, and relationship checks before analysis.
metric-definition
Define trustworthy business metrics with pinned definitions, edge-case rulings, and guardrail pairs.
data-pipeline-idempotency
Designs data pipelines that produce identical output state across any number of re-runs.
medallion-architecture-design
Designs bronze, silver, and gold lakehouse layers with promotion gates and read-path enforcement.
sql-query-optimization
Diagnose and optimize slow SQL queries using execution plans, index strategy, and predicate rewrites.
Frequently Asked Questions About Chigurupati Nandan Sai
FAQPage SchemaWhat tasks can I accomplish with Nandansai08's skill library?▼
The library covers 118 process skills across 14 categories: debugging production systems, designing SLOs and alerts, optimizing SQL and Spark jobs, writing unit and property-based tests, reviewing Terraform plans, threat modeling designs, running A/B test analysis, writing PRDs and ADRs, and career tasks like salary negotiation and interview preparation.
Who is the target audience for these skills?▼
Software engineers, SRE and on-call responders, data engineers, security reviewers, product managers, and engineering leads. Each skill targets practitioners executing real tasks — incident triage, code review, capacity planning, vendor evaluation — rather than beginners seeking tutorials or conceptual overviews.
How do I use these skills in a session?▼
Load the using-these-skills entry point first. It explains that skills are processes to follow, routes your task type to the correct skill across all 14 categories, and states repo-wide non-negotiables. Individual skills then trigger on natural phrases like 'review this PR' or 'design an experiment'.
What prerequisites or dependencies do these skills require?▼
No external dependencies are specified in the manifest. Skills are self-contained process documents. Some skills explicitly sequence others — for example, metric-definition precedes ab-test-analysis, exploratory-data-analysis precedes data-cleaning-pipeline, and incident-triage precedes production-debugging during outages.
Do these skills replace each other or overlap?▼
No. Each skill declares explicit NOT-boundaries to prevent overlap: literature-review maps fields while technology-evaluation ends in adopt/reject decisions; secure-code-review audits diffs while threat-modeling works on design diagrams; flaky-test-diagnosis finds one root cause while e2e-test-triage shapes the whole suite.