@techwavedev/agi-agent-kit 1.1.3

package/templates/base/AGENTS.md

@@ -0,0 +1,463 @@
+# Agent Instructions
+
+> `CLAUDE.md` and `GEMINI.md` are symlinks to this file, so the same instructions load in any AI environment.
+
+---
+
+## Getting Started
+
+### Installation
+
+Run this command in any directory where you want to scaffold a new AI agent:
+
+```bash
+npx @techwavedev/agi-agent-kit init
+```
+
+### Dependencies
+
+This toolkit relies on Python scripts for deterministic execution. Ensure you have the following installed:
+
+1. **Python 3.8+**: `python3 --version`
+2. **Pip Dependencies**:
+   ```bash
+   pip install requests beautifulsoup4 html2text lxml qdrant-client
+   ```
+
+### Updates
+
+To update the kit to the latest version:
+
+```bash
+# Clear npx cache to force latest version download
+rm -rf ~/.npm/_npx
+npx @techwavedev/agi-agent-kit init
+```
+
+---
+
+## Core Philosophy: Determinism Over Probability
+
+LLMs are probabilistic, but business logic requires consistency. This system fixes that mismatch by **pushing complexity into deterministic code** and letting the agent focus on intelligent decision-making.
+
+**Why it matters:** 90% accuracy per step = 59% success over 5 steps. The solution is to minimize probabilistic steps by delegating execution to reliable scripts.
+
+---
+
+## The 3-Layer Architecture
+
+### Layer 1: Directives (Intent)
+
+**Location:** `directives/`
+
+Directives are SOPs written in Markdown that define:
+
+- **Goal**: What needs to be accomplished
+- **Inputs**: Required data, context, or parameters
+- **Tools**: Which execution scripts to use
+- **Outputs**: Expected deliverables and their format
+- **Edge Cases**: Known failure modes and how to handle them
+
+Think of directives as instructions you'd give a capable but literal-minded employee. They bridge human intent to machine execution.
+
+```markdown
+# Example: directives/scrape_competitor_pricing.md
+
+## Goal
+
+Scrape pricing data from competitor websites and compile into a comparison sheet.
+
+## Inputs
+
+- `competitors.json` - List of competitor URLs and selectors
+- Target date range (optional, defaults to current)
+
+## Execution
+
+1. Run `execution/scrape_single_site.py` for each competitor
+2. Run `execution/normalize_pricing.py` to standardize formats
+3. Run `execution/export_to_sheets.py` to push to Google Sheets
+
+## Outputs
+
+- Google Sheet with pricing comparison (link in `.tmp/output_links.json`)
+- Raw data preserved in `.tmp/scraped/`
+
+## Edge Cases
+
+- **Rate limiting**: Script auto-retries with exponential backoff (max 3 attempts)
+- **Selector changes**: Log failure, continue with others, alert user at end
+- **Auth required**: Skip site, note in output sheet
+```
+
+---
+
+### Layer 2: Orchestration (Decision-Making)
+
+**This is the agent's role.**
+
+The agent is the intelligent router between intent and execution:
+
+| Responsibility            | Description                                             |
+| ------------------------- | ------------------------------------------------------- |
+| **Read directives**       | Understand what needs to be done before acting          |
+| **Sequence execution**    | Call scripts in the right order with correct parameters |
+| **Handle errors**         | Diagnose failures and apply self-annealing (see below)  |
+| **Ask for clarification** | When requirements are ambiguous, ask—don't guess        |
+| **Update directives**     | Capture learnings to prevent future failures            |
+
+**Critical principle:** The agent does NOT perform complex data transformations, API calls, or file operations directly. Instead, it invokes execution scripts that handle these deterministically.
+
+```
+❌ Wrong: Agent writes inline Python to scrape a website
+✅ Right: Agent reads directive → invokes execution/scrape_single_site.py → handles result
+```
+
+---
+
+### Layer 3: Execution (Deterministic Work)
+
+**Location:** `execution/`
+
+Python scripts that handle:
+
+- API calls and external integrations
+- Data processing and transformations
+- File operations and I/O
+- Database interactions
+- Export to cloud services (Google Sheets, Slides, etc.)
+
+**Script requirements:**
+
+- Well-commented and self-documenting
+- Accept clear inputs via CLI arguments or stdin
+- Return structured output (JSON preferred) or exit codes
+- Handle their own error cases gracefully
+- Idempotent where possible (safe to retry)
+
+```bash
+# Example invocation
+python execution/scrape_single_site.py \
+  --url "https://competitor.com/pricing" \
+  --selector ".price-table" \
+  --output ".tmp/scraped/competitor_2024.json"
+```
+
+---
+
+## Operating Principles
+
+### 1. Memory-First (Automatic)
+
+**All operations use the Qdrant-powered memory system by default.**
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│  QUERY RECEIVED                                              │
+│  ↓                                                           │
+│  1. Check for opt-out flags ("no cache", "fresh", etc.)     │
+│  ↓                                                           │
+│  2. SEMANTIC CACHE CHECK (similarity > 0.92)                │
+│     └─ Hit? → Return cached response (100% token savings)   │
+│  ↓                                                           │
+│  3. CONTEXT RETRIEVAL (top 5 relevant memories)             │
+│     └─ Inject decisions, patterns, solutions (80-95% saved) │
+│  ↓                                                           │
+│  4. EXECUTE QUERY with enriched context                      │
+│  ↓                                                           │
+│  5. STORE RESPONSE for future cache hits                    │
+└─────────────────────────────────────────────────────────────┘
+```
+
+**Opt-out:** User says "don't use cache", "no cache", "skip memory", or "fresh"
+
+**Auto-stored memories:**
+
+- `decision` — Architecture choices, design decisions
+- `code` — Script patterns, reusable implementations
+- `error` — Bug resolutions with root cause
+- `technical` — Documentation, API knowledge
+
+> See `directives/memory_integration.md` for full details.
+
+### 2. Check for Existing Tools First
+
+Before writing any new script:
+
+1. **Check `execution/`** for existing scripts that might handle the task
+2. **Review the relevant directive** to see if a workflow already exists
+3. **Search Knowledge Items** for documented patterns and learnings
+
+Only create new scripts when truly necessary. Reuse and extend existing tools.
+
+### 3. Self-Anneal When Things Break
+
+Errors are learning opportunities, not failures. When something breaks:
+
+```
+┌─────────────────────────────────────────────────────────┐
+│  ERROR DETECTED                                         │
+│  ↓                                                      │
+│  1. Read error message and full stack trace             │
+│  ↓                                                      │
+│  2. Diagnose root cause                                 │
+│  ↓                                                      │
+│  3. Fix the script or adjust parameters                 │
+│  ↓                                                      │
+│  4. Test the fix (⚠️ confirm with user if uses paid    │
+│     tokens, credits, or has side effects)               │
+│  ↓                                                      │
+│  5. Update directive with what was learned              │
+│  ↓                                                      │
+│  SYSTEM IS NOW STRONGER                                 │
+└─────────────────────────────────────────────────────────┘
+```
+
+**Example:** You hit an API rate limit → investigate API docs → find batch endpoint → rewrite script to use batching → test → update directive with rate limit info and new approach.
+
+### 4. Update Directives as You Learn
+
+Directives are **living documents**. Update them when you discover:
+
+- API constraints or rate limits
+- Better approaches or optimizations
+- Common errors and their solutions
+- Timing expectations (how long things take)
+- New edge cases
+
+**Rules:**
+
+- Always ask before creating or overwriting directives (unless explicitly told to proceed)
+- Append learnings to existing directives rather than replacing content
+- Date your additions for future reference
+
+### 5. Validate Before Delivering
+
+Before marking a task complete:
+
+- Verify outputs exist and are accessible
+- Spot-check data quality where possible
+- Confirm deliverables are in the expected location (cloud service, output file, etc.)
+
+---
+
+## File Organization
+
+### Directory Structure
+
+```
+project/
+├── .agent/
+│   └── workflows/        # Quick-reference workflows for common tasks
+├── .env                  # Environment variables and API keys
+├── .gitignore            # Excludes credentials and .tmp/
+├── .tmp/                 # Intermediate files (always regenerable)
+│   ├── scraped/          # Raw scraped data
+│   ├── processed/        # Transformed data
+│   └── output_links.json # Links to cloud deliverables
+├── credentials.json      # Google OAuth credentials
+├── token.json            # Google OAuth token
+├── directives/           # SOPs in Markdown
+├── docs/                 # Project documentation, guides, and references
+│   ├── guides/           # How-to guides and tutorials
+│   ├── api/              # API references and specifications
+│   └── architecture/     # System design and architecture docs
+├── execution/            # Deterministic Python scripts
+├── skill-creator/        # Skill creation toolkit (use to create new skills)
+├── skills/               # Modular capabilities (PDF reading, web scraping, etc.)
+│   └── <skill-name>/
+│       ├── SKILL.md      # Skill instructions and triggers
+│       ├── scripts/      # Executable tools
+│       └── references/   # Documentation loaded on-demand
+└── AGENTS.md             # This file (symlinked as CLAUDE.md, GEMINI.md)
+```
+
+### Skills
+
+Skills are modular packages that extend agent capabilities with specialized workflows, scripts, and domain knowledge. Each skill contains:
+
+- **SKILL.md** — Instructions with YAML frontmatter (`name`, `description`) for triggering
+- **scripts/** — Deterministic tools the agent can execute
+- **references/** — Documentation loaded only when needed
+
+**Key Resources:**
+
+- **Skills Catalog:** `skills/SKILLS_CATALOG.md` — Complete documentation of all available skills
+- **Skill Creator Guide:** `skill-creator/SKILL_skillcreator.md` — How to create new skills
+
+**Commands:**
+
+```bash
+# Create a new skill
+python3 skill-creator/scripts/init_skill.py <name> --path skills/
+
+# Update the skills catalog (MANDATORY after any skill change)
+python3 skill-creator/scripts/update_catalog.py --skills-dir skills/
+```
+
+### Deliverables vs. Intermediates
+
+| Type              | Location       | Examples                                             |
+| ----------------- | -------------- | ---------------------------------------------------- |
+| **Deliverables**  | Cloud services | Google Sheets, Slides, Drive files, database records |
+| **Intermediates** | `.tmp/`        | Scraped HTML, processed JSON, temp exports           |
+
+**Key principle:** Everything in `.tmp/` can be deleted and regenerated. Deliverables live in the cloud where users can access them.
+
+---
+
+## Integration with Agent Tools
+
+### Reading and Research
+
+- Use `view_file` to read directives before starting work
+- Use `grep_search` to find relevant scripts in `execution/`
+- Use `find_by_name` to locate files across the project
+- Search Knowledge Items for prior solutions to similar problems
+
+### Execution
+
+- Use `run_command` to invoke execution scripts
+- Capture output and exit codes for decision-making
+- Use `command_status` to monitor long-running scripts
+
+### Writing and Updating
+
+- Use `write_to_file` for new scripts (with clear documentation)
+- Use `replace_file_content` to update existing directives with learnings
+- Create new workflows in `.agent/workflows/` for repeatable processes
+
+---
+
+## Workflow Quick Reference
+
+For frequently-used processes, create workflows in `.agent/workflows/`:
+
+```markdown
+# .agent/workflows/refresh-pricing.md
+
+---
+
+## description: Refresh competitor pricing data and update comparison sheet
+
+1. Verify `.env` contains required API keys
+2. Run `python execution/scrape_all_competitors.py`
+   // turbo
+3. Run `python execution/normalize_pricing.py --input .tmp/scraped/ --output .tmp/processed/`
+   // turbo
+4. Run `python execution/export_to_sheets.py --input .tmp/processed/pricing.json`
+5. Verify Google Sheet is updated and share link with user
+```
+
+> **Note:** Steps marked with `// turbo` can be auto-run. Use `// turbo-all` at the top to auto-run all command steps.
+
+---
+
+## Best Practices for Execution Scripts
+
+### Script Template
+
+```python
+#!/usr/bin/env python3
+"""
+Script: script_name.py
+Purpose: Brief description of what this script does
+
+Usage:
+    python script_name.py --input <file> --output <file> [--verbose]
+
+Arguments:
+    --input   Path to input file (required)
+    --output  Path to output file (required)
+    --verbose Enable detailed logging (optional)
+
+Exit Codes:
+    0 - Success
+    1 - Invalid arguments
+    2 - Input file not found
+    3 - API/Network error
+    4 - Processing error
+"""
+
+import argparse
+import json
+import sys
+from pathlib import Path
+
+def main():
+    parser = argparse.ArgumentParser(description=__doc__)
+    parser.add_argument('--input', required=True, help='Input file path')
+    parser.add_argument('--output', required=True, help='Output file path')
+    parser.add_argument('--verbose', action='store_true', help='Verbose output')
+    args = parser.parse_args()
+
+    # Your logic here
+    try:
+        result = process(args.input)
+        Path(args.output).write_text(json.dumps(result, indent=2))
+        print(json.dumps({"status": "success", "output": args.output}))
+        sys.exit(0)
+    except Exception as e:
+        print(json.dumps({"status": "error", "message": str(e)}), file=sys.stderr)
+        sys.exit(4)
+
+if __name__ == '__main__':
+    main()
+```
+
+### Naming Conventions
+
+| Type       | Convention            | Example                                      |
+| ---------- | --------------------- | -------------------------------------------- |
+| Scripts    | `verb_noun.py`        | `scrape_website.py`, `export_to_sheets.py`   |
+| Directives | `noun_or_task.md`     | `competitor_analysis.md`, `weekly_report.md` |
+| Temp files | Descriptive with date | `.tmp/scraped/competitor_2024-01-19.json`    |
+
+---
+
+## Error Handling Patterns
+
+### In Scripts
+
+```python
+# Always return structured errors
+try:
+    result = risky_operation()
+except RateLimitError as e:
+    print(json.dumps({
+        "status": "rate_limited",
+        "retry_after": e.retry_after,
+        "message": str(e)
+    }))
+    sys.exit(3)
+except Exception as e:
+    print(json.dumps({
+        "status": "error",
+        "type": type(e).__name__,
+        "message": str(e)
+    }))
+    sys.exit(4)
+```
+
+### As the Agent
+
+When a script returns an error:
+
+1. Parse the structured error output
+2. Determine if it's recoverable (rate limit → wait and retry) or fatal (auth error → ask user)
+3. Apply the fix or escalate to the user
+4. **Update the directive** with the failure mode and solution
+
+---
+
+## Summary
+
+You are the intelligent orchestrator between human intent (directives) and deterministic execution (Python scripts). Your role is to:
+
+1. **Understand** what needs to be done by reading directives
+2. **Execute** by calling the right scripts in the right order
+3. **Adapt** by handling errors and edge cases gracefully
+4. **Learn** by updating directives with new knowledge
+5. **Deliver** by ensuring outputs reach their intended destination
+
+**Be pragmatic. Be reliable. Self-anneal.**

package/templates/base/requirements.txt

@@ -0,0 +1,6 @@
+requests
+beautifulsoup4
+html2text
+lxml
+qdrant-client
+boto3 # for bedrock/aws skills

package/templates/base/skill-creator/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.