I have Claude/Codex keep logs [1]. It's just prompted in my AGENTS.md [0].
> Every session must produce one of: a session log OR a plan, and end with a written summary appended to it. Default to a log; reserve plans for substantive design work.
It's incredibly valuable. For example today I started a few sessions off like this:
- What's the status of my work on Renovate?
- I was recently working on X, find that
- Did we fix the issue with backups? What are the next steps?
- This bug came up again. Didn't we fix it already?
I have a gaming PC and a steam deck. My goal was to use my steam deck as a steam link (their old streaming hardware) w/ a Xbox controller
Both are connected via Ethernet and actually the video quality was very very good, and input lag was completely fine.
Unfortunately there were so many issues. I want a console like experience where I can just decide that i want to pick up a controller and play.
With this setup I have to unlock windows which is annoying. Also often times something gets stuck so I have to walk to the desktop to fix/click around, or it plays audio via PC, or I have to disable HDR, etc.
Skills can be about as deterministic. Consider GitHub MCP vs skill for GH CLI.
It might use the view_pr tool, or `gh pr view`, but in the end it's still performing a deterministic action.
The benefit might be that the GH skill can contain more domain specific information about GitHub, and you only pay the context cost when the skill is read.
Personally I generally avoid MCP and have skills for CLIs -- if one doesn't exist, then I author one. For example I have a CLI for Grafana, Discord, Sentry, etc.