Agent skill · Security

azure-notification-hubs

Expert knowledge for Azure Notification Hubs development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and integrations & coding patterns. Use when integrating APNS/FCM/WNS, configuring PNS creds, using REST/SDKs, Private Link, or scheduled pushes, and other Azure Notification Hubs related development tasks. Not for Azure Event Hubs (use azure-event-hubs), Azure Service Bus (use azure-service-bus), Azure Web PubSub (use azure-web-pubsub), Azure SignalR Service (use azure-signalr-service).

MicrosoftDocsgithub.com/MicrosoftDocsGitHub ↗
claude-codecopilotcodexCC-BY-4.0
Install
npx skills add MicrosoftDocs/Agent-Skills --skill azure-notification-hubs --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 13 KB
Bundled scripts: none
Requires: Requires network access. Uses mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve documentation.
Path: skills/azure-notification-hubs/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 682 · +8 this week
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Azure Notification Hubs Skill This skill provides expert guidance for Azure Notification Hubs. Covers troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and integrations & coding patterns. It combines local quick-reference content with remote documentation fetching capabilities. ## How to Use This Skill > **IMPORTANT for Agent**: Use the **Category Index** below to locate relevant sections. For categories with line ranges (e.g., `L35-L120`), use `read_file` with the specified lines. For categories with file links (e.g., `[security.md](security.md)`), use `read_file` on the linked reference file > **IMPORTANT for Agent**: If `metadata.generated_at` is more than 3 months old, suggest the user pull the latest version from the repository. If `mcp_microsoftdocs` tools are not available, suggest the user install it: [Installation Guide](https://github.com/MicrosoftDocs/mcp/blob/main/README.md) This skill requires **network access** to fetch documentation content: - **Preferred**: Use `mcp_microsoftdocs:microsoft_docs_fetch` with query string `from=learn-agent-skill`. Returns Markdown. - **Fallback**: Use `fetch_we

What's inside
Steps it walks through
  1. How to Use This Skill
  2. Category Index
  3. Troubleshooting
  4. Best Practices
  5. Decision Making
  6. Architecture & Design Patterns
  7. Limits & Quotas
  8. Security
  9. Configuration
  10. Integrations & Coding Patterns
More from Agent-Skills
All skills →
About this skill
What does the azure-notification-hubs skill do?

Expert knowledge for Azure Notification Hubs development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and integrations & coding patterns. Use when integrating APNS/FCM/WNS, configuring PNS creds, using REST/SDKs, Private Link, or scheduled pushes, and other Azure Notification Hubs related development tasks. Not for Azure Event Hubs (use azure-event-hubs), Azure Service Bus (use azure-service-bus), Azure Web PubSub (use azure-web-pubsub), Azure SignalR Service (use azure-signalr-service).

How do I install it?

Run `npx skills add MicrosoftDocs/Agent-Skills --skill azure-notification-hubs --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From MicrosoftDocs/Agent-Skills, a repository with 682 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going