Skip to content

LeoYeAI/agent-master-skills / skills/autoskill

autoskill

Verified

Analyzes user-requested Screenpipe history windows to detect repeated research workflows, match existing scientific skills, and stage new skill drafts or composition recipes for review. Requires a reachable Screenpipe HTTP API, normally on localhost:3030. Detection and embedding inference run locally; the selected LLM receives redacted app/title cluster summaries and matched skill descriptions. Use only when the user explicitly asks to analyze their recent work and propose skills.

FileKindSize
.gitignoreother34 B
SKILL.mdskill md16.5 KB
config.yamlconfig2.1 KB
references/api-contracts.mdmarkdown7.4 KB
references/https-proxy.mdmarkdown2.2 KB
references/screenpipe-config.yamlconfig1.4 KB
scripts/autoskill.pyscript1.1 KB
scripts/backends.pyscript5.1 KB
scripts/cluster.pyscript1.7 KB
scripts/doctor.pyscript4.5 KB
scripts/fetch_window.pyscript2.8 KB
scripts/match_skills.pyscript1.2 KB
scripts/promote.pyscript1.5 KB
scripts/redact.pyscript1.6 KB
scripts/run.pyscript7.4 KB
scripts/synthesize.pyscript2.7 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. Loopback HTTP is supported for same-host use. Keep the listener on loopback; transport encryption does not replace endpoint authentication or protect against other processes on the host.

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).

The example below keeps the proxy loopback-only. Caddy's `tls internal` creates a local CA and attempts to install it into local trust stores when permitted. Python's HTTPX may use a different trust store.

## Caddy

Install:

```bash
brew install caddy   # macOS
# or see https://caddyserver.com/docs/install
```

Add to your `Caddyfile`:

```caddyfile
screenpipe.local {
    bind 127.0.0.1
    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
```

HTTPX verifies HTTPS by default and normally uses certifi, which may not include
Caddy's local CA. Set `SSL_CERT_FILE` to a PEM CA bundle trusted for this service
(including the Caddy root, and public roots if the same process calls a cloud LLM).
Do not disable certificate verification to work around trust errors. A Caddy
proxy bound off-host also needs access controls; TLS alone is not authorization.
The Screenpipe bearer token is still required for protected API routes.

This configuration was documentation-reviewed, not deployed during maintenance.
Sources: [Caddy local HTTPS](https://caddyserver.com/docs/automatic-https) and
[HTTPX SSL configuration](https://www.python-httpx.org/advanced/ssl/).

## 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.
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall