NITISH-R-G/hackerrank-orchestrate-skills
Skill Claude CodeCodex
Run the final release gate: fresh-clone simulation, artifact freshness, packaging hygiene, documentation accuracy. Use in the final hour. Catches the defects that make a working submission fail on someone else's machine.
NITISH-R-G/hackerrank-orchestrate-skills
Skill Claude CodeCodex
Defending an LLM agent against adversarial input — prompt injection, jailbreak attempts, ambiguous edge cases, and malformed model output — as an explicit design phase rather than a bug-fixing afterthought. Use when building any agent that processes untrusted or user-supplied input, when a challenge dataset is…
NITISH-R-G/hackerrank-orchestrate-skills
Skill Claude CodeCodex
Design a deterministic routing engine that is auditable and injection-immune. Use when choosing between rules and an LLM classifier, and when ordering rule tiers. Includes how to prove no rule is dead or shadowed.
NITISH-R-G/hackerrank-orchestrate-skills
Skill Claude CodeCodex
Build validation guardrails around every LLM-generated field before it reaches output.csv in a HackerRank Orchestrate submission — schema validation, rejecting unsupported label values, and retry-on-malformed-output. Use this whenever writing the code path that turns a model response into a CSV row, when an agent's…
NITISH-R-G/hackerrank-orchestrate-skills
Skill Claude CodeCodex
Enforce the two hard technical constraints HackerRank Orchestrate submissions are explicitly graded on — secrets only in environment variables (never hardcoded), and deterministic/seeded behavior for anything involving randomness or sampling. Use when writing configuration/setup code, when an agent's output changes…
NITISH-R-G/hackerrank-orchestrate-skills
Skill Claude CodeCodex
Attack your own submission across injection, unicode evasion, regex denial of service, path traversal, and malformed media. Use before release. Every failure path must degrade to a valid output rather than crash.
NITISH-R-G/hackerrank-orchestrate-skills
Skill Claude CodeCodex
Honestly estimating how a HackerRank Orchestrate submission (or similar multi-signal AI evaluation) would score across every rubric dimension before submitting, to find the weakest area while there's still time to fix it. Use before final submission of any Orchestrate-style challenge, or whenever the user asks "how…
NITISH-R-G/hackerrank-orchestrate-skills
Skill Claude CodeCodex
Verify a submission against the literal text of problemstatement.md rather than your memory of it — every column, every allowed value, every separator, every required artifact. Use before any release, and immediately after any change to output formatting. Catches the class of defect that costs points mechanically…
NITISH-R-G/hackerrank-orchestrate-skills
Skill Claude CodeCodex
Final pre-submission checklist for a HackerRank Orchestrate (or similar multi-artifact hackathon) submission — packaging, file format compliance, and the mechanical failure modes that lose points for reasons unrelated to your agent's quality. Use in the final phase before submitting, or whenever the user asks to do a…
NITISH-R-G/hackerrank-orchestrate-skills
Skill Claude CodeCodex
Prove the three submission artifacts are current, consistent, and correspond to the same commit. Use in the final hour, and after any change that touches production code. Catches stale outputs, which is the single most common silent submission defect.
NITISH-R-G/hackerrank-orchestrate-skills
Skill Claude CodeCodex
Score a chat transcript against HackerRank's published AI Chat Transcript rubric, and generate prompts that demonstrate the behaviors it rewards -- direction/ownership, technical specificity, iteration/verification, safety awareness. Use before submitting, or at the start of a build to prompt yourself better from turn…