@bluefly/openstandardagents 0.5.1 → 0.5.3

package/examples/showcase/team-leader.ossa.yaml

@@ -1,306 +0,0 @@
-apiVersion: ossa/v0.4.7
-kind: Agent
-metadata:
-  name: team-leader
-  version: 1.0.0
-  description: Multi-agent team leader with task distribution, coordination, and progress tracking capabilities
-  labels:
-    ossa.dev/category: orchestration
-    ossa.dev/tier: production-example
-    ossa.dev/autonomy: autonomous
-    ossa.dev/domain: coordination
-    ossa.dev/role: leader
-  annotations:
-    ossa.dev/documentation: https://openstandardagents.org/agents/team-leader
-    ossa.dev/a2a-enabled: "true"
-    ossa.dev/team-discovery: "true"
-spec:
-  capabilities:
-  - type: function
-    name: task.distribute
-    description: Distribute tasks to team members based on capabilities
-    parameters:
-      type: object
-      properties:
-        task:
-          type: object
-          properties:
-            id:
-              type: string
-            description:
-              type: string
-            requirements:
-              type: array
-              items:
-                type: string
-            priority:
-              type: string
-              enum: [critical, high, medium, low]
-            deadline:
-              type: string
-              format: date-time
-          required: [id, description, requirements]
-        assignment_strategy:
-          type: string
-          enum: [capability_match, load_balance, round_robin, priority]
-          default: capability_match
-      required: [task]
-  - type: function
-    name: team.coordinate
-    description: Coordinate team member activities and dependencies
-    parameters:
-      type: object
-      properties:
-        coordination_type:
-          type: string
-          enum: [sequential, parallel, conditional, fan_out_fan_in]
-        agents:
-          type: array
-          items:
-            type: object
-            properties:
-              agent_id:
-                type: string
-              role:
-                type: string
-              dependencies:
-                type: array
-                items:
-                  type: string
-        timeout:
-          type: integer
-          description: Coordination timeout in seconds
-          default: 3600
-      required: [coordination_type, agents]
-  - type: function
-    name: progress.track
-    description: Track and report team progress
-    parameters:
-      type: object
-      properties:
-        scope:
-          type: string
-          enum: [agent, task, project, team]
-        metrics:
-          type: array
-          items:
-            type: string
-            enum: [completion_rate, velocity, quality, blockers]
-        report_format:
-          type: string
-          enum: [summary, detailed, dashboard]
-          default: summary
-      required: [scope]
-  - type: query
-    name: team.discover
-    description: Discover available team members and their capabilities
-  role: |
-    You are a team leader agent responsible for orchestrating multi-agent teams,
-    distributing tasks, coordinating activities, and tracking progress.
-
-    Your core responsibilities:
-    1. Task Distribution - Assign tasks to team members based on capabilities
-    2. Team Coordination - Manage dependencies and orchestration patterns
-    3. Progress Tracking - Monitor team progress and identify blockers
-    4. Resource Management - Balance workload across team members
-    5. Communication - Facilitate agent-to-agent communication
-    6. Conflict Resolution - Resolve task conflicts and dependencies
-
-    Orchestration patterns:
-    - Sequential: Execute tasks in order with dependencies
-    - Parallel: Execute independent tasks concurrently
-    - Conditional: Route based on conditions and results
-    - Fan-out/Fan-in: Distribute work and aggregate results
-
-    Team leadership principles:
-    - Capability-based assignment (match tasks to agent strengths)
-    - Load balancing (distribute work evenly)
-    - Proactive monitoring (identify blockers early)
-    - Clear communication (use A2A protocols)
-    - Adaptive coordination (adjust based on team state)
-
-    Always:
-    - Verify agent capabilities before assignment
-    - Monitor task progress and completion
-    - Handle failures gracefully with reassignment
-    - Provide clear status updates
-    - Maintain team state and history
-  llm:
-    provider: anthropic
-    model: claude-sonnet-4
-    temperature: 0.3
-    maxTokens: 16384
-    features:
-      promptCaching: true
-      tokenEfficiency: false
-      batchProcessing: false
-  tools:
-  - type: function
-    name: agent.query
-    description: Query agent capabilities and status
-  - type: function
-    name: task.queue
-    description: Manage task queue and priorities
-  - type: function
-    name: dependency.graph
-    description: Build and analyze task dependency graphs
-  - type: function
-    name: notification.send
-    description: Send notifications to team members
-  autonomy:
-    mode: autonomous
-    humanApproval: false
-    escalation:
-      enabled: true
-      triggers:
-        - team_deadlock
-        - critical_task_failure
-        - resource_exhaustion
-        - prolonged_blocker
-      contacts:
-        - role: team_admin
-          method: slack
-        - role: on_call_engineer
-          method: pagerduty
-  a2a:
-    enabled: true
-    role: leader
-    capabilities:
-      - task-distribution
-      - team-coordination
-      - progress-tracking
-      - agent-discovery
-    protocols:
-      - rest
-      - grpc
-      - websocket
-    discovery:
-      enabled: true
-      broadcast: true
-      interval: 60s
-      endpoints:
-        - url: https://team-leader.company.com/v1
-          protocol: rest
-        - url: wss://team-leader.company.com/ws
-          protocol: websocket
-    communication:
-      patterns:
-        - request-response
-        - publish-subscribe
-        - broadcast
-      messageFormats:
-        - application/json
-      reliability:
-        retries: 3
-        timeout: 30s
-        circuitBreaker:
-          enabled: true
-          threshold: 5
-          resetTimeout: 60s
-  teamDiscovery:
-    enabled: true
-    autoRegister: true
-    heartbeat:
-      interval: 30s
-      timeout: 90s
-    capabilities:
-      query: true
-      filter: true
-      subscribe: true
-  messaging:
-    transport: redis
-    queues:
-      - name: task-assignments
-        description: Task assignment notifications
-        dlq: true
-      - name: status-updates
-        description: Team member status updates
-        dlq: false
-      - name: coordination-events
-        description: Coordination lifecycle events
-        dlq: true
-    events:
-      publish:
-        - task.assigned
-        - task.completed
-        - task.failed
-        - coordination.started
-        - coordination.completed
-        - team.member.discovered
-        - team.member.offline
-      subscribe:
-        - task.status.changed
-        - agent.heartbeat
-        - agent.capability.updated
-  observability:
-    metrics:
-      enabled: true
-      provider: prometheus
-      port: 9092
-      custom:
-        - name: tasks_distributed
-          type: counter
-        - name: team_members_active
-          type: gauge
-        - name: coordination_duration
-          type: histogram
-        - name: task_success_rate
-          type: gauge
-    logging:
-      level: info
-      format: json
-      destination: stdout
-    tracing:
-      enabled: true
-      provider: opentelemetry
-      samplingRate: 0.5
-    dashboards:
-      - type: grafana
-        url: https://grafana.company.com/d/team-leader
-  resources:
-    memory: 2Gi
-    cpu: 2000m
-    storage: 5Gi
-  state:
-    persistence: postgresql
-    ttl: 604800  # 7 days
-    schema:
-      type: object
-      properties:
-        team_members:
-          type: array
-          items:
-            type: object
-            properties:
-              agent_id:
-                type: string
-              capabilities:
-                type: array
-              status:
-                type: string
-              workload:
-                type: integer
-        active_tasks:
-          type: array
-        completed_tasks:
-          type: array
-        task_history:
-          type: array
-        coordination_state:
-          type: object
-  security:
-    authentication:
-      required: true
-      methods:
-        - oauth2
-        - mutual_tls
-    authorization:
-      rbac:
-        enabled: true
-        roles:
-          - team_leader
-          - team_member
-          - team_observer
-    encryption:
-      at_rest: true
-      in_transit: true

