Review team usage
Read billing metrics and daily usage with explicit period and timezone.
Read OOMOL billing summary and usage breakdown for [days] days with UTC offset [offset], then explain major usage sources.
Leina connects to OOMOL Console to help you review team usage and check team connection permissions. Ask in your team chat. Leina does the work and brings back the result.
Connect OOMOL Console, choose what to share, and hand off your first task.
You
Review my current OOMOL team for the last 7 days in UTC+8. Show credit spent, total metered events, and the busiest day.
Leina
The team spent 24 credits across 120 metered events. October 10 had the most activity, with 40 events.
OOMOL Console · Usage summary
Team usage · 7 days
Daily totals use UTC+8 boundaries.
AI can use OOMOL Console to explain team usage, inspect team connections, and manage permission groups within your access rights. It can also inspect published skills and manage team package access.
You specify the source and the destination. Leina uses the content available to your connection and returns the result for you to review.
OOMOL Console is the account and team workspace for OOMOL billing, members, connections, and skill package access.
Visit Provider Website ↗Retrieve team credit spent for the requested 7-day window.
Use the same time window and UTC+8 boundaries for usage records.
Count events by day and distinguish activity counts from credit spent.
Copy a prompt, add your details, and send it to Leina in your connected team chat.
Read billing metrics and daily usage with explicit period and timezone.
Read OOMOL billing summary and usage breakdown for [days] days with UTC offset [offset], then explain major usage sources.
Read team connections and a selected connection's permission groups.
List current-team OOMOL Connections, then read permission groups for Connection app ID [app ID] and summarize assignments.
Inspect published skill packages and grant or revoke team package access.
My bot is a team member but cannot install [package name]. Check its identity, team membership, and the team skill configuration, then fix missing package access if authorized.
Your next OOMOL Console task can start with a message.
Tell Leina what you need in your team chat. Include the source, destination, and expected result.
Use your authenticated OOMOL account and current team scope.
Share the source material, say where the result belongs, and describe what you need.
Review the result and any changes in the connected app.
Hand off these everyday tasks to your AI employee.
List skill packages maintained by the authenticated identity, including its private packages. A bot's results do not list its owner's packages. Supports keyword search and pagination.
List skill packages configured for the current team. Team membership alone does not grant access to an unconfigured private package. This lists team configuration, not local installations.
Grant the current team access to an entire registry package, including its private skills. Requires package access and team write permission. Does not make the package public or install it locally.
Revoke the current team's access through this package binding for the entire registry package. Requires package access and team write permission. Does not delete the package, change its visibility, remove other access grants, or uninstall local skills.
Return the current OOMOL team scope and authenticated principal.
List the OOMOL teams the authenticated user or service account belongs to.
Return metadata and member counts for the current OOMOL team.
Return every available balance lot owned by the current OOMOL team creator. This account balance may be shared by multiple teams.
Return current-team billing and usage metrics together with the team creator account balance.
Return the current OOMOL team daily usage breakdown by source and subject.
List members of the current OOMOL team.
List the current-team Connections visible to the authenticated user or service account.
List the default and custom permission groups for one current-team Connection.
Replace the action permission of a Connection's non-deletable default permission group.
Create a custom Connection permission group and replace the assignments of its members.
Replace the name, member assignments, and action permission of a custom Connection permission group.
Delete a custom Connection permission group so its members return to the default group.
Add an OOMOL user to the current team with the member role.
List current-team Connection execution records visible to the authenticated user or service account.
Connect the Apps your work depends on, and give Leina the context to carry the task forward.
Hand off a task while your team is discussing it. Leina uses your connected tools and brings the result back to the conversation.
See How Leina Works in SlackThe team spent 24 credits across 120 metered events. October 10 had the most activity, with 40 events.
No separate provider key is needed. Actions use your authenticated OOMOL account or service account and its permitted team scope.
Changing permission groups requires a user principal with team management permissions. Service accounts can only read them. The assistant reads the current configuration and revision before submitting changes to avoid overwriting concurrent updates.
Yes. Provide the connection’s app ID to review its visible execution records, including status and available error details.
Membership alone does not share an unconfigured private package. An identity with package access and team write permission must add the package to the team. This grants team access without making the package public; installation still uses the recipient’s own credentials.
Start with one task you already need to do. Tell Leina what a finished result should look like.
Connect OOMOL Console, choose what to share, and hand off your first task.