Install
$ agentstack add skill-gigayaya-daa-master-daa-install ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
About
DAA Project Installer
Overview
This skill installs DAA (Declarative Action Architecture) rules and conventions into the user's current project. It creates a knowledge base directory for on-demand reference and updates existing configuration files to point agents to those rules.
What Gets Installed
| Target | Action | Content | |--------|--------|---------| | docs/daa_rules/ | Created (always) | 7 knowledge base files covering DAA principles, naming, anti-patterns, code generation, code review, and project structure | | CLAUDE.md | Modified (only if exists) | Minimal DAA section with pointer table to docs/daa_rules/ | | AGENTS.md | Modified (only if exists) | Minimal DAA section with pointer table to docs/daa_rules/ | | README.md | Modified (only if exists) | Brief DAA architecture section |
Installation Procedure
Follow these steps IN ORDER. Do not skip steps.
Step 1: Safety Check
Determine the user's current working directory. This is the project where DAA will be installed.
STOP if the current directory is inside the DAA plugin repository itself (contains plugins/DAA-Master/skills/). Warn the user: "This skill should be invoked from your own project, not the DAA plugin repo."
Step 2: Survey Existing Files
Check which of these files exist in the project root:
CLAUDE.mdAGENTS.mdREADME.mddocs/daa_rules/directory
For each existing file, check if it already contains the marker `` (inclusive) with the new template content.
- NEVER create CLAUDE.md, AGENTS.md, or README.md if they don't exist. Skip and report.
Step 6: Report Results
Show the user a summary:
DAA Installation Complete
─────────────────────────
✓ docs/daa_rules/ — [created / updated] (7 files)
✓ CLAUDE.md — [appended / refreshed / skipped (file not found)]
✓ AGENTS.md — [appended / refreshed / skipped (file not found)]
✓ README.md — [appended / refreshed / skipped (file not found)]
DAA rules are now available in this project.
AI agents will read docs/daa_rules/ on demand when working with test code.
Idempotency
This skill is safe to run multiple times:
docs/daa_rules/files are overwritten with latest content on each run- The `
/` markers in config files ensure only the DAA block is replaced, leaving all user-written content untouched
What This Skill Does NOT Do
- Does NOT create CLAUDE.md, AGENTS.md, or README.md — only modifies existing ones
- Does NOT modify any source code files
- Does NOT scaffold a test framework structure — use
daa:daa-architectfor that - Does NOT install any dependencies or packages
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: gigayaya
- Source: gigayaya/DAA-Master
- License: Apache-2.0
- Homepage: https://medium.com/@gigayaya/declarative-action-architecture-a-scalable-pattern-for-e2e-automation-1f9a10d24ee0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.