sjyangkevin commented on issue #61984:
URL: https://github.com/apache/airflow/issues/61984#issuecomment-3912062633

   Hi @jason810496 ,
   
   I created this draft PR (https://github.com/apache/airflow/pull/62059) after 
doing some exploration. I think we don't have a `SKILL.md`, or a sample 
locale-specific instruction, defined yet. So, I would like to open this draft 
to ensure I am on the right direction. Meanwhile, it would be great if these 
two files can be used as a reference to implement other locale-specific 
instruction.
   
   Basically, in `SKILL.md`, we could provide a high-level instruction to guide 
the agent on the following:
   1. where to find locale-specific guidelines
   2. general rules across locales
   3. step-by-step workflow
   4. Airflow terminologies / conventions
   
   locale-specific instruction includes specific rules for translating from 
English to the specific language. Also, as mentioned in dev list,  the reasons 
for its terminology choices.
   
   I wonder if we already have such standard or what we should include in the 
skill instruction. If not, probably it is a good time to discuss on this 
aspect, and this could help standardize other implementations.
   
   I also found an issue related to licensing when creating the `SKILL.md`. As 
the YAML formatter must be on the first line of the file, the agent skill 
specification provides a key "license". However, the pre-commit hook will 
attempt to add license, and TOC, etc. to the skill instruction, which could 
break the skill parsing. I am not sure what would be the best way to handle the 
licensing, and would appreciate any feedback on it.
   
   Thanks,


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to