package/examples/showcase/test-generator.ossa.yaml

@@ -1,37 +0,0 @@
-apiVersion: ossa/v0.4.7
-kind: Agent
-metadata:
-  name: test-generator
-  version: 1.0.0
-  description: Automated test generation agent
-  labels:
-    ossa.dev/category: testing
-    ossa.dev/tier: standard-example
-  annotations:
-    ossa.dev/documentation: https://openstandardagents.org/agents/test-generator
-spec:
-  capabilities:
-  - type: function
-    name: test.unit
-    description: Generate unit tests
-  - type: function
-    name: test.integration
-    description: Generate integration tests
-  - type: function
-    name: test.fixtures
-    description: Generate test fixtures and mocks
-  - type: function
-    name: test.coverage
-    description: Analyze and improve test coverage
-  role: "You are a test generation specialist responsible for creating comprehensive\n\
-    test suites for codebases.\n\nTest generation process:\n1. Analyze code structure\
-    \ and dependencies\n2. Identify testable units (functions, classes, modules)\n\
-    3. Generate test cases covering:\n   - Happy path scenarios\n   - Edge cases\n\
-    \   - Error handling\n   - Boundary conditions\n4. Create test fixtures and mocks\n\
-    5. Ensure proper test isolation\n\nTest quality standards:\n- Descriptive test\
-    \ names (should_X_when_Y)\n- Arrange-Act-Assert pattern\n- One assertion per test\
-    \ (where practical)\n- Independent tests (no shared state)\n- Fast execution\n"
-  tools:
-  - type: function
-    name: code.parse
-    description: Parse code into AST

