Skip to content

Add resources section to README to include ai-declare skill#22

Open
yujqiao wants to merge 1 commit into
DimwitLabs:mainfrom
yujqiao:patch-1
Open

Add resources section to README to include ai-declare skill#22
yujqiao wants to merge 1 commit into
DimwitLabs:mainfrom
yujqiao:patch-1

Conversation

@yujqiao
Copy link
Copy Markdown
Contributor

@yujqiao yujqiao commented May 23, 2026

Pull Request Template

Thank you for your contribution!

Note

Before submitting this PR, please ensure You have opened a related issue and referenced it below.

Related Issue:
This is a simple and straight-forward change without an issue. Feel free to close this if you think it's not the right place to include

Description of Changes:

Add resources section to README to include ai-declare skill

AI-DECLARATION.md:

  • I have reviewed the project's AI-DECLARATION.md
  • I have updated AI-DECLARATION.md to reflect AI usage in this contribution (or confirmed no update is needed)

Additional Notes:
Feel free to close this if you think it's not the right place to include

@DeepanshKhurana
Copy link
Copy Markdown
Member

@yujqiao, thank you for the skill. I believe it will help people a lot and make things easier for them! I invite new tooling so this is welcome! That said, I have a few nitpicks.

Isn't it a huge overhead to keep updating the skill with the right version instead of it somehow fetching or inferring the latest version from the spec? Again, I don't mind but I think you will have to update it each time the spec updates and it would be a chore for you. Up to you on this one. (source)

## Common Mistakes

- **Wrong version string**: Must be `"0.1.2"` (quoted, with patch version)

Also, although verbose, I would suggest that the options a user gets remain the same as the spec's usage definitions (and be updated accordingly) if future specs change things. These are discussed and deliberated over on GitHub, Reddit, and other places, and the phrasing is a feature in a way. Also, I know the spec will be written correctly, but then this defeats a sort of assumed WYSIWYG for the user of the skill. (source).

> Which AI involvement level best describes this project?
> 1. **none** — No AI tools used
> 2. **hint** — AI surfaced suggestions passively
> 3. **assist** — AI helped with parts of tasks
> 4. **pair** — Human and AI collaborated equally
> 5. **copilot** — AI generated most code with human oversight
> 6. **auto** — AI built the project autonomously

Copy link
Copy Markdown
Member

@DeepanshKhurana DeepanshKhurana left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a great idea, and I thank you for the initiative. Let's discuss on my other comments. I'm curious to hear what you think!

Comment thread README.md
䷼ Hexagram 61 or Hexagram For Inner Truth (Unicode: `U+4DFC`) is one of 64 hexagrams in the Yi (I) Ching to illustrate principles where each line is either Yin (broken) or Yang (solid). ([source](https://en.wikipedia.org/wiki/List_of_hexagrams_of_the_I_Ching#Hexagram_61))

## Resources
- [ai-declare](https://github.com/yujqiao/ai-declare) agent skill to generate `AI-DECLARATION.md`
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I recommend changing this to:

- [yujqiao/ai-declare](https://github.com/yujqiao/ai-declare) agent skill to generate `AI-DECLARATION.md`

@DeepanshKhurana
Copy link
Copy Markdown
Member

💡 If the spec exposed an API that was a simple, no auth, REST GET endpoint that simply gave the current schema of the spec, would a skill be able to consume it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants