Blog proposal: Agent Skills for GraphQL
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 48/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- graphql, typescript
- Domain
- content
Research direction
Read the blog contribution guidance and inspect the existing blog structure to see where a post about Agent Skills for GraphQL would fit. The proposal outlines the topics, but does not identify a target file or define review and completion criteria; clarify the fit and scope before drafting.
Written by the indexing model from the issue text.
Description
Hey folks, Dale from Apollo here.
I'd love to write a blog post about Agent Skills for GraphQL. I spoke about this at GraphQLConf, and a lot of people came up afterward to ask questions. The live demo at GraphQL Day London this year also got a great response. My talk didn't make the cut for GraphQL Paris, though, so I figured a blog post could reach more people than any single stage 😄
Rough plan:
- Why agents guess instead of following your conventions
- What a Skill is, and the open standard behind it
- Before and after examples from the live demo, with eval results
- Where Skills help most in GraphQL work
- How to write and share your own Skills
Does this sound like a good fit?
- Dominant language
- TypeScript
- Stars
- 889
- Forks
- 1.5k
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 32
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from graphql/graphql.github.io
-
Mistake in learning web ui.May be free again A pull request for this issue was closed without being merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 78/100
graphql/graphql.github.io#1933 ·
Maintainers usually reply within 1 day
-
💄 Enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
graphql/graphql.github.io#1832 ·
Maintainers usually reply within 1 day
-
New event image generation brokenPossibly taken @bignimbus claimed this 13 days ago. Open
graphql/graphql.github.io#2563 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
graphql/graphql.github.io#2551 · 2 comments ·
Maintainers usually reply within 1 day
-
Documentation sections are missing from Resource Hub category pagesPossibly taken @6iu8a claimed this 36 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
graphql/graphql.github.io#2533 ·
Maintainers usually reply within 1 day
All issues in graphql/graphql.github.io
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Add "append" and "prepend" slots for vue-vuetify extended renderersPossibly taken @simeyc claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
eclipsesource/jsonforms#2668 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
cobot/zapier#520 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
README の通知条件を実際の判定処理に合わせるPossibly taken @unhappychoice claimed this today. Openfactory:in-progress priority:medium
Difficulty 1/5 Under an hour Newbie friendliness 90/100
unhappychoice/oss-issue-opener#395 · 1 comment ·
Maintainers usually reply within 1 day