Ai Research Eta Optimization

v1.0.0

Optimizes AI research ETAs with dynamic updates, parallel execution, smart filtering, and template-driven workflows to accelerate prospect analysis by 2-5x w...

0· 48·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (ETA optimization for AI research) matches the SKILL.md content: protocols for initial estimates, parallelization, filtering, templates, and communication. There are no unexpected binaries, config paths, or environment variables requested that would be unrelated to this purpose.
Instruction Scope
Instructions direct concurrent web_search() calls, verification against public sources (LinkedIn, org charts, SEC filings, 'dark web' claims) and to send stakeholder progress updates. Those actions are consistent with prospect research, but the SKILL.md leaves communication methods and external endpoints unspecified—giving an agent discretion about how updates are sent and what external services/APIs are used.
Install Mechanism
No install spec and no code files — the skill is instruction-only, so nothing is written to disk or pulled from external URLs during installation.
Credentials
The skill requests no environment variables or credentials, which is appropriate for a guidance-only skill. However, it references data sources (LinkedIn, SEC filings, other high-signal sources) that in practice may require API keys or access methods; the SKILL.md does not declare or justify any such credentials.
Persistence & Privilege
The skill does not request persistent presence (always:false), does not modify other skills or system configs, and requires no privileged access.
Assessment
This skill appears coherent and lightweight, but before installing consider: (1) confirm how your agent will perform web_search() and what connectors it will use (some sources need API keys or paid access); (2) decide and lock down how progress updates/notifications are delivered (email, Slack, etc.) to avoid accidental data leaks; (3) be cautious about scraping or collecting personal data (LinkedIn, org charts) and ensure you comply with privacy/legal rules; (4) test the workflow on non-sensitive sample tasks to verify it doesn't attempt to access undeclared services or credentials. If you require the skill to use specific APIs, plan to provide those credentials through your normal secure channels rather than expecting the skill to create them.

Like a lobster shell, security has layers — review code before you run it.

latestvk9757qsgc4m3xxcded14ejtx7h84p3kv

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments