Last checked with GitLab: . Status comes from GitLab using a 2-minute cache. Merge events clear affected cached statuses. An already-open page does not update itself. Refresh page.

An MR completes this bounty when it is merged into main with Closes #298 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.

Description

The public bounty API gains recognized interest and skill filters, but bounties_open currently accepts only app, tier, unclaimed and limit. Let members ask their coding agent for Dragon, research or other interest-specific work.

Who might enjoy this

  • Community interests: Community / knowledge sharing, Tech, Full stack
  • Skills: api, backend, qa
  • Experience: intermediate; work style: automation.
  • Readiness: ready; bounty size: S (existing points tier; standard merge award stacks separately).

Current behavior and starting points

Source-reviewed against main cf05b29c6256dba70d0ebc09b22cc9867cdb786a on2026-10-18. Check current main and related issues/MRs before implementing so existing work is reused.

Relevant Files

Deliverables

  • Add optional allowlisted interest, skill and experience arguments to bounties_open and pass them to the existing fixed Scoreboard API endpoint.
  • Render recognized returned interest metadata clearly while preserving existing tool arguments and compact output.
  • Document one request with interest=rf-sdr and skill=python, and keep unknown values or upstream errors explicit.

Dependencies and decisions

  • Foundation released: MR !331; the public interest/skill metadata endpoint is live.

Acceptance criteria

  • [ ] Add a focused executable harness exercising the actual bounties_open registration with a positive interest filter, invalid-value and upstream-failure controls; assert the exact outbound query and record its command.
  • [ ] Run pnpm --filter @irregularchat/search-mcp build and pnpm --filter @irregularchat/search-mcp lint; record one fixture-backed local MCP protocol call with returned task IDs, reusing the #216 protocol-client pattern when available.
  • [ ] Record named baseline failures and the exact commands used. A behavior fix includes a real route/database/protocol check observed failing before the change. Knowledge work includes source traceability and reproducible reviewer evidence.
  • [ ] Run the affected app's existing checks. Explain any baseline failures rather than reporting a matching failure count as proof.

Try it locally

Start from the existing source files above. The following is the target demo your contribution should enable; a newly proposed script or fixture is part of the deliverable:

Use the public /api/bounties?interest=rf-sdr endpoint and the existing bounties_open registration as the starting contract. A fixture-backed local protocol call requires no production write access.

Use public or synthetic examples. Starter work should run without production access; explicitly name any software/device prerequisite before claiming it is ready.

Out of scope

  • No bounty-detail tool (tracked separately), new model prompts, member profiling, new endpoint or publishing work.
  • Unrelated refactors, new services/providers, bulk dependency changes, production access changes, unrequested notifications, and copying private member material. Keep credentials and unresolved security findings outside the issue and repository.

For a coding agent and reviewer

Read AGENTS.md, applicable .cursor/rules/, app instructions and docs/contributing/agentic-bounty-review.md. Reuse the existing shared helpers, identity/access paths and app styling. Implement one bounded story and provide evidence the accepting app maintainer can reproduce. State updated / pre-release verified / released / live verified accurately.

A parent index carries no duplicate award for these child deliverables. Open one scoped MR using this issue's actual number after the closing keyword. Link your GitLab identity on Scoreboard; the existing merge webhook handles eligible points.

Catalog index: #258.

<!-- community-interest-bounty:2026-10-18:mcp-interest-discovery -->

Relevant files

Hints

No hints yet.

Activity

  • +50 Hugo Zarate earned S bounty Oct 25

Comments

No comments yet. Be the first to weigh in.

↑ Top