package/examples/showcase/workflow-orchestrator.ossa.yaml

@@ -1,114 +0,0 @@
-apiVersion: ossa/v0.4.7
-kind: Workflow
-metadata:
-  name: workflow-orchestrator
-  version: 1.0.0
-  description: Multi-agent workflow orchestration and coordination
-  labels:
-    ossa.dev/category: orchestration
-    ossa.dev/tier: standard-example
-  annotations:
-    ossa.dev/documentation: https://openstandardagents.org/agents/workflow-orchestrator
-spec:
-  execution:
-    type: orchestrated
-    parallelism: 5
-    timeout: 3600s
-  capabilities:
-  - type: function
-    name: workflow.create
-    description: Create and configure workflows
-  - type: function
-    name: workflow.execute
-    description: Execute multi-agent workflows
-  - type: function
-    name: workflow.monitor
-    description: Monitor workflow execution status
-  - type: function
-    name: workflow.route
-    description: Route tasks to appropriate agents
-  role: 'You are the workflow orchestrator responsible for coordinating complex
-
-    multi-agent workflows. You manage task routing, state persistence,
-
-    and agent-to-agent communication.
-
-
-    Orchestration patterns:
-
-    1. Sequential - Execute agents in order
-
-    2. Parallel - Execute multiple agents concurrently
-
-    3. Conditional - Route based on conditions
-
-    4. Fan-out/Fan-in - Distribute and aggregate
-
-    5. Human-in-the-loop - Pause for human approval
-
-    '
-  llm:
-    provider: anthropic
-    model: claude-sonnet-4
-    temperature: 0.2
-    maxTokens: 8192
-  agents:
-  - ref: code-reviewer
-    alias: reviewer
-    on_complete: security-scanner
-  - ref: security-scanner
-    alias: security
-    on_complete: ci-pipeline
-  - ref: ci-pipeline
-    alias: pipeline
-    condition: security.result.passed == true
-  steps:
-  - id: review
-    agent: reviewer
-    input:
-      mr_iid: ${input.mr_iid}
-      project_id: ${input.project_id}
-  - id: security
-    agent: security
-    depends_on:
-    - review
-    condition: review.status == "approved"
-    input:
-      paths: ${input.changed_files}
-  - id: deploy
-    agent: pipeline
-    depends_on:
-    - security
-    condition: security.passed == true
-    input:
-      action: deploy
-      environment: ${input.environment}
-  state:
-    persistence: redis
-    ttl: 86400
-    schema:
-      type: object
-      properties:
-        current_step:
-          type: string
-        completed_steps:
-          type: array
-        results:
-          type: object
-  messaging:
-    transport: redis
-    queues:
-    - name: workflow-events
-      description: Workflow lifecycle events
-    - name: agent-results
-      description: Agent execution results
-    events:
-      publish:
-      - workflow.started
-      - workflow.completed
-      - workflow.failed
-      - step.completed
-      subscribe:
-      - agent.completed
-      - agent.failed
-      - human.approved

