charlieviettq/awesome-agent-skill / .claude/skills/autoskill
autoskill
VerifiedObserve the user's screen via screenpipe, detect repeated research workflows, match them against existing scientific-agent-skills, and draft new skills (or composition recipes that chain existing ones) for the patterns not yet covered. Use when the user asks to analyze their recent work and propose skills based on what they actually do. Requires the screenpipe daemon (https://github.com/screenpipe/screenpipe) running locally on port 3030 — the skill has no other data source and will refuse to run if screenpipe is unreachable. All detection runs locally; only redacted cluster summaries reach the LLM.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.1 KB |
| config.yaml | config | 2.0 KB |
| references/https-proxy.md | markdown | 1.5 KB |
| references/screenpipe-config.yaml | config | 1.5 KB |
| scripts/autoskill.py | script | 1.1 KB |
| scripts/backends.py | script | 2.3 KB |
| scripts/cluster.py | script | 1.7 KB |
| scripts/doctor.py | script | 3.4 KB |
| scripts/fetch_window.py | script | 1.1 KB |
| scripts/match_skills.py | script | 1.3 KB |
| scripts/promote.py | script | 1.5 KB |
| scripts/redact.py | script | 1.6 KB |
| scripts/run.py | script | 7.2 KB |
| scripts/synthesize.py | script | 2.3 KB |
| tests/conftest.py | script | 113 B |
| tests/smoke_lmstudio.py | script | 2.0 KB |
| tests/test_backends.py | script | 4.2 KB |
| tests/test_cli.py | script | 1.5 KB |
| tests/test_cluster.py | script | 2.7 KB |
| tests/test_doctor.py | script | 3.0 KB |
| tests/test_e2e.py | script | 11.9 KB |
| tests/test_fetch_window.py | script | 3.7 KB |
| tests/test_match_skills.py | script | 2.5 KB |
| tests/test_promote.py | script | 3.5 KB |
| tests/test_redact.py | script | 4.5 KB |
| tests/test_run.py | script | 8.0 KB |
| tests/test_synthesize.py | script | 3.1 KB |
references/https-proxy.md
View on GitHub# Optional: TLS for localhost screenpipe access
Screenpipe's HTTP server (Axum, binding `localhost:3030`) speaks plain HTTP. For a Python script running as the same user on the same host, plain HTTP is adequate — loopback traffic never hits a network adapter, so TLS provides no additional confidentiality.
TLS on localhost is only useful when:
- A corporate security policy mandates "TLS everywhere" regardless of transport.
- The screenpipe endpoint is tunneled or exposed off-host.
- A browser client requires a "secure context" (Service Workers, WebCrypto).
If you need it, put a one-line Caddy reverse proxy in front. Caddy's `tls internal` generates and trusts a local CA automatically.
## Caddy
Install:
```bash
brew install caddy # macOS
# or see https://caddyserver.com/docs/install
```
Add to your `Caddyfile`:
```caddyfile
screenpipe.local {
tls internal
reverse_proxy localhost:3030
}
```
Ensure `screenpipe.local` resolves to loopback (add to `/etc/hosts`):
```
127.0.0.1 screenpipe.local
```
Start Caddy:
```bash
caddy run
```
Then update autoskill's `config.yaml`:
```yaml
screenpipe:
url: https://screenpipe.local
```
No code change is required on the autoskill side. `httpx` handles both HTTP and HTTPS transparently.
## mkcert (alternative)
If you prefer managing the cert yourself instead of Caddy's internal CA:
```bash
brew install mkcert
mkcert -install
mkcert localhost 127.0.0.1
```
Then terminate TLS with nginx, Caddy, or stunnel using the generated cert.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |