# Chairman daily report

A daily briefing workflow that turns business metrics, market changes, and external signals into one report.

## Agent Install Policy

Agents must get explicit user confirmation before installing a skill, writing configuration, or changing the local environment.

1. Read this guide and the manifest: https://qveris.ai/skills/chairman-daily-report/manifest.json
2. Explain to the user what will be installed and which QVeris API actions may be used.
3. Ask for explicit approval before running an install command or changing local configuration.
4. After approval, install the skill and run one starter prompt.

## Official GitHub Source

- Repository: https://github.com/QVerisAI/open-qveris-skills
- Skill path: chairman-daily-report
- Skill source: https://github.com/QVerisAI/open-qveris-skills/tree/main/chairman-daily-report
- Clone and inspect: `git clone https://github.com/QVerisAI/open-qveris-skills.git && cd open-qveris-skills/chairman-daily-report`

## Install Commands

- OpenClaw: `openclaw skills install chairman-daily-report`

## Starter Prompts

### Executive daily brief
Combine internal context with market and public signals.

```text
Create a daily executive brief for our company. Include market changes, competitor updates, content platform signals, and the three most important decisions leadership should review.
```

### Market monitor
Track the outside world and summarize what changed.

```text
Monitor today's market, news, and social platform signals for the AI agent infrastructure sector. Summarize what changed, what matters, and which QVeris capabilities were used.
```

## QVeris API Actions

- Discover `POST /search`: Search for market data, news, social signals, and other report-ready data sources.
- Inspect `POST /tools/by-ids`: Check each source before it becomes part of a recurring leadership report.
- Call `POST /tools/execute`: Execute selected capabilities and structure outputs into a concise daily brief.

## Estimated QVeris Usage

Recurring reports usually combine multiple public data sources, so the paid portion scales with the number of sections and providers called.

- Typical paid Call executions: 4-12
- Planning estimate: 4-120 credits
- Free actions: Discover, Inspect
- Paid actions: Call
- Note: Keep scheduled reports bounded by specifying the exact tickers, competitors, or signal sources to call.

## Related Cases

- [Agent action over time](https://qveris.ai/blog/agent-action-long-term) - Why recurring agent workflows need reliable external capabilities.
- [TikHub content platform signals](https://qveris.ai/blog/qveris-tikhub-content-platform-signals) - Use public platform signals as part of operational reporting.

## Human Page

https://qveris.ai/skills/chairman-daily-report