two-factor-auth-issue
0
总安装量
1
周安装量
安装命令
npx skills add https://github.com/skillrecordings/support --skill two-factor-auth-issue
Agent 安装分布
amp
1
cline
1
opencode
1
cursor
1
continue
1
kimi-cli
1
Skill 文档
Two-Factor Authentication Issue
Response Patterns (from samples)
Common openings:
- “Thank you, [NAME] ———– Forwarded message ———– From: [EMAIL] Date: December 5, 2024 at 3:44 PM CST Subject: New login to your Kit account To: [EMAIL] You recently attempted to log in to your Kit account from an unrecognized device. Device: Chrome on Mac OS X Location: Boise, Idaho, United States (approximate) Time: 4:44 PM EST, December 05, 2024 If this was you, you can complete your login by clicking one of the buttons below. If you’re logging in from a shared or public device, we recommend allowing access just once. Trust this device Trust this device once If you didn’t recently attempt to log in to Kit, we recommend that you change your password immediately to secure your account. You can request a password change by clicking here , or by visiting app.kit.com and clicking the “Forgot your password?” link. Need help? Get in touch by emailing Customer Success at [EMAIL] [ADDRESS] #761, Boise, Idaho 83701″
- “I have been able to reset the password but now when accessing the admin”
- “Hey Kiran,”
Common core lines:
- “>”
- “Thank you, [NAME] ———– Forwarded message ———– From: [EMAIL] Date: December 5, 2024 at 3:44 PM CST Subject: New login to your Kit account To: [EMAIL] You recently attempted to log in to your Kit account from an unrecognized device. Device: Chrome on Mac OS X Location: Boise, Idaho, United States (approximate) Time: 4:44 PM EST, December 05, 2024 If this was you, you can complete your login by clicking one of the buttons below. If you’re logging in from a shared or public device, we recommend allowing access just once. Trust this device Trust this device once If you didn’t recently attempt to log in to Kit, we recommend that you change your password immediately to secure your account. You can request a password change by clicking here , or by visiting app.kit.com and clicking the “Forgot your password?” link. Need help? Get in touch by emailing Customer Success at [EMAIL] [ADDRESS] #761, Boise, Idaho 83701″
- “I have been able to reset the password but now when accessing the admin”
Common closings:
- “Thank you, [NAME] ———– Forwarded message ———– From: [EMAIL] Date: December 5, 2024 at 3:44 PM CST Subject: New login to your Kit account To: [EMAIL] You recently attempted to log in to your Kit account from an unrecognized device. Device: Chrome on Mac OS X Location: Boise, Idaho, United States (approximate) Time: 4:44 PM EST, December 05, 2024 If this was you, you can complete your login by clicking one of the buttons below. If you’re logging in from a shared or public device, we recommend allowing access just once. Trust this device Trust this device once If you didn’t recently attempt to log in to Kit, we recommend that you change your password immediately to secure your account. You can request a password change by clicking here , or by visiting app.kit.com and clicking the “Forgot your password?” link. Need help? Get in touch by emailing Customer Success at [EMAIL] [ADDRESS] #761, Boise, Idaho 83701″
- “>”
- “Let me know if you have any issues requesting login links using that email address.”
Phrases That Work (4-gram frequency)
- “to your kit account” â 2 (50%)
- “to log in to” â 2 (50%)
- “thank you creeland forwarded” â 1 (25%)
- “you creeland forwarded message” â 1 (25%)
- “creeland forwarded message from” â 1 (25%)
- “forwarded message from email” â 1 (25%)
- “message from email date” â 1 (25%)
- “from email date december” â 1 (25%)
- “email date december 5” â 1 (25%)
- “date december 5 2024” â 1 (25%)
Tone Guidance (observed)
- Openings trend toward: “Thank you, [NAME] ———– Forwarded message ———– From: [EMAIL] Date: December 5, 2024 at 3:44 PM CST Subject: New login to your Kit account To: [EMAIL] You recently attempted to log in to your Kit account from an unrecognized device. Device: Chrome on Mac OS X Location: Boise, Idaho, United States (approximate) Time: 4:44 PM EST, December 05, 2024 If this was you, you can complete your login by clicking one of the buttons below. If you’re logging in from a shared or public device, we recommend allowing access just once. Trust this device Trust this device once If you didn’t recently attempt to log in to Kit, we recommend that you change your password immediately to secure your account. You can request a password change by clicking here , or by visiting app.kit.com and clicking the “Forgot your password?” link. Need help? Get in touch by emailing Customer Success at [EMAIL] [ADDRESS] #761, Boise, Idaho 83701″
- Closings often include: “Thank you, [NAME] ———– Forwarded message ———– From: [EMAIL] Date: December 5, 2024 at 3:44 PM CST Subject: New login to your Kit account To: [EMAIL] You recently attempted to log in to your Kit account from an unrecognized device. Device: Chrome on Mac OS X Location: Boise, Idaho, United States (approximate) Time: 4:44 PM EST, December 05, 2024 If this was you, you can complete your login by clicking one of the buttons below. If you’re logging in from a shared or public device, we recommend allowing access just once. Trust this device Trust this device once If you didn’t recently attempt to log in to Kit, we recommend that you change your password immediately to secure your account. You can request a password change by clicking here , or by visiting app.kit.com and clicking the “Forgot your password?” link. Need help? Get in touch by emailing Customer Success at [EMAIL] [ADDRESS] #761, Boise, Idaho 83701″
What NOT To Do
- Don’t introduce policy details that are not present in the verified response lines above.
- Don’t paraphrase or reframe the customer’s question in a way that changes meaning.
- Don’t add refund/discount promises unless they appear in the extracted responses for this topic.
Validation
Draft must:
- Include at least one of the required phrases from the validation block
- Stay consistent with the observed response patterns above
- NOT introduce policy details that are not present in the verified response lines above.