@williamkos 

— good questions. I would separate these into three areas:

1. Customizing the KB generation prompt
   You generally should not modify the delivered OOB KB generation skill directly. The supported pattern is to clone the OOB KB generation skill in Now Assist Skill Kit, then configure custom prompts for the applicable OOB or custom knowledge article templates. That allows you to align the generated article structure with the customer’s template, required sections, writing standards, or KCS-style guidance.

2. Generating from sources beyond incidents/cases
   OOTB KB generation is primarily delivered around supported source records such as incidents, cases, and work order tasks. For other source records, this becomes more of a custom/cloned NASK skill pattern. You would need to define the input source, pass the relevant record fields into the prompt, and optionally use retrievers to bring in additional indexed context.

3. Creating translated versions
   For translation, I would distinguish between Now Assist multilingual support and formal KB article translation. Now Assist multilingual services can support generation/interaction in supported languages, but if the requirement is to create and manage translated KB article records, the Knowledge translation/localization process should be considered as part of the design. A custom skill could potentially assist with translation content generation, but workflow, review, publishing, and article relationships still need to be designed carefully.

Bottom line: this does not necessarily mean building everything from scratch, but it likely does mean using Now Assist Skill Kit as the extensibility path rather than expecting the OOTB KB generation action to satisfy all three requirements as-is.

@rob_martoncik @John Vincent 
this is exactly the gap I've been describing. Article-type-aware optimization isn't a nice-to-have; it's what makes the difference between output that's actually usable and output that's generic enough to be unhelpful. William's customer is already working around it.