activity
Skill2 starsChanged 4 months agoMITView on GitHub
View transaction history and recent account activity. Invoke when the user asks about past spending, wants to verify a payment went through, check if an order completed, review wallet transfers, or see a log of all account actions. Covers wallet transfers, faucet drops, API payments, shopping checkouts, agent registrations, and session approvals.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- egregore-labs/egregoretheir own version, first seen Nov 6, 2026
- gr219/OpenBA-Kittheir own version, first seen Oct 25, 2026
- spmtitsolution/OpenBA-Kittheir own version, first seen Oct 20, 2026
- anthonysuherli/br8ntheir own version, first seen Oct 13, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- egregore-labs/egregore★ 293same name
- spmtitsolution/OpenBA-Kit★ 38same name
- anthonysuherli/br8n★ 1same name
- gr219/OpenBA-Kit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- attach-sessionSkill
- authenticate-userSkill
- defi-auto-repaySkill
- defi-swapSkill
- form-session-delegationSkill
- kite-discoverySkill
- kite-passportSkill
- manage-agentsSkill
- passport-overviewSkill
- Passport SetupSkill
- report-feedbackSkill
- request-sessionSkill
- shoppingSkill
- upgrade-passportSkill
- wallet-sendSkill
- x402-executeSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 3 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Prerequisite: Before using any Passport skill, check if kpass is installed by running command -v kpass.
- Very specific: line 36
If the user wants to send tokens or check wallet balance, use the wallet-send skill.
- Very specific: line 37
If the user wants to execute a payment through a session, use the x402-execute skill.
- Very specific: line 38
If the user wants to list agents or sessions, use the manage-agents skill.
- Very specific: line 39
If the user wants to search products or checkout, use the shopping skill.
- Distinctive: line 45
No agent registration or spending session is required.
- Distinctive: line 61
When presenting activity events to the user, format each event as a card:
- Distinctive: line 99
Do NOT attempt any of the following.
- Very specific: line 114
To send tokens or check balance: Use the wallet-send skill.
- Very specific: line 115
To execute API payments: Use the x402-execute skill.
- Very specific: line 116
To list agents and sessions: Use the manage-agents skill.
- Very specific: line 117
To search products or checkout: Use the shopping skill.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Activity Feed
Prerequisite: Before using any Passport skill, check if kpass is installed by running command -v kpass. If it returns nothing, invoke the passport-setup skill first to install the CLI.
View recent account activity for the authenticated user. Returns a paginated list of activity events including wallet transfers, faucet drops, x402 API payments, agent registrations, session approvals, passkey registrations, and shopping checkouts.
Reference files (read when you need exact detail):
@references/commands.md— full command reference, argument table, activity kinds, every JSON output shape, and the input validation checklist.@references/examples.md— worked examples (view all recent activity, filter by kind, paginate).
When to Use This Skill
- The user asks "show me my recent activity" or "what have I done recently?"
- The user asks "show me my transaction history" or "what transactions have I made?"
- The user wants to review spending history or verify a payment went through.
- The user asks "did my shopping checkout go through?" or "show me my purchases."
- You need to verify an action was recorded (e.g., confirm a wallet transfer completed).
- The user asks to filter activity by type (e.g., "show me only my wallet transfers").
When NOT to Use This Skill
- If the user wants to send tokens or check wallet balance, use the
wallet-sendskill. - If the user wants to execute a payment through a session, use the
x402-executeskill. - If the user wants to list agents or sessions, use the
manage-agentsskill. - If the user wants to search products or checkout, use the
shoppingskill.
Prerequisites
The user MUST be authenticated before using this skill. If not logged in (exit code 3 with "Not logged in"), use the authenticate-user skill first.
No agent registration or spending session is required. This command uses the user's JWT directly.
Defaults (Do Not Ask the User Unless They Specify Otherwise)
| Setting | Default value | Override |
| Output format | --output json | Always use JSON output. Never omit this flag. |
| Kind filter | Omit (returns all kinds) | Only pass --kind when the user asks to filter by activity type. |
| Limit | Server default (20, omit) | Only pass --limit if the user requests pagination or you need to limit results. |
| Offset | 0 (omit) | Only pass --offset for pagination when combined with --limit. |
| Base URL | Omit (uses built-in default) | Only pass --base-url if the user explicitly provides a custom backend URL. |
Display Cards (MANDATORY)
When presenting activity events to the user, format each event as a card:
For transaction events (wallet_transfer, wallet_faucet, x402_payment — NOT shopping_checkout, which always uses the dedicated template below):
{title} -- {status} Kind: {kind} | {occurred_at} Amount: {details.transaction.amount_raw ÷ 10^details.transaction.decimals} {details.transaction.asset_symbol} | Chain: {details.transaction.chain_name} Tx: {details.transaction.tx_hash}
For shopping checkout events (shopping_checkout):
{title} -- {status} Kind: shopping_checkout | {occurred_at} Items: {details.transaction.shopping.item_count} ({details.transaction.shopping.item_titles joined}) Total: {details.transaction.shopping.total_amount_display} | Order: {details.transaction.shopping.order_id} Tx: {details.transaction.tx_hash}
For non-transaction events (agent_registration, session_approval, passkey_registration):
{title} -- {status} Kind: {kind} | {occurred_at}
Error Handling
| Exit Code | Meaning | Error Message Pattern | Recovery Action |
| 0 | Success | status: "success" | Present the result to the user. |
| 1 | Network error | network error: ... | Check connectivity. Retry after a brief pause. |
| 2 | Usage error | --limit must be an integer between 1 and 100, --offset must be a non-negative integer | Fix the flag value. See validation rules in @references/commands.md. |
| 3 | Auth error | Not logged in. Run ... | Use the authenticate-user skill to log in. |
| 5 | Rate limited | rate limit | Wait 30 seconds, then retry. |
| 6 | Session policy violation | N/A for activity | Activity commands do not use spending sessions. This exit code is not expected. |
See @references/commands.md for the exact error envelope of every state.
Commands That DO NOT Exist
Do NOT attempt any of the following. They will fail:
kpass activity list-- does not exist; usekpass activitydirectlykpass activity --type-- the flag is--kind, not--typekpass activity --filter-- does not exist; use--kindkpass transactions-- does not exist; usekpass activitykpass history-- does not exist; usekpass activitykpass activity --status-- does not exist; status is part of the event data, not a filter- Any command with
--json-- the correct flag is--output json(two separate tokens)
Cross-Skill References
- Prerequisite: User must be logged in. Use the
authenticate-userskill. - To send tokens or check balance: Use the
wallet-sendskill. - To execute API payments: Use the
x402-executeskill. - To list agents and sessions: Use the
manage-agentsskill. - To search products or checkout: Use the
shoppingskill.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