package/examples/single-agent.ossa.yaml

@@ -1,40 +0,0 @@
-apiVersion: ossa/v0.4
-kind: Agent
-metadata:
-  name: code-assistant
-  version: 1.0.0
-  description: A single code assistant agent
-  agentType: claude
-  agentKind: assistant
-  agentArchitecture:
-    pattern: single
-    capabilities:
-      - tools
-      - code
-      - context
-spec:
-  role: >
-    You are an expert code assistant. You help developers write, review,
-    and debug code across multiple programming languages.
-  llm:
-    provider: anthropic
-    model: claude-sonnet-4-5-20250514
-    temperature: 0.3
-    maxTokens: 8192
-  tools:
-    - type: function
-      name: read_file
-      description: Read a file from the filesystem
-    - type: function
-      name: write_file
-      description: Write content to a file
-    - type: function
-      name: run_tests
-      description: Execute test suite
-  constraints:
-    cost:
-      maxTokensPerRequest: 8192
-      maxTokensPerDay: 500000
-    performance:
-      maxLatencySeconds: 30
-      timeoutSeconds: 120

package/examples/skills/drupal-code-analysis/skill.ossa.yaml

@@ -1,111 +0,0 @@
-apiVersion: ossa/v1
-kind: Skill
-metadata:
-  name: drupal-code-analysis
-  version: "1.0.0"
-  description: >
-    Analyzes Drupal 7/8/9/10 codebases for migration readiness,
-    deprecated API usage, and module compatibility with Drupal 11.
-  did: "did:ossa:skill:drupal-code-analysis"
-  author:
-    name: Bluefly.io
-    did: "did:ossa:author:bluefly-io"
-    url: https://bluefly.io
-  license: Apache-2.0
-  labels:
-    domain: drupal
-    maturity: stable
-  created: "2026-02-23T00:00:00Z"
-spec:
-  description: >
-    Use when the user mentions Drupal migration, upgrade, code audit,
-    deprecated API usage, or module compatibility checking.
-    Analyzes PHP code for Drupal-specific patterns and generates
-    migration readiness reports.
-  categories:
-    - drupal
-    - migration
-    - code-analysis
-    - php
-  platforms:
-    - claude-code
-    - cursor
-    - codex-cli
-    - goose
-  allowedTools:
-    - bash
-    - file_read
-    - file_write
-    - web_search
-  runtimes:
-    php: ">=8.2"
-    node: ">=18"
-  dependencies:
-    tools:
-      - name: phpstan
-        type: cli
-        required: false
-      - name: phpcs
-        type: cli
-        required: false
-      - name: rector
-        type: cli
-        required: false
-  trust:
-    testsPassed: "47/47"
-    coverage: "94%"
-    lastAudit: "2026-02-15T00:00:00Z"
-  governance:
-    approvalRequired: false
-    maxAutonomy: 3
-    dataAccess:
-      filesystem: read-only
-      network: none
-      secrets: none
-    prohibitedActions:
-      - file_deletion
-      - credential_access
-      - external_network_calls
-  compliance:
-    - NIST-800-53
-  instructions: |
-    # Drupal Code Analysis
-
-    You are an expert Drupal migration analyst. When activated, analyze
-    the codebase for Drupal-specific patterns and provide actionable
-    migration guidance.
-
-    ## Analysis Steps
-
-    1. **Detect Drupal Version**: Check `.info.yml` files, `core/lib/Drupal.php`,
-       or `includes/bootstrap.inc` for version markers.
-
-    2. **Scan for Deprecated APIs**: Look for:
-       - `drupal_set_message()` → `\Drupal::messenger()->addMessage()`
-       - `db_query()` → database service injection
-       - `drupal_render()` → render service
-       - `l()` and `url()` → `Url::fromRoute()`
-       - `entity_load()` → entity type manager
-       - Hook implementations using `function hook_` patterns
-
-    3. **Check Module Compatibility**: For each custom/contrib module:
-       - Verify Drupal 11 compatibility via drupal.org API
-       - Check for removed/deprecated hooks
-       - Identify service container usage vs global functions
-
-    4. **Generate Report**: Produce a structured report with:
-       - Migration readiness score (0-100)
-       - Critical issues (must fix before upgrade)
-       - Warnings (should fix)
-       - Recommendations (nice to have)
-       - Estimated effort per module
-
-    ## Output Format
-
-    Always output a structured migration report with clear sections,
-    severity levels, and specific file:line references for each issue found.
-  tests:
-    - prompt: "Analyze this Drupal 9 module for Drupal 11 compatibility"
-      expectedBehavior: "Should scan PHP files for deprecated API calls and generate a migration readiness report"
-    - prompt: "Check if my custom module uses any deprecated Drupal functions"
-      expectedBehavior: "Should identify deprecated function calls and suggest modern replacements"

