Awesome Azd Template Submit Agent Skill

>- Submit an azd template to the awesome-azd gallery. Use when asked to submit, add, or contribute a template to awesome-azd. Requires only a GitHub repository URL — all metadata (title, description, languages, frameworks, Azure services, IaC) is auto-detected by the submission pipeline.

770 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

262

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/Azure/awesome-azd --skill awesome-azd-template-submit

The instruction itself

10 sections, as written by the author

Awesome AZD Template Submission

You submit azd templates to the awesome-azd gallery by filing a GitHub issue

that triggers the automated submission pipeline. Given a repository URL, you

create the issue — everything else is auto-detected from the repository.

Usage

The user provides a repository URL. That's it.

Submit this template: https://github.com/Azure-Samples/my-ai-app

Steps

1. Validate the URL

Confirm the URL points to a valid GitHub repository

(https://github.com/{owner}/{repo}). If the URL is malformed or missing, ask

the user to provide one.

2. Extract the repo name for the issue title

Parse {owner}/{repo} from the URL to use in the issue title.

3. Confirm with the user

Show the user the issue title and source URL. This is a write operation —

require explicit approval before executing gh issue create.

4. File the issue

Use the GitHub CLI to create an issue in the Azure/awesome-azd repository.

The issue body must use ### Heading format matching the issue form fields so

the automated parser can extract the values.

Only the Source Repository field is required. All other fields are

auto-detected by the pipeline. Do NOT fill in optional fields unless the user

explicitly provides overrides.

gh issue create \
  --repo Azure/awesome-azd \
  --title "[Template]: {repo-name}" \
  --body "### Source Repository

{url}

### Template Title

_No response_

### Description

_No response_

### Author

_No response_

### Author URL

_No response_

### Author Type

_No response_

### Preview Image URL

_No response_

### IaC Provider

_No response_

### Languages

_No response_

### Frameworks

_No response_

### Azure Services

_No response_

### Additional Information

_No response_"

5. Confirm success

After filing, report the issue URL and explain that:

A maintainer will review and add the template-submission label to trigger

processing

The pipeline auto-extracts metadata, validates the repo, and creates a PR
The user will be notified on the issue when the PR is ready for review

Handling user overrides

If the user provides additional context like language, framework, or Azure

services, include those in the appropriate fields instead of _No response_.

Example:

Submit https://github.com/Azure-Samples/my-app with language python and services openai, aca

Would fill in:

Languages: python
Azure Services: openai, aca

Important

Always get user confirmation before filing the issue (show the title and URL)
The template-submission label is NOT auto-applied — a maintainer must add it
This is a write operation — require explicit approval before executing

Other skills for the same job

different authors, same section of the catalogue

Modal

by christophacham

×3

Run Python code in the cloud with serverless containers, GPUs, and autoscaling. Use when deploying ML models, running batch processing jobs, scheduling compute-intensive tasks, or serving APIs that require GPU acceleration or dynamic scaling.

17k tokens

Github Workflow Automation

by ComeOnOliver

×3

Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management

Google Cloud Platform CLI - manage GCP resources including Compute Engine, Cloud Run, GKE, Cloud Functions, Storage, BigQuery, and more.

Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC APIs, event-driven architectures, service mesh patterns, and modern backend frameworks. Handles service boundary definition, inter-service communication, resilience patterns, and observability. Use PROACTIVELY when creating new backend services or APIs.

Aspire skill covering the Aspire CLI, AppHost orchestration, service discovery, integrations, MCP server, VS Code extension, Dev Containers, GitHub Codespaces, templates, dashboard, and deployment. Use when the user asks to create, run, debug, configure, deploy, or troubleshoot an Aspire distributed application.

21k tokens

Bigquery Pipeline Audit

by github

vendor ×1

Audits Python + BigQuery pipelines for cost safety, idempotency, and production readiness. Returns a structured report with exact patch locations.

Microsoft Store Developer CLI (msstore) for publishing Windows applications to the Microsoft Store. Use when asked to configure Store credentials, list Store apps, check submission status, publish submissions, manage package flights, set up CI/CD for Store publishing, or integrate with Partner Center. Supports Windows App SDK/WinUI, UWP, .NET MAUI, Flutter, Electron, React Native, and PWA applications.

4k tokens

How to use it

Copy the folder

Take azure/awesome-azd-template-submit from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.