Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Ship skills for agentic use of Iris

Open
  • Is something wrong?
#560 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
cli, documentation, release, testing

Research direction

Start with the existing .agents/skills guide and the iris --help entry point, then inspect the release/install path to determine how a version-matched guide can ship with the single binary. Add checks for discovery, representative PureScript workspace tasks, and release inclusion; done means an installed Iris points agents to supported commands without relying on stale sidecar files.

Written by the indexing model from the issue text.

Description

Motivation

An agent may know PureScript and Spago but have no prior knowledge of Iris. It can discover iris --help, but help enumerates commands rather than teaching the workflow or explaining where Iris differs from familiar PureScript tooling. The existing .agents/skills guide contributors working on Iris, not agents using an installed Iris in a PureScript project.

Vercel's agent-browser offers a useful model: a small discovery skill points agents to substantive, version-matched instructions served by the installed CLI. This reduces reliance on stale model knowledge or web searches.

Goal

Make it easy for an unfamiliar agent to discover and correctly use the installed Iris version to work on a PureScript project.

Scope

  • Ship a concise, task-oriented skill for using Iris: discover or create a Spago workspace, add dependencies, build, interpret diagnostics, run/test, and know when to use Spago or other tools rather than inventing Iris commands. Document only behavior supported by the current CLI.
  • Provide a discovery path both from iris --help and from an installable agent skill. Keep the latter small enough to direct agents to the installed version's guide rather than duplicating a guide that may become stale.
  • Make the guide available with the installed CLI and match its version. Iris's current release installers extract a single binary, so consider embedding the content rather than assuming sidecar files are installed.
  • Keep user-facing usage guidance distinct from the repository's contributor skills.

Completion criteria

  • An agent without Iris-specific prior knowledge can find the guide and choose the correct Iris commands for a representative PureScript workspace task without guessing unsupported flags or subcommands.
  • The guide and CLI help are covered by appropriate checks, and the release/install path is verified to include the guide.
Dominant language
Rust
Stars
102
Forks
11
Avg merge
4h 17m
Merged PRs (30d)
129

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from purefunctor/purescript-iris

All issues in purefunctor/purescript-iris

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.