BytesAgain is a curated directory of 60,000+ AI agent skills from ClawHub, GitHub, LobeHub, and Dify. Search skills by keyword in 7 languages, browse by role (developer, creator, trader, marketer) or by use case.

How do I find AI skills on BytesAgain?

Use the search bar on BytesAgain.com to search by keyword in 7 languages. You can also browse by role (developer, creator, trader, marketer) or by use case. Each skill shows install instructions for Claude, Cursor, OpenClaw, Continue, and more.

Yes, BytesAgain is completely free. No registration required for searching skills. The MCP API is also free with rate limits.

Does BytesAgain have an API for AI agents?

Yes! BytesAgain provides a free MCP SSE endpoint at /api/mcp/sse for AI agents, plus a REST API at /api/mcp?action=search&q= . No authentication needed.

Can I request a new AI skill on BytesAgain?

Yes! Visit the Requests page on BytesAgain.com to submit a skill request. Your request will be visible to the community and notified to the site admin.

🦀 ClawHub

WorkIQ

by @likudo95

Query Microsoft 365 data (emails, meetings, documents, Teams messages, people) using WorkIQ CLI

Versionv1.0.0

Installs1

#clawhub

⚡ When to Use

Trigger	Action
- Emails — "What did Sarah say about the budget?", "Find emails about project X"
- Calendar / meetings — "What's on my calendar tomorrow?", "Who attended the standup last Friday?"
- Documents / files — "Find my recent PowerPoints", "Summarize the Q4 spec document"
- Teams messages — "Summarize today's messages in the Engineering channel"
- People / org — "Who is working on Project Alpha?", "Who is my manager?"
- Meeting notes — "What issues were raised in yesterday's Contoso meeting?"
### How to query
Use the `exec` tool to run WorkIQ. Prefer the global CLI if available, otherwise fall back to npx.
If `workiq` is on PATH:
```bash
workiq ask -q ""
```
If only `npx` is available (Node.js required):
```bash
npx -y @microsoft/workiq ask -q ""
```
With a specific Entra tenant ID:
```bash
workiq ask -t -q ""
```
### Query guidelines
- Write questions in natural language — WorkIQ understands context
- Be specific: include names, dates, project names, or channel names when known
- WorkIQ CLI is stateless per call — for follow-ups, include full context in each question
- WorkIQ only returns data the signed-in user has permission to see
- Do not pipe or combine WorkIQ output with other shell commands — run it standalone
### Example queries
\| User intent \| Command \|
\|---\|---\|
\| Recent emails on a topic \| `workiq ask -q "What did John say about the proposal last week?"` \|
\| Tomorrow's calendar \| `workiq ask -q "What meetings do I have tomorrow?"` \|
\| Find a document \| `workiq ask -q "Find my recent documents about Q4 planning"` \|
\| Teams channel summary \| `workiq ask -q "Summarize today's messages in the Engineering channel"` \|
\| People lookup \| `workiq ask -q "Who is working on Project Alpha?"` \|
\| Meeting notes \| `workiq ask -q "What issues were raised in yesterday's Contoso meeting?"` \|
\| Spec document \| `workiq ask -q "Summarize the key requirements in the user portal spec document"` \|
\| Emails from a person \| `workiq ask -q "Summarize emails from Sarah about the budget"` \|
### First-time setup
If WorkIQ has never been used, the EULA must be accepted first. Tell the user to run:
```bash
workiq accept-eula
```
If WorkIQ is not installed at all:
```bash
npm install -g @microsoft/workiq
workiq accept-eula
```
### Error handling
\| Error \| Action \|
\|---\|---\|
\| Auth / sign-in prompt \| Tell the user to run `workiq ask` manually in their terminal to complete the interactive sign-in flow \|
\| EULA not accepted \| Prompt the user to run `workiq accept-eula` \|
\| No results / empty response \| Rephrase the question with more context, a different time range, or more specific names \|
\| Permission denied \| User may lack an M365 Copilot license or admin consent for the WorkIQ app in their Entra tenant \|
\| `workiq` not found \| Prompt the user to install: `npm install -g @microsoft/workiq` \|

View on ClawHub

TERMINAL

clawhub install workiq

🧪 Use this skill with your agent

Most visitors already have an agent. Pick your environment, install or copy the workflow, then run the smoke-test prompt above.

Manusinvite

Task-oriented agent. Great for testing AI skills end-to-end.

Try Manus →

OpenClaw

Local-first agent. Install skills via ClawHub CLI.

Set up OpenClaw →

Claude Code

Anthropic's coding agent. Paste the prompt or SKILL.md into your session.

Claude Code docs →

Cursor

AI-powered IDE. Use the smoke-test prompt in Cursor Agent.

Open Cursor →

Continue.dev

Open-source AI code assistant. Add SKILL.md as a custom tool.

Continue docs →

Windsurf

Agentic IDE by Codeium. Paste the prompt into Cascade.

Try Windsurf →

Cline

VS Code extension for autonomous coding with MCP tools.

Cline on GitHub →

Copilot Workspace

GitHub's AI dev environment. Suitable for code-generation skills.

Copilot Workspace →

Trigger	Action
- Emails — "What did Sarah say about the budget?", "Find emails about project X"
- Calendar / meetings — "What's on my calendar tomorrow?", "Who attended the standup last Friday?"
- Documents / files — "Find my recent PowerPoints", "Summarize the Q4 spec document"
- Teams messages — "Summarize today's messages in the Engineering channel"
- People / org — "Who is working on Project Alpha?", "Who is my manager?"
- Meeting notes — "What issues were raised in yesterday's Contoso meeting?"
### How to query
Use the `exec` tool to run WorkIQ. Prefer the global CLI if available, otherwise fall back to npx.
If `workiq` is on PATH:
```bash
workiq ask -q ""
```
If only `npx` is available (Node.js required):
```bash
npx -y @microsoft/workiq ask -q ""
```
With a specific Entra tenant ID:
```bash
workiq ask -t -q ""
```
### Query guidelines
- Write questions in natural language — WorkIQ understands context
- Be specific: include names, dates, project names, or channel names when known
- WorkIQ CLI is stateless per call — for follow-ups, include full context in each question
- WorkIQ only returns data the signed-in user has permission to see
- Do not pipe or combine WorkIQ output with other shell commands — run it standalone
### Example queries
\| User intent \| Command \|
\|---\|---\|
\| Recent emails on a topic \| `workiq ask -q "What did John say about the proposal last week?"` \|
\| Tomorrow's calendar \| `workiq ask -q "What meetings do I have tomorrow?"` \|
\| Find a document \| `workiq ask -q "Find my recent documents about Q4 planning"` \|
\| Teams channel summary \| `workiq ask -q "Summarize today's messages in the Engineering channel"` \|
\| People lookup \| `workiq ask -q "Who is working on Project Alpha?"` \|
\| Meeting notes \| `workiq ask -q "What issues were raised in yesterday's Contoso meeting?"` \|
\| Spec document \| `workiq ask -q "Summarize the key requirements in the user portal spec document"` \|
\| Emails from a person \| `workiq ask -q "Summarize emails from Sarah about the budget"` \|
### First-time setup
If WorkIQ has never been used, the EULA must be accepted first. Tell the user to run:
```bash
workiq accept-eula
```
If WorkIQ is not installed at all:
```bash
npm install -g @microsoft/workiq
workiq accept-eula
```
### Error handling
\| Error \| Action \|
\|---\|---\|
\| Auth / sign-in prompt \| Tell the user to run `workiq ask` manually in their terminal to complete the interactive sign-in flow \|
\| EULA not accepted \| Prompt the user to run `workiq accept-eula` \|
\| No results / empty response \| Rephrase the question with more context, a different time range, or more specific names \|
\| Permission denied \| User may lack an M365 Copilot license or admin consent for the WorkIQ app in their Entra tenant \|
\| `workiq` not found \| Prompt the user to install: `npm install -g @microsoft/workiq` \|