gws-admin-reports
by googleworkspacegws-admin-reports helps with Google Workspace Admin SDK Reports API tasks, including audit log lookups, usage reports, and watch channels. Use it for structured Reporting workflows with gws admin-reports resource and method commands, not broad API exploration.
This skill scores 79/100, which means it is a solid directory candidate: it gives users enough concrete API scope, invocation shape, and resource/method coverage to justify installation, though it still leaves some execution details to the shared prerequisite docs. For directory users, this is a useful, task-specific skill for Google Workspace admin reporting workflows rather than a placeholder or generic stub.
- Explicit trigger path and command form (`gws admin-reports <resource> <method> [flags]`) make it easy for an agent to invoke correctly.
- Covers real Admin SDK reporting surfaces such as activities, customerUsageReports, entityUsageReports, and userUsageReport, which provides concrete workflow value.
- Frontmatter includes versioning and binary requirement (`gws`), improving install-time clarity and trustworthiness.
- The skill depends on `../gws-shared/SKILL.md` for auth, global flags, and security rules, so it is not fully self-contained.
- No install command, scripts, or supporting reference files are present, which limits progressive disclosure and hands-on guidance inside this skill.
Overview of gws-admin-reports skill
What gws-admin-reports does
The gws-admin-reports skill helps you work with Google Workspace Admin SDK Reports API tasks such as audit log lookups, usage reports, and watch channels. It is built for users who need structured reporting data from Workspace, not for general Google API exploration. If you need a fast way to query activities, customer usage, or entity usage with the gws CLI, this skill gives you the right command shape and resource mapping.
Who should use it
Use the gws-admin-reports skill if you are validating admin activity, checking adoption or usage trends, or automating report retrieval for a Workspace tenant. It is a good fit for admins, operations teams, and agents that need Reporting output with less guesswork than hand-crafting API calls.
What makes it different
The main value of gws-admin-reports is that it narrows the problem to the Reports API resources and methods that actually exist in the skill: activities.list, activities.watch, channels.stop, customerUsageReports.get, and entityUsageReports.get. That makes it more reliable than a generic prompt because the skill centers the expected gws admin-reports <resource> <method> workflow and reminds you that shared auth and global flags live in ../gws-shared/SKILL.md.
How to Use gws-admin-reports skill
Install and locate the shared prerequisites
Install gws-admin-reports through the gws skill workflow, then read ../gws-shared/SKILL.md before running anything. The repository explicitly treats the shared skill as required for authentication, global flags, and security behavior. If the shared file is missing in your environment, run gws generate-skills first so the prerequisite is created.
Build a complete request from a rough goal
A weak prompt like “check Workspace activity” is usually not enough. A better gws-admin-reports usage prompt names the resource, method, and the reporting question you want answered, for example: “Use gws admin-reports activities list to review Drive activity for the last 24 hours and summarize unusual events.” For reporting work, include the target application, customer scope, time window, and whether you need raw records or a concise summary.
Start with the right source files
For the gws-admin-reports guide, start with SKILL.md and then inspect ../gws-shared/SKILL.md for cross-skill requirements. In this skill, the command patterns and resource list are the main decision points, so you usually do not need a large support tree to understand it. Focus on the method descriptions first, then map your use case to activities, customerUsageReports, or entityUsageReports.
Use the reporting resources intentionally
Choose activities.list for audit-style event review, activities.watch when you need push notifications, channels.stop when you must end a watch channel cleanly, and customerUsageReports.get or entityUsageReports.get for usage snapshots. This is the core of the gws-admin-reports install decision: it is strongest when your job matches one of those report types and weakest when you want broad data analysis outside the Reports API.
gws-admin-reports skill FAQ
Is gws-admin-reports only for Reporting?
Yes, this skill is centered on Google Workspace Reporting via the Admin SDK. If your task is mail, Drive file management, or unrelated admin automation, gws-admin-reports is probably the wrong skill.
Do I need to know the API before using it?
Not much. The gws-admin-reports skill is useful precisely because it turns a reporting goal into a narrower command path. You still need to provide enough context for the report you want, but you do not need to memorize every endpoint before installing it.
When should I not use this skill?
Do not use it if you need ad hoc analysis across multiple systems, if you do not have the shared gws authentication setup, or if you only want a one-off natural-language explanation instead of a real report request. In those cases, a generic prompt or a different skill may be a better fit.
How is it different from a normal prompt?
A normal prompt may describe the outcome, but gws-admin-reports gives you a concrete resource-and-method workflow for Reporting. That reduces ambiguity around what to call, which is especially helpful when the task is specific to Workspace audit logs or usage reports.
How to Improve gws-admin-reports skill
Give the report shape up front
The best gws-admin-reports skill inputs specify the tenant context, the resource, the method, and the exact reporting goal. For example, instead of “show admin activity,” say “list Drive activities for the last 7 days for this customer and flag permission changes.” Better inputs produce better filtering, better summaries, and fewer follow-up corrections.
Be explicit about scope and time range
Most Reporting mistakes come from vague scope. Tell the skill whether you want a single customer, a specific application, a day range, or a usage snapshot by entity. If the task is gws-admin-reports for Reporting, the time window and target resource usually matter more than prose style.
Iterate from raw report to decision
First ask for the report data or command, then refine for interpretation. If the first output is too broad, narrow it by application, event type, or date range; if it is too narrow, ask for a grouped summary or a comparison across periods. That iterative loop is usually more effective than trying to force a perfect final prompt on the first try.