Skip to content

Feature: Expiring developer opportunity signals for agents #214

Description

@sajeetharan

Problem

accepts-agent-requests is too broad to communicate what kind of collaboration a developer wants now, and indefinite availability becomes stale.

Proposed Solution

opted-in structured opportunity signals with mandatory expiry.

MVP Scope

signal types OSS collaboration, MCP contributors, code review, mentorship, speaking, and custom; optional short context/project URL; expiry presets 7/30/90 days; renew/expire/delete; profile badge and filters; mission delta when a matching signal appears; introduction request prefilled with signal context but still requires approval.

Acceptance Criteria

only claimed profile owner can manage signals; expired signals disappear from public API/search and cannot trigger new alerts; visible expiry/freshness; custom text validation and abuse reporting path; no contact details exposed; API/MCP schema documented; tests for auth, expiry, filters, alert dedupe.

Privacy and Trust Constraints

no inferred availability and no default opt-in.

Success Metrics

active signals, renewal rate, signal-to-profile open, qualified introduction rate, decline/report rate.

Related Issues

#72, #73, #75.

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureNew feature requestgrowthFeatures to drive user growthpriority: P1High-value retention follow-upretentionFeatures to improve user retention

    Projects

    Status
    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions