completely redesigned the post detail page around this.. PITAS Analytics is the most advanced analytics available for your TikTok accounts
you get the full picture on every post: retention, traffic sources, demographics, locations, performance over time. the same data you would get if you were running the accounts manually, but across every single post in all your accounts in your grid
but the real unlock? to pipe it all into Claude, OpenClaw, whatever you use via MCP or API. imagine asking "which hooks drove the most retention this week across all 50 accounts" and getting an answer in seconds
Announcing PITAS Analytics: full post intelligence.
Views, play time, retention, traffic sources, audience demographics, locations, and performance over time. From post, from account. One dashboard.
Connect it to Claude, OpenClaw, or your favorite AI tool via MCP or API.
@pushpak1300 You were right, package-lock.json was lurking locally (gitignored) at [email protected], while package.json already had ^2.3.4. Since boost/skills/echo-development ships in 2.3.4+, boost couldn't find it and stripped it from boost.json every run π
@pushpak1300 I'm having a weird behaviour with the boost.json I can't figure out. I currently have a list of skills:
```
"skills": [
"ai-sdk-development",
"laravel-best-practices",
"configuring-horizon",
"mcp-development",
"pennant-development",
"socialite-development",
"pest-testing",
"inertia-react-development",
"echo-react-development",
"tailwindcss-development",
"echo-development",
"medialibrary-development"
]
```
... but every time I run a `boost:update` it removes a few of them:
```
- "inertia-react-development",
- "echo-react-development",
- "tailwindcss-development",
- "echo-development",
```
I can't track why, any idea?
@pushpak1300 That was my first guess, as we have different developers in the team - but it wasnβt the case π« no other lock files locally or on our repo
Latest boost. Maybe I check out latest version of the repository and ask Claude to diagnose and get back to you
@allenwalton@amorriscode The part I haven't figured out is how to --dangerously-skip-permissions π any hint @amorriscode? Accept edits doesn't seem to work the same way it does in the CLI
I love the Desktop app, but sometimes I just want to not have to accept 500 permissions π
@aarondfrancis So do we! @yondifon extended @laravelphp Horizon to be Postgres compatible π
Probably we should open it up, now that we've run it in production safely for a bit
Content is really what most founders struggle with.. Shameless plug but connect this with PITAS and get mass distribution with managed accounts, proper warm up and interactions, reply to comments with intention ("whats the app/link?") 24/7... would love to show you https://t.co/7qAlTJPe42
@0xROAS Good stuff! Would love to show you how can you improve this with a completed managed accounts: creation, warm ups, or even replying 24/7 to any comment https://t.co/ypnB8QFaVj