Your first job
Choose a small job, check its sources and turn useful work into a repeatable routine.
Pick a job you can check
Choose a small piece of real work with a clear source and finish line. Connect the relevant app first, or use a channel OpenTag can already read.
Good starting requests:
- “Find open GitHub pull requests older than a week and link the ones waiting for review.”
- “Read this week's #growth discussion and list decisions with their sources.”
- “Find pricing questions in my Gmail from the last two weeks and draft a response summary.”
Start with analysis or a draft so you can judge the result before asking for changes in another system.
State the scope
Include the account, time window and output. Ask in the channel where the result belongs, or in a DM for personal sources.
You
@OpenTag find open pull requests older than a week in our app repo. Group them by what is blocking them and link the sources.
Found 6 open pull requests older than a week: 3 awaiting review, 2 with failing checks and 1 draft.
The report links each pull request and its latest review or check. One check result was unavailable, so that item's status needs verification.
Want a short version for the engineering channel?
This is an illustrative result. Your answer should link the actual records it used and say what it could not verify. The GitHub connector is read-only; handing off code changes is a separate workflow.
Check and steer
Open a source. Check that OpenTag used the intended period and repository. Follow up in the thread: “Exclude drafts”, “Only the mobile repo”, or “Show this as a table”.
Requests consume credits according to the work performed. Check Usage after the job; there is no guaranteed price for this example.
Make useful work repeat
If the report is worth receiving regularly, ask for a schedule: “Do this every Monday at 09:00 Europe/London in #engineering.” Review the resulting routine and its first run.