AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
Parser development — grammar, bindings, tests, CLI, and docs
Install Parser Dev
$ npx skills add agentopology/agentopology --skill parser-dev -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install agentopology/agentopology parser-dev --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/agentopology/agentopology.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/parser-dev .claude/skills/parser-dev && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "parser-dev" agent skill from https://github.com/agentopology/agentopology/tree/main/.claude/skills/parser-dev into .claude/skills/parser-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parser-dev", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/agentopology/agentopology/tree/main/.claude/skills/parser-devType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add agentopology/agentopology --skill parser-dev -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install agentopology/agentopology parser-dev --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentopology/agentopology.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/parser-dev .agents/skills/parser-dev && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "parser-dev" agent skill from https://github.com/agentopology/agentopology/tree/main/.claude/skills/parser-dev into .agents/skills/parser-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parser-dev", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add agentopology/agentopology --skill parser-dev -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install agentopology/agentopology parser-dev --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentopology/agentopology.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/parser-dev .cursor/skills/parser-dev && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "parser-dev" agent skill from https://github.com/agentopology/agentopology/tree/main/.claude/skills/parser-dev into .cursor/skills/parser-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parser-dev", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/agentopology/agentopology.git --path .claude/skills/parser-dev--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add agentopology/agentopology --skill parser-dev -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install agentopology/agentopology parser-dev --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentopology/agentopology.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/parser-dev .gemini/skills/parser-dev && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "parser-dev" agent skill from https://github.com/agentopology/agentopology/tree/main/.claude/skills/parser-dev into .gemini/skills/parser-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parser-dev", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install agentopology/agentopology parser-devInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add agentopology/agentopology --skill parser-dev -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/agentopology/agentopology.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/parser-dev .github/skills/parser-dev && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "parser-dev" agent skill from https://github.com/agentopology/agentopology/tree/main/.claude/skills/parser-dev into .github/skills/parser-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parser-dev", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add agentopology/agentopology --skill parser-dev -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install agentopology/agentopology parser-dev --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentopology/agentopology.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/parser-dev .opencode/skills/parser-dev && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "parser-dev" agent skill from https://github.com/agentopology/agentopology/tree/main/.claude/skills/parser-dev into .opencode/skills/parser-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parser-dev", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
parser-dev- GitHub stars
- 103
- Token cost
- ~401 tokens
- SKILL.md length
- 120 words
- Files
- 4 (incl. scripts)
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Parser development — grammar, bindings, tests, CLI, and docs
- Tasks that involve Infrastructure as code
- SKILL.md covers Orchestrator, Flow, Gates and Triggers
- Runs Shell scripts from its folder
What it does
Parser Dev is an agent skill from agentopology/agentopology. Parser development — grammar, bindings, tests, CLI, and docs
Its SKILL.md is about 400 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts (for example `scripts/validate-examples.sh`).
It sits in Knowledge Management, covering Infrastructure as code. It works with Model Context Protocol, Terraform, TypeScript and Obsidian. The repository describes itself as: Harness as code — the Terraform for AI agents. Define your agent team AND its memory once, deploy to Claude Code, OpenClaw, Cursor, Codex, Gemini, Copilot, Kiro. Declarative .at… The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Infrastructure as code
Example prompts
- “/parser-dev”
Requirements
- Node.js
- A Bash shell
What it can do on your machine
Read from SKILL.md and the folder at commit 9a0f0c8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 2 files in scripts/ (Shell), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Parser Dev loads about 401 tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 120 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from agentopology/agentopology at commit 9a0f0c8, republished under its Apache-2.0 licence (© agentopology). 120 words, ~401 tokens.
Download SKILL.mdSave it as
.claude/skills/parser-dev/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- parser-dev
- description
- Parser development — grammar, bindings, tests, CLI, and docs
- version
- 1.0.0
- topology
- parser-dev
- patterns
- pipeline, fan-out
- entry
- commands/grammar.md
Parser Dev Topology Skill
Parser development — grammar, bindings, tests, CLI, and docs
Version: 1.0.0 Patterns: pipeline, fan-out
Orchestrator
Model: opus Handles: develop-grammar, develop-binding, develop-tests, develop-cli, develop-docs, validate-all Generates: commands/parser-dev.md
Flow
- develop-grammar -> grammar-engineer
- grammar-engineer -> test-engineer [when grammar-engineer.status == needs-tests]
- grammar-engineer -> doc-writer [when grammar-engineer.status == done]
- develop-binding -> binding-engineer
- binding-engineer -> test-engineer [when binding-engineer.status == needs-tests]
- binding-engineer -> doc-writer [when binding-engineer.status == done]
- develop-tests -> test-engineer
- develop-cli -> cli-engineer
- cli-engineer -> test-engineer [when cli-engineer.status == needs-tests]
- cli-engineer -> doc-writer [when cli-engineer.status == done]
- develop-docs -> doc-writer
- validate-all -> test-engineer
Gates
Type Check
After: grammar-engineer Before: test-engineer Run: npx tsc --noEmit On fail: bounce-back
Example Validation
After: test-engineer Run: scripts/validate-examples.sh On fail: halt
Triggers
/grammar
Pattern: /parser grammar
/binding
Pattern: /parser binding
/test
Pattern: /parser test
/cli
Pattern: /parser cli
/docs
Pattern: /parser docs
/validate
Pattern: /parser validate
© agentopology, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts) in .claude/skills/parser-dev of agentopology/agentopology.
- SKILL.md
- runs/.gitkeep
- scripts/npx
- scripts/validate-examples.sh
Open the folder on GitHubat commit 9a0f0c8
Compare with similar skills
Parser Dev next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Parser Dev this skillagentopology/agentopology | 103 | — | ~401 | Automated safety check: Pass | Apache-2.0 | |
| AWS Cdk Developmentzxkane/aws-skills | 367 | 2 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Terravision Cloud Diagramspatrickchugh/terravision | 1.6k | — | ~5.6k | Automated safety check: Notes | AGPL-3.0-only | |
| Infra Syncagentic-community/mcp-gateway-registry | 964 | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Eks Best Practicesaws-samples/appmod-blueprints | 113 | — | ~5k | Automated safety check: Pass | MIT-0 | |
| AWS Sst Developmentzxkane/aws-skills | 367 | — | ~2.7k | Automated safety check: Warn | MIT |
Similar skills
Terravision Cloud Diagrams
patrickchugh/terravision
Draw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision.
Infra Sync
agentic-community/mcp-gateway-registry
Keep Terraform and CDK infrastructure in sync. An agent skill from agentic-community/mcp-gateway-registry.
- Official
Eks Best Practices
aws-samples/appmod-blueprints
Advisory guidance for Amazon EKS architecture and configuration decisions — compute strategy, networking, security, reliability, cost, autoscaling, observability, multi-tenancy, and upgrade planning.
AWS Sst Development
zxkane/aws-skills
SST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework.
- Official
Google Cloud Storage Basics
google/skills
Stores, retrieves, and manages data as objects in Cloud Storage on Google Cloud (also known colloquially as GCS) buckets.
More from agentopology/agentopology
Agentopology Skill
agentopology/agentopology
Design, validate, scaffold, and visualize multi-agent topologies using the .at language
Related
Categories
Questions about Parser Dev
What does Parser Dev do?
Parser development — grammar, bindings, tests, CLI, and docs. Parser Dev is an agent skill from agentopology/agentopology.
When should I use Parser Dev?
Parser Dev fits situations like: tasks that involve Infrastructure as code.
How do I install Parser Dev in Claude Code?
Run `npx skills add agentopology/agentopology --skill parser-dev -a claude-code`. Or copy the skill folder (.claude/skills/parser-dev in agentopology/agentopology) into .claude/skills/parser-dev in your project. Claude Code loads it when a task matches its description.
How do I install Parser Dev in Codex?
Run `npx skills add agentopology/agentopology --skill parser-dev -a codex`. Or copy the skill folder (.claude/skills/parser-dev in agentopology/agentopology) into .agents/skills/parser-dev in your project. Codex loads it when a task matches its description.
Can I use Parser Dev in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add agentopology/agentopology --skill parser-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/parser-dev, .gemini/skills/parser-dev, .github/skills/parser-dev and .opencode/skills/parser-dev in your project.
What does Parser Dev need to run?
Going by SKILL.md and its folder, Parser Dev needs a shell for the scripts in its folder. Our summary lists: Node.js; A Bash shell.
Does Parser Dev access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Parser Dev safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Parser Dev use?
Parser Dev is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Parser Dev use?
About 401 tokens (SKILL.md is roughly 1.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Parser Dev?
Skills that share tags, products or a category with Parser Dev: AWS Cdk Development (zxkane/aws-skills, 367 stars), Terravision Cloud Diagrams (patrickchugh/terravision, 1.6k stars), Infra Sync (agentic-community/mcp-gateway-registry, 964 stars) and Eks Best Practices (aws-samples/appmod-blueprints, 113 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Parser Dev?
agentopology (a GitHub organization) maintains it in agentopology/agentopology, which has 103 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 27, 2026.
Source: agentopology/agentopology on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.