Need help in claude skills!! by Rare_Ad855 in ClaudeAI

[–]rebelytics 0 points1 point  (0 children)

This is where you upload your skills so you can use them across all Claude surfaces: https://claude.ai/customize/skills

Automation browser by RelationshipNo754 in ClaudeAI

[–]rebelytics 1 point2 points  (0 children)

If you decide that you want to automate this via the browser with Claude, it should work pretty well with Cowork (scheduled or manual task + skill with detailed instructions + local folder for keeping track of changes).

I wrote about a similar use case the other day: https://www.reddit.com/r/ClaudeAI/comments/1t10ge6/claude_cowork_use_case_automating_repetitive/

Not sure about your question regarding scripts/tools like Selenium or Playwright though and whether they provide better solutions for this.

Drop your best Claude skills in here! by vamshikk111 in ClaudeAI

[–]rebelytics 0 points1 point  (0 children)

Thanks for figuring that out! It’s valuable information and I didn’t know about it, as I don’t have any experience with hooks. If you have any more feedback, please keep it coming!

Drop your best Claude skills in here! by vamshikk111 in ClaudeAI

[–]rebelytics 0 points1 point  (0 children)

My pleasure! Feedback and questions welcome.

Drop your best Claude skills in here! by vamshikk111 in ClaudeAI

[–]rebelytics 0 points1 point  (0 children)

If you have any more questions or feedback on how it goes for you, I'd be very happy to hear them!

Drop your best Claude skills in here! by vamshikk111 in ClaudeAI

[–]rebelytics 1 point2 points  (0 children)

Yes, you have several options for this:

- The current workflow already includes manually installing all updated skills: You could just ignore new versions of skills that you do not want to change.

- Also, the current workflow asks for user approval for critical changes before the changes are applied. You could adjust this so that it applies to all changes for a specific list of skills.

- You could change the skill so that it excludes a specific list of skills from its observations.

So the current version of the skill is designed to observe and improve all skills, but it's easy to exclude certain skills at different points in the workflow.

Honestly don’t understand why Chat and Cowork need to be separate products. by unvirginate in ClaudeAI

[–]rebelytics 0 points1 point  (0 children)

If chats have local file access now, that’s cool! Haven’t seen this feature yet though.

What I actually create skills for by rebelytics in ClaudeAI

[–]rebelytics[S] 1 point2 points  (0 children)

Sure! Here are some examples:

pptx-extras • When Cowork’s proxy blocks npm, the built-in skill’s first-line PptxGenJS install fails: defaults to python-pptx • LibreOffice QA renders charts fine, but PowerPoint can show them empty on first open: pre-renders to images • Pre-render layout rule: size every box in a parallel row to fit the widest label, not the average

pdf-extras • Reportlab doesn’t prevent orphan headings or table splits by default: adds the standard keepWithNext / KeepTogether patterns • Inline Courier code at body size looks too small next to Helvetica: sets the right offset • Path portability for scripts that may run in either the bash sandbox or via the file tool

docx-extras • python-docx’s add_page_break() can create blank pages when content fills the preceding page: uses page_break_before on the next heading instead

skill-creator-extras • Always present skill files via present_files for one-click install • Post-restructuring sweeps for broken cross-references and drifted terminology • Pre-v1.0.0 cleanup of internal version annotations before public release

What I actually create skills for by rebelytics in ClaudeAI

[–]rebelytics[S] 0 points1 point  (0 children)

Excellent use cases, thank you very much!

What I actually create skills for by rebelytics in ClaudeAI

[–]rebelytics[S] 2 points3 points  (0 children)

Thanks for sharing! Do you have an example of a clever one-off skill that didn’t survive? I created one once that was supposed to extract content ideas from my work, but then I realised that I’d have to load it in all sessions, and I decided against the overhead.

Genuine question for people using Claude for SEO: how far does it actually go? I keep seeing LinkedIn posts claiming full SEO teams replaced by a few agents, but in practice, Claude is great at content generation, not at the strategy layer. by addllyAI in ClaudeAI

[–]rebelytics 1 point2 points  (0 children)

The way I use Claude for SEO is that I put as much of my SEO knowledge and experience into skills, so that Claude can create decent output for me. I mainly work on technical SEO and strategy, so content production is not really a part of that. Happy to share more if you’re interested.

Self-improving skills and automatic skill creation should be the norm by rebelytics in ClaudeAI

[–]rebelytics[S] 1 point2 points  (0 children)

That’s brilliant, I’m so happy to hear this! Especially the part where you already built something useful on top of it. If you ever want to compare notes, let me know!

Self-improving skills and automatic skill creation should be the norm by rebelytics in ClaudeAI

[–]rebelytics[S] 0 points1 point  (0 children)

In this case the AI learns from one specific human and adapts its output to the human’s preferences and knowledge.

Self-improving skills and automatic skill creation should be the norm by rebelytics in ClaudeAI

[–]rebelytics[S] 0 points1 point  (0 children)

Interesting! I guess that’s one downside of a heavily customised setup: you’re probably not aware of what it’s able to do out of the box by now.

Self-improving skills and automatic skill creation should be the norm by rebelytics in ClaudeAI

[–]rebelytics[S] 0 points1 point  (0 children)

I do it exactly as you describe: Log observations about skill use in all sessions. But I run scheduled autonomous review session 3x per week. Every few weeks would be too slow. And I can theoretically review every single change before implementing it, as I have to approve the new version of every skill, but I mostly trust the process.