Resolve timezone questions for .NET and C# code with production-safe guidance and copy-paste-ready snippets.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondotnet-timezoneExecute the skills CLI command in your project's root directory to begin installation:
Fetches dotnet-timezone from github/awesome-copilot and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate dotnet-timezone. Access via /dotnet-timezone in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
28.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
28.7K
stars
Resolve timezone questions for .NET and C# code with production-safe guidance and copy-paste-ready snippets.
Identify the request type first:
If the library is unclear, default to TimeZoneConverter for cross-platform work. If the scenario involves recurring schedules or strict DST rules, prefer NodaTime.
If the user provides an address, city, region, country, or document containing place names:
references/timezone-index.md for common Windows and IANA mappings.For each resolved location, provide:
Location: <resolved place>
Windows ID: <windows id>
IANA ID: <iana id>
UTC offset: <standard offset and DST offset when relevant>
DST: <yes/no>
Then include a cross-platform snippet like:
using TimeZoneConverter;
TimeZoneInfo tz = TZConvert.GetTimeZoneInfo("Asia/Colombo");
DateTime local = TimeZoneInfo.ConvertTimeFromUtc(DateTime.UtcNow, tz);
If multiple locations are present, include one block per location and then a combined multi-timezone snippet.
If a location is ambiguous, list the possible timezone matches and ask the user to choose the correct one.
Use references/timezone-index.md for Windows to IANA mappings.
Always provide both formats:
TimeZoneInfo.FindSystemTimeZoneById() on WindowsNodaTime, and TimeZoneConverterUse references/code-patterns.md and pick the smallest pattern that fits:
TimeZoneInfo for Windows-only codeTimeZoneConverter for cross-platform conversionNodaTime for strict timezone arithmetic and DST-sensitive schedulingDateTimeOffset for APIs and data transferAlways include package guidance when recommending third-party libraries.
Mention the relevant warning when applicable:
TimeZoneInfo.FindSystemTimeZoneById() is platform-specific for timezone IDs.DateTime.Now in databases; store UTC instead.DateTimeKind.Unspecified as a bug risk unless it is deliberate input.For address and location requests:
For code and architecture requests:
Keep responses concise and code-first.
references/timezone-index.md: common Windows and IANA timezone mappingsreferences/code-patterns.md: ready-to-use .NET timezone patternsMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
github/awesome-copilot
github/awesome-copilot
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
Keeps context tight: dotnet-timezone is the kind of skill you can hand to a new teammate without a long onboarding doc.
dotnet-timezone reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added dotnet-timezone from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
dotnet-timezone reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend dotnet-timezone for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: dotnet-timezone is the kind of skill you can hand to a new teammate without a long onboarding doc.
dotnet-timezone is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in dotnet-timezone — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for dotnet-timezone matched our evaluation — installs cleanly and behaves as described in the markdown.
dotnet-timezone fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 74