loudmouth-ai 0.1.0 → 0.2.0

package/extensions/open-prose/skills/prose/examples/01-hello-world.prose

@@ -1,4 +0,0 @@
-# Hello World
-# The simplest OpenProse program - a single session
-
-session "Say hello and briefly introduce yourself"

package/extensions/open-prose/skills/prose/examples/02-research-and-summarize.prose

@@ -1,6 +0,0 @@
-# Research and Summarize
-# A two-step workflow: research a topic, then summarize findings
-
-session "Research the latest developments in AI agents and multi-agent systems. Focus on papers and announcements from the past 6 months."
-
-session "Summarize the key findings from your research in 5 bullet points. Focus on practical implications for developers."

package/extensions/open-prose/skills/prose/examples/03-code-review.prose

@@ -1,17 +0,0 @@
-# Code Review Pipeline
-# Review code from multiple perspectives sequentially
-
-# First, understand what the code does
-session "Read the files in src/ and provide a brief overview of the codebase structure and purpose."
-
-# Security review
-session "Review the code for security vulnerabilities. Look for injection risks, authentication issues, and data exposure."
-
-# Performance review
-session "Review the code for performance issues. Look for N+1 queries, unnecessary allocations, and blocking operations."
-
-# Maintainability review
-session "Review the code for maintainability. Look for code duplication, unclear naming, and missing documentation."
-
-# Synthesize findings
-session "Create a unified code review report combining all the findings above. Prioritize issues by severity and provide actionable recommendations."

package/extensions/open-prose/skills/prose/examples/04-write-and-refine.prose

@@ -1,14 +0,0 @@
-# Write and Refine
-# Draft content, then iteratively improve it
-
-# Create initial draft
-session "Write a first draft of a README.md for this project. Include sections for: overview, installation, usage, and contributing."
-
-# Self-review and improve
-session "Review the README draft you just wrote. Identify areas that are unclear, too verbose, or missing important details."
-
-# Apply improvements
-session "Rewrite the README incorporating your review feedback. Make it more concise and add any missing sections."
-
-# Final polish
-session "Do a final pass on the README. Fix any typos, improve formatting, and ensure code examples are correct."

package/extensions/open-prose/skills/prose/examples/05-debug-issue.prose

@@ -1,20 +0,0 @@
-# Debug an Issue
-# Step-by-step debugging workflow
-
-# Understand the problem
-session "Read the error message and stack trace. Identify which file and function is causing the issue."
-
-# Gather context
-session "Read the relevant source files and understand the code flow that leads to the error."
-
-# Form hypothesis
-session "Based on your investigation, form a hypothesis about what's causing the bug. List 2-3 possible root causes."
-
-# Test hypothesis
-session "Write a test case that reproduces the bug. This will help verify the fix later."
-
-# Implement fix
-session "Implement a fix for the most likely root cause. Explain your changes."
-
-# Verify fix
-session "Run the test suite to verify the fix works and doesn't break anything else."

package/extensions/open-prose/skills/prose/examples/06-explain-codebase.prose

@@ -1,17 +0,0 @@
-# Explain Codebase
-# Progressive exploration of an unfamiliar codebase
-
-# Start with the big picture
-session "List all directories and key files in this repository. Provide a high-level map of the project structure."
-
-# Understand the entry point
-session "Find the main entry point of the application. Explain how the program starts and initializes."
-
-# Trace a key flow
-session "Trace through a typical user request from start to finish. Document the key functions and modules involved."
-
-# Document architecture
-session "Based on your exploration, write a brief architecture document explaining how the major components fit together."
-
-# Identify patterns
-session "What design patterns and conventions does this codebase use? Document any patterns future contributors should follow."

package/extensions/open-prose/skills/prose/examples/07-refactor.prose

@@ -1,20 +0,0 @@
-# Refactor Code
-# Systematic refactoring workflow
-
-# Assess current state
-session "Analyze the target code and identify code smells: duplication, long functions, unclear naming, tight coupling."
-
-# Plan refactoring
-session "Create a refactoring plan. List specific changes in order of priority, starting with the safest changes."
-
-# Ensure test coverage
-session "Check test coverage for the code being refactored. Add any missing tests before making changes."
-
-# Execute refactoring
-session "Implement the first refactoring from your plan. Make a single focused change."
-
-# Verify behavior
-session "Run tests to verify the refactoring preserved behavior. If tests fail, investigate and fix."
-
-# Document changes
-session "Update any documentation affected by the refactoring. Add comments explaining non-obvious design decisions."

package/extensions/open-prose/skills/prose/examples/08-blog-post.prose

@@ -1,20 +0,0 @@
-# Write a Blog Post
-# End-to-end content creation workflow
-
-# Research the topic
-session "Research the topic: 'Best practices for error handling in TypeScript'. Find authoritative sources and common patterns."
-
-# Create outline
-session "Create a detailed outline for the blog post. Include introduction, 4-5 main sections, and conclusion."
-
-# Write first draft
-session "Write the full blog post following the outline. Target 1500-2000 words. Include code examples."
-
-# Technical review
-session "Review the blog post for technical accuracy. Verify all code examples compile and work correctly."
-
-# Editorial review
-session "Review the blog post for clarity and readability. Simplify complex sentences and improve flow."
-
-# Add finishing touches
-session "Add a compelling title, meta description, and suggest 3-5 relevant tags for the post."

package/extensions/open-prose/skills/prose/examples/09-research-with-agents.prose

@@ -1,25 +0,0 @@
-# Research Pipeline with Specialized Agents
-# This example demonstrates defining agents with different models
-# and using them in sessions with property overrides.
-
-# Define specialized agents
-agent researcher:
-  model: sonnet
-  prompt: "You are a research assistant skilled at finding and synthesizing information"
-
-agent writer:
-  model: opus
-  prompt: "You are a technical writer who creates clear, concise documentation"
-
-# Step 1: Initial research with the researcher agent
-session: researcher
-  prompt: "Research recent developments in renewable energy storage technologies"
-
-# Step 2: Deep dive with a more powerful model
-session: researcher
-  model: opus
-  prompt: "Analyze the top 3 most promising battery technologies and their potential impact"
-
-# Step 3: Write up the findings
-session: writer
-  prompt: "Create a summary report of the research findings suitable for executives"

package/extensions/open-prose/skills/prose/examples/10-code-review-agents.prose

@@ -1,32 +0,0 @@
-# Code Review Workflow with Agents
-# This example shows how to use agents for a multi-step code review process.
-
-# Define agents with specific roles
-agent security-reviewer:
-  model: opus
-  prompt: "You are a security expert focused on identifying vulnerabilities"
-
-agent performance-reviewer:
-  model: sonnet
-  prompt: "You are a performance optimization specialist"
-
-agent style-reviewer:
-  model: haiku
-  prompt: "You check for code style and best practices"
-
-# Step 1: Quick style check (fast)
-session: style-reviewer
-  prompt: "Review the code in src/ for style issues and naming conventions"
-
-# Step 2: Performance analysis (medium)
-session: performance-reviewer
-  prompt: "Identify any performance bottlenecks or optimization opportunities"
-
-# Step 3: Security audit (thorough)
-session: security-reviewer
-  prompt: "Perform a security review looking for OWASP top 10 vulnerabilities"
-
-# Step 4: Summary
-session: security-reviewer
-  model: sonnet
-  prompt: "Create a consolidated report of all review findings with priority rankings"

package/extensions/open-prose/skills/prose/examples/11-skills-and-imports.prose

@@ -1,27 +0,0 @@
-# Skills and Imports Example
-# This demonstrates importing external skills and assigning them to agents.
-
-# Import skills from external sources
-import "web-search" from "github:anthropic/skills"
-import "summarizer" from "npm:@example/summarizer"
-import "file-reader" from "./local-skills/file-reader"
-
-# Define a research agent with web search capability
-agent researcher:
-  model: sonnet
-  prompt: "You are a research assistant skilled at finding information"
-  skills: ["web-search", "summarizer"]
-
-# Define a documentation agent with file access
-agent documenter:
-  model: opus
-  prompt: "You create comprehensive documentation"
-  skills: ["file-reader", "summarizer"]
-
-# Research phase
-session: researcher
-  prompt: "Search for recent developments in renewable energy storage"
-
-# Documentation phase
-session: documenter
-  prompt: "Create a technical summary of the research findings"

package/extensions/open-prose/skills/prose/examples/12-secure-agent-permissions.prose

@@ -1,43 +0,0 @@
-# Secure Agent with Permissions Example
-# This demonstrates defining agents with restricted access permissions.
-
-# Import required skills
-import "code-analyzer" from "github:anthropic/code-tools"
-
-# Define a read-only code reviewer
-# This agent can read source files but cannot modify them or run shell commands
-agent code-reviewer:
-  model: sonnet
-  prompt: "You are a thorough code reviewer"
-  skills: ["code-analyzer"]
-  permissions:
-    read: ["src/**/*.ts", "src/**/*.js", "*.md"]
-    write: []
-    bash: deny
-
-# Define a documentation writer with limited write access
-# Can only write to docs directory
-agent doc-writer:
-  model: opus
-  prompt: "You write technical documentation"
-  permissions:
-    read: ["src/**/*", "docs/**/*"]
-    write: ["docs/**/*.md"]
-    bash: deny
-
-# Define a full-access admin agent
-agent admin:
-  model: opus
-  prompt: "You perform administrative tasks"
-  permissions:
-    read: ["**/*"]
-    write: ["**/*"]
-    bash: prompt
-    network: allow
-
-# Workflow: Code review followed by documentation update
-session: code-reviewer
-  prompt: "Review the codebase for security issues and best practices"
-
-session: doc-writer
-  prompt: "Update the documentation based on the code review findings"

package/extensions/open-prose/skills/prose/examples/13-variables-and-context.prose

@@ -1,51 +0,0 @@
-# Example 13: Variables & Context
-#
-# This example demonstrates using let/const bindings to capture session
-# outputs and pass them as context to subsequent sessions.
-
-# Define specialized agents for the workflow
-agent researcher:
-  model: sonnet
-  prompt: "You are a thorough research assistant who gathers comprehensive information on topics."
-
-agent analyst:
-  model: opus
-  prompt: "You are a data analyst who identifies patterns, trends, and key insights."
-
-agent writer:
-  model: opus
-  prompt: "You are a technical writer who creates clear, well-structured documents."
-
-# Step 1: Gather initial research (captured in a variable)
-let research = session: researcher
-  prompt: "Research the current state of quantum computing, including recent breakthroughs, major players, and potential applications."
-
-# Step 2: Analyze the research findings (using research as context)
-let analysis = session: analyst
-  prompt: "Analyze the key findings and identify the most promising directions."
-  context: research
-
-# Step 3: Get additional perspectives (refreshing context)
-let market-trends = session: researcher
-  prompt: "Research market trends and commercial applications of quantum computing."
-  context: []
-
-# Step 4: Combine multiple contexts for final synthesis
-const report = session: writer
-  prompt: "Write a comprehensive executive summary covering research, analysis, and market trends."
-  context: [research, analysis, market-trends]
-
-# Step 5: Iterative refinement with variable reassignment
-let draft = session: writer
-  prompt: "Create an initial draft of the technical deep-dive section."
-  context: research
-
-# Refine the draft using its own output as context
-draft = session: writer
-  prompt: "Review and improve this draft for clarity and technical accuracy."
-  context: draft
-
-# Final polish
-draft = session: writer
-  prompt: "Perform final editorial review and polish the document."
-  context: draft

package/extensions/open-prose/skills/prose/examples/14-composition-blocks.prose

@@ -1,48 +0,0 @@
-# Example 14: Composition Blocks
-# Demonstrates do: blocks, block definitions, and inline sequences
-
-# Define reusable agents
-agent researcher:
-  model: sonnet
-  prompt: "You are a thorough research assistant"
-
-agent writer:
-  model: opus
-  prompt: "You are a skilled technical writer"
-
-agent reviewer:
-  model: sonnet
-  prompt: "You are a careful code and document reviewer"
-
-# Define a reusable research block
-block research-phase:
-  session: researcher
-    prompt: "Gather information on the topic"
-  session: researcher
-    prompt: "Analyze key findings"
-
-# Define a reusable writing block
-block writing-phase:
-  session: writer
-    prompt: "Write initial draft"
-  session: writer
-    prompt: "Polish and refine the draft"
-
-# Define a review block
-block review-cycle:
-  session: reviewer
-    prompt: "Review for accuracy"
-  session: reviewer
-    prompt: "Review for clarity"
-
-# Main workflow using blocks
-let research = do research-phase
-
-let document = do writing-phase
-
-do review-cycle
-
-# Use anonymous do block for final steps
-do:
-  session "Incorporate review feedback"
-  session "Prepare final version"

package/extensions/open-prose/skills/prose/examples/15-inline-sequences.prose

@@ -1,23 +0,0 @@
-# Example 15: Inline Sequences
-# Demonstrates the -> operator for chaining sessions
-
-# Quick pipeline using arrow syntax
-session "Plan the task" -> session "Execute the plan" -> session "Review results"
-
-# Inline sequence with context capture
-let analysis = session "Analyze data" -> session "Draw conclusions"
-
-session "Write report"
-  context: analysis
-
-# Combine inline sequences with blocks
-block quick-check:
-  session "Security scan" -> session "Performance check"
-
-do quick-check
-
-# Use inline sequence in variable assignment
-let workflow = session "Step 1" -> session "Step 2" -> session "Step 3"
-
-session "Final step"
-  context: workflow

package/extensions/open-prose/skills/prose/examples/16-parallel-reviews.prose

@@ -1,19 +0,0 @@
-# Parallel Code Reviews
-# Run multiple specialized reviews concurrently
-
-agent reviewer:
-  model: sonnet
-  prompt: "You are an expert code reviewer"
-
-# Run all reviews in parallel
-parallel:
-  security = session: reviewer
-    prompt: "Review for security vulnerabilities"
-  perf = session: reviewer
-    prompt: "Review for performance issues"
-  style = session: reviewer
-    prompt: "Review for code style and readability"
-
-# Synthesize all review results
-session "Create unified code review report"
-  context: { security, perf, style }

package/extensions/open-prose/skills/prose/examples/17-parallel-research.prose

@@ -1,19 +0,0 @@
-# Parallel Research
-# Gather information from multiple sources concurrently
-
-agent researcher:
-  model: sonnet
-  prompt: "You are a research assistant"
-
-# Research multiple aspects in parallel
-parallel:
-  history = session: researcher
-    prompt: "Research the historical background"
-  current = session: researcher
-    prompt: "Research the current state of the field"
-  future = session: researcher
-    prompt: "Research future trends and predictions"
-
-# Combine all research
-session "Write comprehensive research summary"
-  context: { history, current, future }

package/extensions/open-prose/skills/prose/examples/18-mixed-parallel-sequential.prose

@@ -1,36 +0,0 @@
-# Mixed Parallel and Sequential Workflow
-# Demonstrates nesting parallel and sequential blocks
-
-agent worker:
-  model: sonnet
-
-# Define reusable blocks
-block setup:
-  session "Initialize resources"
-  session "Validate configuration"
-
-block cleanup:
-  session "Save results"
-  session "Release resources"
-
-# Main workflow with mixed composition
-do:
-  do setup
-
-  # Parallel processing phase
-  parallel:
-    # Each parallel branch can have multiple steps
-    do:
-      session: worker
-        prompt: "Process batch 1 - step 1"
-      session: worker
-        prompt: "Process batch 1 - step 2"
-    do:
-      session: worker
-        prompt: "Process batch 2 - step 1"
-      session: worker
-        prompt: "Process batch 2 - step 2"
-
-  session "Aggregate results"
-
-  do cleanup

package/extensions/open-prose/skills/prose/examples/19-advanced-parallel.prose

@@ -1,71 +0,0 @@
-# Advanced Parallel Execution (Tier 7)
-#
-# Demonstrates join strategies and failure policies
-# for parallel blocks.
-
-agent researcher:
-  model: haiku
-  prompt: "You are a research assistant. Provide concise information."
-
-# 1. Race Pattern: First to Complete Wins
-# ----------------------------------------
-# Use parallel ("first") when you want the fastest result
-# and don't need all branches to complete.
-
-parallel ("first"):
-  session: researcher
-    prompt: "Find information via approach A"
-  session: researcher
-    prompt: "Find information via approach B"
-  session: researcher
-    prompt: "Find information via approach C"
-
-session "Summarize: only the fastest approach completed"
-
-# 2. Any-N Pattern: Get Multiple Quick Results
-# --------------------------------------------
-# Use parallel ("any", count: N) when you need N results
-# but not necessarily all of them.
-
-parallel ("any", count: 2):
-  a = session "Generate a creative headline for a tech blog"
-  b = session "Generate a catchy headline for a tech blog"
-  c = session "Generate an engaging headline for a tech blog"
-  d = session "Generate a viral headline for a tech blog"
-
-session "Choose the best from the 2 headlines that finished first"
-  context: { a, b, c, d }
-
-# 3. Continue on Failure: Gather All Results
-# ------------------------------------------
-# Use on-fail: "continue" when you want all branches
-# to complete and handle failures afterwards.
-
-parallel (on-fail: "continue"):
-  session "Fetch data from primary API"
-  session "Fetch data from secondary API"
-  session "Fetch data from backup API"
-
-session "Combine all available data, noting any failures"
-
-# 4. Ignore Failures: Best-Effort Enrichment
-# ------------------------------------------
-# Use on-fail: "ignore" for optional enrichments
-# where failures shouldn't block progress.
-
-parallel (on-fail: "ignore"):
-  session "Get optional metadata enrichment 1"
-  session "Get optional metadata enrichment 2"
-  session "Get optional metadata enrichment 3"
-
-session "Continue with whatever enrichments succeeded"
-
-# 5. Combined: Race with Resilience
-# ---------------------------------
-# Combine join strategies with failure policies.
-
-parallel ("first", on-fail: "continue"):
-  session "Fast but might fail"
-  session "Slow but reliable"
-
-session "Got the first result, even if it was a handled failure"

