AgentStack
SKILL verified MIT Self-run

Aigent Builder

skill-wkusnierczyk-aigent-skills-aigent-builder · by wkusnierczyk

>

No reviews yet
0 installs
3 views
0.0% view→install

Install

$ agentstack add skill-wkusnierczyk-aigent-skills-aigent-builder

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Aigent Builder? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

AIgent Builder

Generates complete AI agent skill definitions from natural language purpose descriptions. Produces a valid SKILL.md file with YAML frontmatter and structured Markdown body following the Anthropic agent skill best practices.

When to Use

Use this skill when:

  • The user asks to create, build, or generate a new agent skill
  • The user describes functionality they want to package as a skill
  • The user wants to scaffold a new SKILL.md file

Instructions

Step 1: Detect aigent availability

Run the following to check if the aigent CLI is installed:

command -v aigent

Step 2a: With aigent (primary mode)

If aigent is on PATH, use the CLI for authoritative skill generation:

  1. Build the skill:

``bash aigent build "" --dir .claude/skills ``

Additional options:

  • --name — override the derived skill name
  • --license — set a license (e.g., MIT)
  • --compatibility — set compatibility (e.g., claude)
  • --allowed-tools — set allowed tools (e.g., Bash, Read, Write)
  • --no-llm — force deterministic mode (no API key required)

If ANTHROPIC_API_KEY is set, aigent build uses Claude to generate richer names, descriptions, and body content. Without an API key, it falls back to deterministic generation automatically.

  1. Validate the output:

``bash aigent validate .claude/skills/ ``

Exit code 0 means valid. Any errors are printed to stderr.

  1. Report the output directory path and any warnings to the user.

Step 2b: Without aigent (fallback mode)

If aigent is not available, generate the skill manually using the Anthropic spec:

  1. Derive a skill name from the user's purpose:
  • Convert to kebab-case (lowercase, hyphens between words)
  • Use gerund form for the verb (e.g., "process" becomes "processing")
  • Maximum 64 characters
  • Must not contain reserved words: anthropic, claude
  • No leading, trailing, or consecutive hyphens
  1. Write the SKILL.md with this structure:

```markdown --- name: description: . Use when . --- #

## When to Use

Use this skill when:

## Instructions

```

Rules for the description:

  • Write in third person ("This skill processes..." not "Process...")
  • Include a "Use when..." clause for auto-invocation triggers
  • Maximum 1024 characters
  • No XML-like tags (``)
  1. Write to .claude/skills//SKILL.md using the Write tool (or a user-specified directory).
  1. Inform the user that validation was not run because aigent is not installed. Recommend installing it for authoritative validation.

Output location

The default output directory is .claude/skills// (project-local skills). The user may specify an alternative directory. Both CLI mode and fallback mode use the same default.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.