Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Agent Skill to Force Docs in ASD-STE100 Simplified Technical English

github.com

Post reply on HN
Print view View original

41–50 of 139 posts

Re: Agent Skill to Force Docs in ASD-STE100 Simplified Technical English

#41

Post by mastodon_acc »

bbg2401 wrote: post #31
UqWBcuFx6NV4r wrote: post #13

Earlier quoted context omitted.

What’s it like to be this abrasive about people simply doing things?

It would be nice if people were indeed doing things. However, asking Claude to write a skill encoding ASD-STE100 after seeing it pop-up in your social feed is not doing much at all. It's certainly not worth a post on HN. Having said that, this skill might have been the seed for the flurry of low-effort posts on the subject on various platforms this week. If that's the case, I take back the majority of my scorn. You'l…

Not everyone spends their time browsing hackernews or other forums all day.

This is the first time I’m hearing about this, I think it’s nifty, and it’s precisely why I come to hackernews at least once a day.

Also what is wrong with using Claude to make a more polished post about something that’s being talked about already?

Re: Agent Skill to Force Docs in ASD-STE100 Simplified Technical English

#42

Post by gillesjacobs »

https://youtu.be/uJblcC4lKYw

This video benchmarks slop-style indicators with different skill/prompt solutions including the STE skill vs. George Orwell's six rules of writing prompt: Orwell came out on top overall.

Additional bonus: it doesn't add much more tokens to input context. I have compared prose prompts with these rules and without and I am liking the results.

  1. Never use a metaphor, simile, or other figure of speech which you are used to seeing in print.
  2. Never use a long word where a short one will do.
  3. If it is possible to cut a word out, always cut it out.
  4. Never use the passive where you can use the active.
  5. Never use a foreign phrase, a scientific word, or a jargon word if you can think of an everyday English equivalent.
  6. Break any of these rules sooner than say anything outright barbarous.

Re: Agent Skill to Force Docs in ASD-STE100 Simplified Technical English

#44

Post by wonnage »

mastodon_acc wrote: post #41
bbg2401 wrote: post #31

Earlier quoted context omitted.

It would be nice if people were indeed doing things. However, asking Claude to write a skill encoding ASD-STE100 after seeing it pop-up in your social feed is not doing much at all. It's certainly not worth a post on HN. Having said that, this skill might have been the seed for the flurry of low-effort posts on the subject on various platforms this week. If that's the case, I take back the majority of my scorn. You'l…

Not everyone spends their time browsing hackernews or other forums all day. This is the first time I’m hearing about this, I think it’s nifty, and it’s precisely why I come to hackernews at least once a day. Also what is wrong with using Claude to make a more polished post about something that’s being talked about already?

This is actually completely useless slop and any illusion of usefulness is misguided

Re: Agent Skill to Force Docs in ASD-STE100 Simplified Technical English

#47

Post by rspeele »

Planktonne wrote: post #34

This is cruft [1]. No one who is capable of using this needs it--it's a line in the prompt at most. [1] https://knowyourmeme.com/memes/thinking-quickly-dave-constru...

I have yet to see an "agent skill" that does not match this description.

Re: Agent Skill to Force Docs in ASD-STE100 Simplified Technical English

#49

Post by bcrosby95 »

mcintyre1994 wrote: post #24
bayesnet wrote: post #17

It’s ironic that the README has all the tells of being LLM-written: > 53 numbered rules, 9 sections, written in 1983 by people whose readers die when a sentence is ambiguous. The ones doing the heavy lifting: … Not really a promising tell for a writing skill, IMO.

They acknowledge this, but I really dislike whatever style they're using for the readme: > Yes, this README breaks half of them. Marketing is explicitly out of STE scope. The skill knows that and stays in the docs. > Where it refuses to go: marketing copy, blog voice, brand writing. Flat on purpose. (Each sentence there has an emoji that HN cuts out)

The problem with at least ChatGPT is no matter what personality you set it still reads like a smug asshole trying to sound smart. You can just pick different flavors of smug asshole.

Re: Agent Skill to Force Docs in ASD-STE100 Simplified Technical English

#50

Post by hedgehog »

rspeele wrote: post #47
Planktonne wrote: post #34

This is cruft [1]. No one who is capable of using this needs it--it's a line in the prompt at most. [1] https://knowyourmeme.com/memes/thinking-quickly-dave-constru...

I have yet to see an "agent skill" that does not match this description.

They are useful for packaging all the related bits together. Some instructions on the line to add to the main prompt, detailed policy doc that spells out details, troubleshooting docs, the code itself, etc.
Post reply on HN