Source profileQuality 92/100

Benknightdark/neo-skills/skills/neo-dotnet-tag-helper/SKILL.md

neo-dotnet-tag-helper

Use this skill when the user asks to design, implement, refactor, or review custom ASP.NET Core Tag Helpers in C#, including TagBuilder usage, strongly typed attributes, dependency injection, ProcessAsync, and reusable Razor UI behavior.

Source repository stars: 7
Declared platforms: 0
Static risk flags: 0
Last source update: 2026-08-05
Source checked: 2026-08-05

Decision Compatibility Install Workflow Permissions Evidence Source

Decision brief

What it does—and where it fits

NET Core Tag Helpers in C#, including TagBuilder usage, strongly typed attributes, dependency injection, ProcessAsync, and reusable Razor UI behavior.

Best for

Use this skill when the user asks to design, implement, refactor, or review custom ASP.

Not for

Tasks that require unconfirmed production actions or broad system permissions.
Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

Platform	Status	Evidence	What to check
Codex	Not declared	No explicit evidence	Portability before use
Claude Code	Not declared	No explicit evidence	Portability before use
Cursor	Not declared	No explicit evidence	Portability before use
Gemini CLI	Not declared	No explicit evidence	Portability before use

Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource

npx skills add https://github.com/Benknightdark/neo-skills --skill "skills/neo-dotnet-tag-helper"

Safe inspection promptEditorial

Inspect the Agent Skill "neo-dotnet-tag-helper" from https://github.com/Benknightdark/neo-skills/blob/c3e3d1bcf6aae00a729ceab257e6a68dd40d89ec/skills/neo-dotnet-tag-helper/SKILL.md at commit c3e3d1bcf6aae00a729ceab257e6a68dd40d89ec. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

