Skip to content
Agentmart
Submit a tool

poc-development

Build a clearly identified .NET proof of concept or experiment to test technical feasibility.

Skill by dprakash2101

IndexedMIT★ 4
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/dprakash2101-poc-development

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Build a clearly identified .NET proof of concept or experiment to test technical feasibility. Use only when the user or repository context explicitly marks the work as POC, spike, prototype, or experimental.

Use cases: testing

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/poc-development

What's inside

Skill name
poc-development
Description
Build a clearly identified .NET proof of concept or experiment to test technical feasibility. Use only when the user or repository context explicitly marks the work as POC, spike, prototype, or experimental.
License
MIT
Instructions
11 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# POC development

Define the hypothesis, success criteria, time/scope boundary, and what evidence the experiment must produce. Build the smallest representative vertical slice and keep experimental code isolated from production paths where practical.

Unit tests and production hardening are optional for a POC. Prioritize executable evidence, integration feasibility, important constraints, and reproducible setup. Still avoid credentials, unsafe destructive actions, and unrelated repository changes.

Label shortcuts and unknowns: security, resilience, error handling, scalability, observability, migration, compatibility, operations, and test gaps. Do not silently classify ordinary work as a POC to avoid tests.

If the result is promoted to production, reassess architecture and contracts, remove shortcuts, add normal automated tests and validation, and review the result as production code rather than incrementally blessing the prototype.

Record hypothesis, setup, observed result and promotion blockers in a reproducible handoff. Reassess any shortcut before production adoption.

From dprakash2101/dotnet-production-agent-skills, MIT.

More from dprakash2101/dotnet-production-agent-skills

Signals

Stars
4
Forks
1
Open issues
0
Last commit (this folder)
Sep 20, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/dprakash2101/dotnet-production-agent-skills
Website
dprakash2101.github.io/dotnet-production-agent-skills/
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from dprakash2101

Cite this page

poc-development skill. Agent Mart. https://agentmart.dev/skills/dprakash2101-poc-development (last updated 2026-10-24)