How do I install the Author Iac skill?

Run npx skillmds@latest add poly-gents/author-iac in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Author Iac skill do?

Write infrastructure-as-code modules and templates It is listed under Coding & Dev Tools on SkillMD.

Is Author Iac safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Author Iac?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Author Iac free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Author Iac?

poly-gents (@poly-gents) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Author Iac by poly-gents — Agent Skill

Name: Author Iac
Author: poly-gents

File contents

Author IaC

Purpose

Write infrastructure-as-code modules and templates

This skill provides operational guidance for Author IaC, including tool usage patterns, workflows, and quality expectations aligned with Syncolab skill standards.

When to Use

Use when the user needs help with Author IaC.
When integrations for this domain are available and the task matches the workflows below.

When NOT to Use

When the task is unrelated to Author IaC or covered by a more specific skill.
When required integrations or credentials are unavailable.

Expected Outcome

Correct use of domain tools with verified results (not fabricated).
Clear summary of actions taken, data returned, and recommended next steps.
Errors and missing permissions reported explicitly.

Inputs to Gather

User goal, constraints, and any identifiers (URLs, IDs, project keys).
Available tool sets and connection status.
Relevant context from related systems before destructive writes.

Workflow

Confirm the request maps to Author IaC and required tools are available.
Gather identifiers and scope (project, channel, repo, date range, etc.).
Follow the domain guidance below; prefer list/search before get/update when applicable.
Execute tool calls using schemas from the integration; never invent tool output.
Summarize results and offer logical follow-ups.

Tool Availability Rules

Access	Behavior
Full tool access	Execute workflows, verify outputs, report errors.
Read-only	Inspect and plan; provide exact commands or dispatch request for writes.
No integration	State limitation; do not fabricate API results.

Related tool sets

kubernetes
docker

Review / Decision / Execution Criteria

Prefer smallest safe change; confirm destructive actions with the user.
Use evidence from tool responses; cite IDs and links when present.
Match integration-specific conventions (JQL, RFC3339, A1 notation, etc.).

Output Format

Report:

What was requested and what was done.
Key results (tables or bullets).
Errors, blockers, or missing permissions.
Suggested next steps.

Quality Bar

Specific, actionable, and grounded in tool output.
Concise unless the user asked for detail.
Respect rate limits, pagination, and API semantics.

Safety and Boundaries

Do not commit secrets, tokens, or PII into skills or user-visible logs.
Do not fabricate validation, send, or write confirmations.
Confirm destructive operations (delete, destroy, mass update) when appropriate.

Escalation / Dispatch Rules

If the task spans multiple domains, use or suggest related skills via relationships.skills.
If write access is required but unavailable, dispatch or ask the user to enable tools.

References

Legacy content migrated from skills/old_skills.json (author-iac).
skills/skill.instruction.md, skills/meta.instructions.md

---name: author-iacdescription: Write infrastructure-as-code modules and templates---# Author IaC## PurposeWrite infrastructure-as-code modules and templatesThis skill provides operational guidance for Author IaC, including tool usage patterns, workflows, and quality expectations aligned with Syncolab skill standards.## When to Use- Use when the user needs help with Author IaC.- When integrations for this domain are available and the task matches the workflows below.## When NOT to Use- When the task is unrelated to Author IaC or covered by a more specific skill.- When required integrations or credentials are unavailable.## Expected Outcome- Correct use of domain tools with verified results (not fabricated).- Clear summary of actions taken, data returned, and recommended next steps.- Errors and missing permissions reported explicitly.## Inputs to Gather- User goal, constraints, and any identifiers (URLs, IDs, project keys).- Available tool sets and connection status.- Relevant context from related systems before destructive writes.## Workflow1. Confirm the request maps to Author IaC and required tools are available.2. Gather identifiers and scope (project, channel, repo, date range, etc.).3. Follow the domain guidance below; prefer list/search before get/update when applicable.4. Execute tool calls using schemas from the integration; never invent tool output.5. Summarize results and offer logical follow-ups.## Tool Availability Rules| Access | Behavior ||--------|----------|| Full tool access | Execute workflows, verify outputs, report errors. || Read-only | Inspect and plan; provide exact commands or dispatch request for writes. || No integration | State limitation; do not fabricate API results. |### Related tool sets- `kubernetes`- `docker`## Review / Decision / Execution Criteria- Prefer smallest safe change; confirm destructive actions with the user.- Use evidence from tool responses; cite IDs and links when present.- Match integration-specific conventions (JQL, RFC3339, A1 notation, etc.).## Output FormatReport:1. What was requested and what was done.2. Key results (tables or bullets).3. Errors, blockers, or missing permissions.4. Suggested next steps.## Quality Bar- Specific, actionable, and grounded in tool output.- Concise unless the user asked for detail.- Respect rate limits, pagination, and API semantics.## Safety and Boundaries- Do not commit secrets, tokens, or PII into skills or user-visible logs.- Do not fabricate validation, send, or write confirmations.- Confirm destructive operations (delete, destroy, mass update) when appropriate.## Escalation / Dispatch Rules- If the task spans multiple domains, use or suggest related skills via `relationships.skills`.- If write access is required but unavailable, dispatch or ask the user to enable tools.## References- Legacy content migrated from `skills/old_skills.json` (`author-iac`).- `skills/skill.instruction.md`, `skills/meta.instructions.md`

Frequently asked questions

Author Iac