01
Workflow (Generator Pattern)
Follow these steps exactly to create robust, high-performance C Tag Helpers.
Target HTML Tag: What is the name of the custom tag in HTML? (e.g., , )Properties: What parameters/attributes should this tag accept? (e.g., theme, is-active, user-id)Dependencies (DI): Does this tag need to query a database or call a service? (Needs Dependency Injection)
02
Step 1: Perceive & Gather Requirements (Inversion)
Before writing any code, ask the user to clarify the following if not already provided: 1. Target HTML Tag: What is the name of the custom tag in HTML? (e.g., , ) 2. Properties: What parameters/attributes should this tag accept? (e.g., theme, is-active, user-id) 3. Dependencies…
Target HTML Tag: What is the name of the custom tag in HTML? (e.g., , )Properties: What parameters/attributes should this tag accept? (e.g., theme, is-active, user-id)Dependencies (DI): Does this tag need to query a database or call a service? (Needs Dependency Injection)
03
Step 2: Reason & Design (Planning)
Based on the answers: - Class Naming: Ensure the class name ends with TagHelper (e.g., MyButtonTagHelper). - Target Element: Apply [HtmlTargetElement("my-button")]. - Properties: Map HTML kebab-case attributes to C PascalCase properties. Apply [HtmlAttributeName("is-active")] if…
Class Naming: Ensure the class name ends with TagHelper (e.g., MyButtonTagHelper).Target Element: Apply [HtmlTargetElement("my-button")].Properties: Map HTML kebab-case attributes to C PascalCase properties. Apply [HtmlAttributeName("is-active")] if necessary.
04
Step 3: Act (Code Generation)
Generate the complete C class. Strictly adhere to the following rules: 1. Inherit from Microsoft.AspNetCore.Razor.TagHelpers.TagHelper. 2. Do NOT generate .cshtml files. All HTML must be constructed using TagBuilder inside the C class. 3. If ViewContext is needed, use [ViewConte…
Inherit from Microsoft.AspNetCore.Razor.TagHelpers.TagHelper.Do NOT generate .cshtml files. All HTML must be constructed using TagBuilder inside the C class.If ViewContext is needed, use [ViewContext] and [HtmlAttributeNotBound].

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial

Signal	Value	Evidence type	Meaning
Quality score	92/100	Computed	Documentation, specificity, maintenance, and trust rules
Repository stars	7	Source	Repository attention, not individual Skill quality
Compatibility	0 platforms	Source	Declared in the catalog source record
Usage guide	automated source guide	Editorial	Generated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository: Benknightdark/neo-skills
Skill path: skills/neo-dotnet-tag-helper/SKILL.md
Commit: c3e3d1bcf6aae00a729ceab257e6a68dd40d89ec
License: MIT
Collected: 2026-08-05
Default branch: main

View the original SKILL.md

.NET Tag Helper Expert Skill

Trigger On

The user requests to create, generate, or design a custom Razor Tag Helper in C#.
The user wants to encapsulate complex HTML/UI logic into reusable custom tags without using Partial Views or CSHTML.
The target framework is .NET 6.0 (LTS) and above.

Workflow (Generator Pattern)

Follow these steps exactly to create robust, high-performance C# Tag Helpers.

Step 1: Perceive & Gather Requirements (Inversion)

Before writing any code, ask the user to clarify the following if not already provided:

Target HTML Tag: What is the name of the custom tag in HTML? (e.g., <my-button>, <user-card>)
Properties: What parameters/attributes should this tag accept? (e.g., theme, is-active, user-id)
Dependencies (DI): Does this tag need to query a database or call a service? (Needs Dependency Injection)
Context: Does it need to access ViewContext (e.g., to generate URLs or check model state)?

Step 2: Reason & Design (Planning)

Based on the answers:

Class Naming: Ensure the class name ends with TagHelper (e.g., MyButtonTagHelper).
Target Element: Apply [HtmlTargetElement("my-button")].
Properties: Map HTML kebab-case attributes to C# PascalCase properties. Apply [HtmlAttributeName("is-active")] if necessary.
Method Selection:
- If no IO/Async operations, override Process.
- If using DI for database/API calls, override ProcessAsync.

Step 3: Act (Code Generation)

Generate the complete C# class. Strictly adhere to the following rules:

Inherit from Microsoft.AspNetCore.Razor.TagHelpers.TagHelper.
Do NOT generate .cshtml files. All HTML must be constructed using TagBuilder inside the C# class.
If ViewContext is needed, use [ViewContext] and [HtmlAttributeNotBound].
Manage content properly using output.TagName, output.Attributes.SetAttribute, and output.Content.SetHtmlContent.
Ensure Thread-Safety (do not store request-specific state in instance fields unless injected as scoped/transient).

Step 4: Validate (Quality Check)

Review the generated code against these criteria before presenting it:

Are all properties strongly typed?
Is TagBuilder used instead of string concatenation for HTML elements?
Is ProcessAsync used correctly if awaiting tasks?

Deliverable

Present the C# code wrapped in a markdown code block. Briefly explain how to register it in _ViewImports.cshtml (e.g., @addTagHelper *, YourAssemblyName).

Documentation

Official References

Internal References

Alternatives

Compare before choosing

Computed 976

mgiovani/cc-arsenal

team-review

Multi-agent review team: architecture, security, performance, testing, style, docs/UX, plus an adversary that cross-examines the other 6, for security-sensitive, architectural, or large PRs (15+ files) where a single-agent pass risks missing cross-cutting issues. Use for auth/payments/PII changes, schema/pattern changes, compliance sign-off, or when asked to 'get the review team on this' / 'multi-agent review' / 'thorough review before merge'. For a standard PR or a quick pre-merge check, use /r

Computed 9438,502

wshobson/agents

brand-landingpage

Brand-first landing page designer — runs a brand-identity interview (colors, typography, shape language), then generates and iterates on a polished landing page via Stitch with deployment-ready HTML. Use when the user asks to create, design, or build a landing page, homepage, or marketing page and has no established visual direction. Skip when they have a design mockup, need a dashboard or app UI, are working at component level, building a multi-page app, or restyling with known design tokens —

Computed 9279,318

bytedance/deer-flow

code-documentation

Use this skill when the user requests to generate, create, or improve documentation for code, APIs, libraries, repositories, or software projects. Supports README generation, API reference documentation, inline code comments, architecture documentation, changelog generation, and developer guides. Trigger on requests like "document this code", "create a README", "generate API docs", "write developer guide", or when analyzing codebases for documentation purposes.

Computed 916

mgiovani/cc-arsenal

team-implement

Spec-driven team orchestration for large, multi-component features or new epics: writes a full spec/design/review artifact trail under .specs/, gates code changes behind an explicit user approval, then scales a team from 3 (lite) to roughly 9 (full) agents based on complexity. Use for sizable features spanning frontend+backend+DB, unfamiliar domains, or anything you want a reviewable spec for before code is touched. Not for small/single-component changes (use implement-feature, no spec overhead)