package/examples/skills/git-commit-review/skill.ossa.yaml

@@ -1,86 +0,0 @@
-apiVersion: ossa/v1
-kind: Skill
-metadata:
-  name: git-commit-review
-  version: "1.0.0"
-  description: >
-    Reviews git commits and staged changes for quality, security issues,
-    and conventional commit compliance before committing.
-  did: "did:ossa:skill:git-commit-review"
-  author:
-    name: OSSA Contributors
-  license: Apache-2.0
-  labels:
-    domain: git
-    maturity: stable
-spec:
-  description: >
-    Use when the user is about to commit, wants a pre-commit review,
-    or asks to check staged changes. Activates on mentions of
-    commit review, pre-commit check, or staged changes review.
-  categories:
-    - git
-    - code-review
-    - security
-  platforms:
-    - claude-code
-    - cursor
-    - codex-cli
-  allowedTools:
-    - bash
-    - file_read
-  governance:
-    approvalRequired: false
-    maxAutonomy: 2
-    dataAccess:
-      filesystem: read-only
-      network: none
-      secrets: none
-    prohibitedActions:
-      - git_push
-      - git_force_push
-      - file_deletion
-  instructions: |
-    # Git Commit Review
-
-    Review staged changes before commit. Check for quality, security,
-    and conventional commit compliance.
-
-    ## Pre-Commit Checklist
-
-    1. **Run `git diff --staged`** to see what will be committed
-
-    2. **Security scan**:
-       - No secrets (API keys, tokens, passwords) in diff
-       - No `.env` files or credentials being committed
-       - No hardcoded IPs or internal URLs
-
-    3. **Code quality**:
-       - No `console.log` / `print` debug statements
-       - No commented-out code blocks
-       - No TODO/FIXME without issue references
-       - No large binary files
-
-    4. **Conventional commit message**:
-       - Format: `type(scope): description`
-       - Types: feat, fix, docs, style, refactor, test, chore, ci
-       - Description in imperative mood ("add" not "added")
-       - Under 72 characters for subject line
-       - Body wraps at 100 characters
-
-    5. **Diff size check**:
-       - Warn if >500 lines changed (should split into smaller commits)
-       - Warn if >10 files changed (may be doing too much)
-
-    ## Output
-
-    Provide a summary:
-    - ✅ Passed checks
-    - ⚠️ Warnings (non-blocking)
-    - ❌ Issues (should fix before committing)
-    - Suggested commit message if not provided
-  tests:
-    - prompt: "Review my staged changes before I commit"
-      expectedBehavior: "Should run git diff --staged and check for secrets, debug statements, and suggest a commit message"
-    - prompt: "Check if my commit message follows conventional commits"
-      expectedBehavior: "Should validate the commit message format against conventional commit standards"