package/extensions/open-prose/skills/prose/examples/20-fixed-loops.prose

@@ -1,20 +0,0 @@
-# Example: Fixed Loops in OpenProse
-# Demonstrates repeat, for-each, and parallel for-each patterns
-
-# Repeat block - generate multiple ideas
-repeat 3:
-  session "Generate a creative app idea"
-
-# For-each block - iterate over a collection
-let features = ["authentication", "dashboard", "notifications"]
-for feature in features:
-  session "Design the user interface for this feature"
-    context: feature
-
-# Parallel for-each - research in parallel
-let topics = ["market size", "competitors", "technology stack"]
-parallel for topic in topics:
-  session "Research this aspect of the startup idea"
-    context: topic
-
-session "Synthesize all research into a business plan"

package/extensions/open-prose/skills/prose/examples/21-pipeline-operations.prose

@@ -1,35 +0,0 @@
-# Pipeline Operations Example
-# Demonstrates functional-style collection transformations
-
-# Define a collection of startup ideas
-let ideas = ["AI tutor", "smart garden", "fitness tracker", "meal planner", "travel assistant"]
-
-# Filter to keep only tech-focused ideas
-let tech_ideas = ideas | filter:
-  session "Is this idea primarily technology-focused? Answer yes or no."
-    context: item
-
-# Map to expand each idea into a business pitch
-let pitches = tech_ideas | map:
-  session "Write a compelling one-paragraph business pitch for this idea"
-    context: item
-
-# Reduce all pitches into a portfolio summary
-let portfolio = pitches | reduce(summary, pitch):
-  session "Integrate this pitch into the portfolio summary, maintaining coherence"
-    context: [summary, pitch]
-
-# Present the final portfolio
-session "Format and present the startup portfolio as a polished document"
-  context: portfolio
-
-# Parallel map example - research multiple topics concurrently
-let topics = ["market analysis", "competition", "funding options"]
-
-let research = topics | pmap:
-  session "Research this aspect of the startup portfolio"
-    context: item
-
-# Final synthesis
-session "Create an executive summary combining all research findings"
-  context: research

package/extensions/open-prose/skills/prose/examples/22-error-handling.prose

@@ -1,51 +0,0 @@
-# Error Handling Example
-# Demonstrates try/catch/finally patterns for resilient workflows
-
-# Basic try/catch for error recovery
-try:
-  session "Attempt to fetch data from external API"
-catch:
-  session "API failed - use cached data instead"
-
-# Catch with error variable for context-aware handling
-try:
-  session "Parse and validate complex configuration file"
-catch as err:
-  session "Handle the configuration error"
-    context: err
-
-# Try/catch/finally for resource cleanup
-try:
-  session "Open database connection and perform queries"
-catch:
-  session "Log database error and notify admin"
-finally:
-  session "Ensure database connection is properly closed"
-
-# Nested error handling
-try:
-  session "Start outer transaction"
-  try:
-    session "Perform risky inner operation"
-  catch:
-    session "Recover inner operation"
-    throw  # Re-raise to outer handler
-catch:
-  session "Handle re-raised error at outer level"
-
-# Error handling in parallel blocks
-parallel:
-  try:
-    session "Service A - might fail"
-  catch:
-    session "Fallback for Service A"
-  try:
-    session "Service B - might fail"
-  catch:
-    session "Fallback for Service B"
-
-session "Continue with whatever results we got"
-
-# Throwing custom errors
-session "Validate input data"
-throw "Validation failed: missing required fields"